[OpenSIPS-Users] Dispatcher nodes start as Inactive

[Bogdan-Andrei Iancu]

Hi Rik,

Do you set the "ds_probing_mode" param ? Maybe you start with the 
destination as active, but because of that param (whenset to 1), the 
probing is permanent and the destinations may be learned as inactive 
(based on probing).

Regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com

On 10.06.2014 13:06, Rik Broers wrote:
>
> I’ve tried putting 0 in the flags column, They still start as 
> Inactive. Strange thing is that not all of them start as inactive?
>
> Opensips –V output below:
>
> version: opensips 1.10.1-notls (x86_64/linux)
>
> flags: STATS: On, USE_IPV6, USE_TCP, DISABLE_NAGLE, USE_MCAST, 
> SHM_MEM, SHM_MMAP, PKG_MALLOC, F_MALLOC, FAST_LOCK-ADAPTIVE_WAIT
>
> ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, 
> MAX_URI_SIZE 1024, BUF_SIZE 65535
>
> poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
>
> git revision: f03f552
>
> @(#) $Id$
>
> main.c compiled on 11:28:31 May 19 2014 with gcc 4.4.5
>
> Vriendelijke groet,
>
> *Rik Broers*
> Voice Engineer
>
> *Van:*Bogdan-Andrei Iancu [mailto:bogdan at opensips.org]
> *Verzonden:* dinsdag 27 mei 2014 11:33
> *Aan:* Rik Broers; users at lists.opensips.org
> *Onderwerp:* Re: [OpenSIPS-Users] Dispatcher nodes start as Inactive
>
> Hi Rik,
>
> yes, I have to agree about the docs - it needs to be done.
>
> Put 0 for the flags - that means is active .
>
> Regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developer
> http://www.opensips-solutions.com
>
> On 27.05.2014 11:43, Rik Broers wrote:
>
>     So i can use the following values in the Flags column?
>
>     ·/"i", "I" or "0"/- the last destination should be set to inactive
>     and will be ignored in future requests.
>
>     ·/"a", "A" or "1"/- the last destination should be set to active.
>
>     ·/"p", "P" or "2"/- the last destination will be set to probing.
>     Note: You will need to call this function "threshhold"-times,
>     before it will be actually set to probing.
>
>     I don’t find this to be very clear from the documentation, as
>     there also is the modparam named flags which does not seem to do
>     anything with Flags in the DB.
>
>     No where there is specifically noted what values you can use for
>     the different columns.
>
>     Vriendelijke groet,
>
>     *Rik Broers*
>     Voice Engineer
>
>     *Van:*Bogdan-Andrei Iancu [mailto:bogdan at opensips.org]
>     *Verzonden:* maandag 26 mei 2014 20:00
>     *Aan:* users at lists.opensips.org <mailto:users at lists.opensips.org>;
>     Rik Broers
>     *Onderwerp:* Re: [OpenSIPS-Users] Dispatcher nodes start as Inactive
>
>     Hi Rik,
>
>     In 1.10, upon restart, the status flags from DB are loaded (the in
>     memory state is discarded) - so  check the flags you have for the
>     destinations in DB.
>
>     Regards,
>
>
>     Bogdan-Andrei Iancu
>
>     OpenSIPS Founder and Developer
>
>     http://www.opensips-solutions.com
>
>     On 26.05.2014 09:55, Rik Broers wrote:
>
>         When I restart my 1.10 opensips a lot of the dispatcher nodes
>         start as Inactive.
>
>         I have to manually set them to P or A before they become used.
>
>         How can I make sure all nodes start as Probing or Active after
>         a server reboot.
>
>         Vriendelijke groet,
>
>         *Rik Broers*
>         Voice Engineer
>
>
>
>
>
>
>
>         _______________________________________________
>
>         Users mailing list
>
>         Users at lists.opensips.org  <mailto:Users at lists.opensips.org>
>
>         http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20140610/cdccb6db/attachment-0001.htm>