subject:"\[OpenSIPS\-Users\] Wrong number of children"

Re: [OpenSIPS-Users] Wrong number of children

2018-02-28 Thread Bogdan-Andrei Iancu


Super !

I like this "unwanted children" :P

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  http://www.opensips-solutions.com
OpenSIPS Summit 2018
  http://www.opensips.org/events/Summit-2018Amsterdam

On 02/28/2018 12:36 PM, xaled wrote:


Hi Bodgan,

thanks, now there are no unwanted TCP children ;)

Number of SIP receiver UDP children matches the children param value.

ivr01:/usr/local/etc/opensips # /usr/local/sbin/opensipsctl fifo ps

Process::  ID=0 PID=12872 Type=attendant

Process::  ID=1 PID=12873 Type=MI FIFO

Process::  ID=2 PID=12874 Type=time_keeper

Process::  ID=3 PID=12875 Type=timer

Process::  ID=4 PID=12876 Type=SIP receiver udp: x.x.x.x:5060

Process::  ID=5 PID=12878 Type=SIP receiver udp: x.x.x.x:5060

Process::  ID=6 PID=12879 Type=SIP receiver udp: x.x.x.x:5060

Process::  ID=7 PID=12880 Type=SIP receiver udp: x.x.x.x:5060

Process::  ID=8 PID=12881 Type=Timer handler

Xaled

*From:*Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
*Sent:* Tuesday, February 27, 2018 6:39 PM
*To:* OpenSIPS users mailling list <users@lists.opensips.org>; xaled 
<xa...@web.de>

*Subject:* Re: [OpenSIPS-Users] Wrong number of children

Ok, thanks to Razvan, we have an fix for this:
https://github.com/OpenSIPS/opensips/commit/b022ad5a7c1c24aa9cf3ddf22d5f50510807c9f4

Please update from GIT and give it a try.

Many Thanks,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
   http://www.opensips-solutions.com
OpenSIPS Summit 2018
   http://www.opensips.org/events/Summit-2018Amsterdam

On 02/27/2018 06:38 PM, Bogdan-Andrei Iancu wrote:

Thank you Xaled,

Based on the output you provided I managed to identify the issue.
There is a tricky internal test that actually forces the TCP layer
to start more or less all the time.
Let us have this fixed !! I will update you

Best regards,


Bogdan-Andrei Iancu

OpenSIPS Founder and Developer

   http://www.opensips-solutions.com

OpenSIPS Summit 2018

   http://www.opensips.org/events/Summit-2018Amsterdam

On 02/27/2018 06:30 PM, xaled wrote:

Hi Bogdan,

It’s a different server, but the same tcp issue:

2018-02-27T17:19:29.939207+01:00 dus-ivr01 opensips:
DBG:core:main: Loaded 1 transport protocols

2018-02-27T17:19:29.939411+01:00 dus-ivr01 opensips:
DBG:core:socket2str: 

2018-02-27T17:19:29.939630+01:00 dus-ivr01 opensips:
INFO:core:tcp_init: enabling TCP for proto 5

2018-02-27T17:19:29.939842+01:00 dus-ivr01 opensips:
DBG:core:ipc_register_handler: IPC type 0 [TCP reporting]
registered with

handler 0x5f9fee

2018-02-27T17:19:29.940120+01:00 dus-ivr01 opensips:
DBG:core:create_status_pipe: pipe created ? rc = 0, errno =
Success

2018-02-27T17:19:29.940326+01:00 dus-ivr01 opensips:
DBG:core:daemonize: waiting for status code from children

2018-02-27T17:19:29.940526+01:00 dus-ivr01 opensips:
DBG:core:count_init_children: 15 children are going to be inited

2018-02-27T17:19:29.940724+01:00 dus-ivr01
/usr/local/sbin/opensips[13076]: DBG:core:set_core_dump: core
dump limits set to 18

446744073709551615

2018-02-27T17:19:29.940951+01:00 dus-ivr01
/usr/local/sbin/opensips[13076]: NOTICE:core:main: version:
opensips 2.3.3 (x86_64/

linux)

Do you need full logs, or is this enough?

Thanks,

Xale

*From:*Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
*Sent:* Monday, February 26, 2018 10:38 PM
*To:* xaled <xa...@web.de> <mailto:xa...@web.de>
    *Subject:* Re: [OpenSIPS-Users] Wrong number of children

Please apply the below patch, recompile and send again the
startup logs:

diff --git a/net/net_tcp.c b/net/net_tcp.c
index 2dbea49..2d63940 100644
--- a/net/net_tcp.c
+++ b/net/net_tcp.c
@@ -1624,7 +1624,7 @@ int tcp_init(void)
/* first we do auto-detection to see if there are any
TCP based
 * protocols loaded */
for ( i=PROTO_FIRST ; i  


OpenSIPS Founder and Developer

   http://www.opensips-solutions.com

OpenSIPS Summit 2018

   http://www.opensips.org/events/Summit-2018Amsterdam

On 02/26/2018 08:14 PM, xaled wrote:

Hi Bogdan,

would a full debug log will be sufficient?

The config is spread across quite a few files.

Thanks,

Xaled

*From:*Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
*Sent:* Monday, February 26, 2018 5:25 PM
*To:* xaled <xa...@web.de> <mailto:xa...@web.de>;
'OpenSIPS users mailling list' <users@lists.opensips.org>
<mailto:users@lists.opensips.org>
    *Subject:* Re:

Re: [OpenSIPS-Users] Wrong number of children

2018-02-28 Thread xaled

Hi Bodgan,

 

thanks, now there are no unwanted TCP children ;)

Number of SIP receiver UDP children matches the children param value.

 

ivr01:/usr/local/etc/opensips # /usr/local/sbin/opensipsctl fifo ps

Process::  ID=0 PID=12872 Type=attendant

Process::  ID=1 PID=12873 Type=MI FIFO

Process::  ID=2 PID=12874 Type=time_keeper

Process::  ID=3 PID=12875 Type=timer

Process::  ID=4 PID=12876 Type=SIP receiver udp: x.x.x.x:5060

Process::  ID=5 PID=12878 Type=SIP receiver udp: x.x.x.x:5060

Process::  ID=6 PID=12879 Type=SIP receiver udp: x.x.x.x:5060

Process::  ID=7 PID=12880 Type=SIP receiver udp: x.x.x.x:5060

Process::  ID=8 PID=12881 Type=Timer handler

 

Xaled

 

From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org] 
Sent: Tuesday, February 27, 2018 6:39 PM
To: OpenSIPS users mailling list <users@lists.opensips.org>; xaled 
<xa...@web.de>
Subject: Re: [OpenSIPS-Users] Wrong number of children

 

Ok, thanks to Razvan, we have an fix for this:
https://github.com/OpenSIPS/opensips/commit/b022ad5a7c1c24aa9cf3ddf22d5f50510807c9f4

Please update from GIT and give it a try.

Many Thanks,



Bogdan-Andrei Iancu
 
OpenSIPS Founder and Developer
  http://www.opensips-solutions.com
OpenSIPS Summit 2018
  http://www.opensips.org/events/Summit-2018Amsterdam

On 02/27/2018 06:38 PM, Bogdan-Andrei Iancu wrote:

Thank you Xaled,

Based on the output you provided I managed to identify the issue. There is a 
tricky internal test that actually forces the TCP layer to start more or less 
all the time.
Let us have this fixed !! I will update you 

Best regards,




Bogdan-Andrei Iancu
 
OpenSIPS Founder and Developer
  http://www.opensips-solutions.com
OpenSIPS Summit 2018
  http://www.opensips.org/events/Summit-2018Amsterdam

On 02/27/2018 06:30 PM, xaled wrote:

Hi Bogdan,

 

It’s a different server, but the same tcp issue:

 

2018-02-27T17:19:29.939207+01:00 dus-ivr01 opensips: DBG:core:main: Loaded 1 
transport protocols

2018-02-27T17:19:29.939411+01:00 dus-ivr01 opensips: DBG:core:socket2str: 


2018-02-27T17:19:29.939630+01:00 dus-ivr01 opensips: INFO:core:tcp_init: 
enabling TCP for proto 5

2018-02-27T17:19:29.939842+01:00 dus-ivr01 opensips: 
DBG:core:ipc_register_handler: IPC type 0 [TCP reporting] registered with

handler 0x5f9fee

2018-02-27T17:19:29.940120+01:00 dus-ivr01 opensips: 
DBG:core:create_status_pipe: pipe created ? rc = 0, errno = Success

2018-02-27T17:19:29.940326+01:00 dus-ivr01 opensips: DBG:core:daemonize: 
waiting for status code from children

2018-02-27T17:19:29.940526+01:00 dus-ivr01 opensips: 
DBG:core:count_init_children: 15 children are going to be inited

2018-02-27T17:19:29.940724+01:00 dus-ivr01 /usr/local/sbin/opensips[13076]: 
DBG:core:set_core_dump: core dump limits set to 18

446744073709551615

2018-02-27T17:19:29.940951+01:00 dus-ivr01 /usr/local/sbin/opensips[13076]: 
NOTICE:core:main: version: opensips 2.3.3 (x86_64/

linux)

 

Do you need full logs, or is this enough?

 

Thanks,

Xale

From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org] 
Sent: Monday, February 26, 2018 10:38 PM
To: xaled  <mailto:xa...@web.de> <xa...@web.de>
Subject: Re: [OpenSIPS-Users] Wrong number of children

 

Please apply the below patch, recompile and send again the startup logs:

diff --git a/net/net_tcp.c b/net/net_tcp.c
index 2dbea49..2d63940 100644
--- a/net/net_tcp.c
+++ b/net/net_tcp.c
@@ -1624,7 +1624,7 @@ int tcp_init(void)
/* first we do auto-detection to see if there are any TCP based
 * protocols loaded */
for ( i=PROTO_FIRST ; ihttp://www.opensips-solutions.com
OpenSIPS Summit 2018
  http://www.opensips.org/events/Summit-2018Amsterdam

On 02/26/2018 08:14 PM, xaled wrote:

Hi Bogdan,

 

would a full debug log will be sufficient?

 

The config is spread across quite a few files.

 

Thanks,

Xaled

 

From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org] 
Sent: Monday, February 26, 2018 5:25 PM
To: xaled  <mailto:xa...@web.de> <xa...@web.de>; 'OpenSIPS users mailling list' 
 <mailto:users@lists.opensips.org> <users@lists.opensips.org>
Subject: Re: [OpenSIPS-Users] Wrong number of children

 

Hmm that is strange.

Could you send me (off list) your cfg to give it a try - I see you use the 
2.3.3 version , right ?

Regards,





Bogdan-Andrei Iancu
 
OpenSIPS Founder and Developer
  http://www.opensips-solutions.com
OpenSIPS Summit 2018
  http://www.opensips.org/events/Summit-2018Amsterdam

On 02/26/2018 06:27 PM, xaled wrote:

Nothing

 

root@dus-appsrv01:/etc/opensips# opensipsctl fifo ps

Process::  ID=0 PID=14966 Type=attendant

Process::  ID=1 PID=14967 Type=MI FIFO

Process::  ID=2 PID=14968 Type=time_keeper

Process::  ID=3 PID=14969 Type=timer

Process::  ID=4 PID=14970 Type=SIP receiver udp:1.2.3.4:5060

Process::  ID=5 PID=14975 Type=SIP receiver udp:1.2.3.4:5060

Process::  ID=6 PID=14976 Type=SIP receiver udp:1.2.3.4:5060

Process::  ID=7 PID=14977 Type=SIP receiver udp:1.2.3.4:5060

Re: [OpenSIPS-Users] Wrong number of children

2018-02-27 Thread xaled

Hi Bogdan,

Glad I could help with this one. 

XaledOn Feb 27, 2018 17:39, Bogdan-Andrei Iancu <bog...@opensips.org> wrote:
  
  
Thank you Xaled,

Based on the output you provided I managed to identify the issue.
There is a tricky internal test that actually forces the TCP layer
to start more or less all the time.
Let us have this fixed !! I will update you 

Best regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  http://www.opensips-solutions.com
OpenSIPS Summit 2018
  http://www.opensips.org/events/Summit-2018Amsterdam

On 02/27/2018 06:30 PM, xaled wrote:


  
  
  
  
Hi Bogdan,
 
It’s a different server, but the same tcp
issue:
 
2018-02-27T17:19:29.939207+01:00 dus-ivr01
opensips: DBG:core:main: Loaded 1 transport protocols
2018-02-27T17:19:29.939411+01:00 dus-ivr01
opensips: DBG:core:socket2str:

2018-02-27T17:19:29.939630+01:00 dus-ivr01
opensips: INFO:core:tcp_init: enabling TCP for proto 5
2018-02-27T17:19:29.939842+01:00 dus-ivr01
opensips: DBG:core:ipc_register_handler: IPC type 0 [TCP
reporting] registered with
 handler 0x5f9fee
2018-02-27T17:19:29.940120+01:00 dus-ivr01
opensips: DBG:core:create_status_pipe: pipe created ? rc =
0, errno = Success
2018-02-27T17:19:29.940326+01:00 dus-ivr01
opensips: DBG:core:daemonize: waiting for status code from
children
2018-02-27T17:19:29.940526+01:00 dus-ivr01
opensips: DBG:core:count_init_children: 15 children are
going to be inited
2018-02-27T17:19:29.940724+01:00 dus-ivr01
/usr/local/sbin/opensips[13076]: DBG:core:set_core_dump:
core dump limits set to 18
446744073709551615
2018-02-27T17:19:29.940951+01:00 dus-ivr01
/usr/local/sbin/opensips[13076]: NOTICE:core:main: version:
opensips 2.3.3 (x86_64/
linux)
 
Do you need full logs, or is this enough?
 
Thanks,
Xale

  
From: Bogdan-Andrei Iancu
[mailto:bog...@opensips.org] 
Sent: Monday, February 26, 2018 10:38 PM
To: xaled <xa...@web.de>
Subject: Re: [OpenSIPS-Users] Wrong number of
children
  

 
Please
  apply the below patch, recompile and send again the
  startup logs:

diff --git a/net/net_tcp.c b/net/net_tcp.c
index 2dbea49..2d63940 100644
--- a/net/net_tcp.c
+++ b/net/net_tcp.c
@@ -1624,7 +1624,7 @@ int tcp_init(void)
    /* first we do auto-detection to see if there
  are any TCP based
 * protocols loaded */
    for ( i=PROTO_FIRST ; i
-   if (is_tcp_based_proto(i))
  {tcp_disabled=0;break;}
+   if (is_tcp_based_proto(i))
  {LM_INFO("enabling TCP for proto
  %d\n",i);tcp_disabled=0;break;}
 
    if (tcp_disabled)
    return 0;


Regards,

  
Bogdan-Andrei Iancu
 
OpenSIPS Founder and Developer
  http://www.opensips-solutions.com
OpenSIPS Summit 2018
  http://www.opensips.org/events/Summit-2018Amsterdam

  On 02/26/2018 08:14 PM, xaled wrote:


  Hi
  Bogdan,
   
  would a full debug log will be sufficient?
   
  The config is spread across quite a few
  files.
   
  Thanks,
  Xaled
   
  

  From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
  
  Sent: Monday, February 26, 2018 5:25 PM
  To: xaled <xa...@web.de>;
  'OpenSIPS users mailling list' <users@lists.opensips.org>
      Subject: Re: [OpenSIPS-Users] Wrong number of
  children

  
   
  Hmm that is strange.

Could you send me (off list) your cfg to give it a try - I
see you use the 2.3.3 version , right ?

Regards,



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

Re: [OpenSIPS-Users] Wrong number of children

2018-02-27 Thread Bogdan-Andrei Iancu


Ok, thanks to Razvan, we have an fix for this:
https://github.com/OpenSIPS/opensips/commit/b022ad5a7c1c24aa9cf3ddf22d5f50510807c9f4

Please update from GIT and give it a try.

Many Thanks,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  http://www.opensips-solutions.com
OpenSIPS Summit 2018
  http://www.opensips.org/events/Summit-2018Amsterdam

On 02/27/2018 06:38 PM, Bogdan-Andrei Iancu wrote:

Thank you Xaled,

Based on the output you provided I managed to identify the issue. 
There is a tricky internal test that actually forces the TCP layer to 
start more or less all the time.

Let us have this fixed !! I will update you

Best regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   http://www.opensips-solutions.com
OpenSIPS Summit 2018
   http://www.opensips.org/events/Summit-2018Amsterdam
On 02/27/2018 06:30 PM, xaled wrote:


Hi Bogdan,

It’s a different server, but the same tcp issue:

2018-02-27T17:19:29.939207+01:00 dus-ivr01 opensips: DBG:core:main: 
Loaded 1 transport protocols


2018-02-27T17:19:29.939411+01:00 dus-ivr01 opensips: 
DBG:core:socket2str: 


2018-02-27T17:19:29.939630+01:00 dus-ivr01 opensips: 
INFO:core:tcp_init: enabling TCP for proto 5


2018-02-27T17:19:29.939842+01:00 dus-ivr01 opensips: 
DBG:core:ipc_register_handler: IPC type 0 [TCP reporting] registered with


handler 0x5f9fee

2018-02-27T17:19:29.940120+01:00 dus-ivr01 opensips: 
DBG:core:create_status_pipe: pipe created ? rc = 0, errno = Success


2018-02-27T17:19:29.940326+01:00 dus-ivr01 opensips: 
DBG:core:daemonize: waiting for status code from children


2018-02-27T17:19:29.940526+01:00 dus-ivr01 opensips: 
DBG:core:count_init_children: 15 children are going to be inited


2018-02-27T17:19:29.940724+01:00 dus-ivr01 
/usr/local/sbin/opensips[13076]: DBG:core:set_core_dump: core dump 
limits set to 18


446744073709551615

2018-02-27T17:19:29.940951+01:00 dus-ivr01 
/usr/local/sbin/opensips[13076]: NOTICE:core:main: version: opensips 
2.3.3 (x86_64/


linux)

Do you need full logs, or is this enough?

Thanks,

Xale

*From:*Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
*Sent:* Monday, February 26, 2018 10:38 PM
*To:* xaled <xa...@web.de>
*Subject:* Re: [OpenSIPS-Users] Wrong number of children

Please apply the below patch, recompile and send again the startup logs:

diff --git a/net/net_tcp.c b/net/net_tcp.c
index 2dbea49..2d63940 100644
--- a/net/net_tcp.c
+++ b/net/net_tcp.c
@@ -1624,7 +1624,7 @@ int tcp_init(void)
/* first we do auto-detection to see if there are any TCP based
 * protocols loaded */
for ( i=PROTO_FIRST ; i+   if (is_tcp_based_proto(i)) {LM_INFO("enabling TCP for 
proto %d\n",i);tcp_disabled=0;break;}


if (tcp_disabled)
return 0;


Regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
   http://www.opensips-solutions.com
OpenSIPS Summit 2018
   http://www.opensips.org/events/Summit-2018Amsterdam

On 02/26/2018 08:14 PM, xaled wrote:

Hi Bogdan,

would a full debug log will be sufficient?

The config is spread across quite a few files.

Thanks,

Xaled

*From:*Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
*Sent:* Monday, February 26, 2018 5:25 PM
*To:* xaled <xa...@web.de> <mailto:xa...@web.de>; 'OpenSIPS users
mailling list' <users@lists.opensips.org>
<mailto:users@lists.opensips.org>
    *Subject:* Re: [OpenSIPS-Users] Wrong number of children

Hmm that is strange.

Could you send me (off list) your cfg to give it a try - I see
you use the 2.3.3 version , right ?

Regards,


Bogdan-Andrei Iancu

  


OpenSIPS Founder and Developer

   http://www.opensips-solutions.com

OpenSIPS Summit 2018

   http://www.opensips.org/events/Summit-2018Amsterdam

On 02/26/2018 06:27 PM, xaled wrote:

Nothing

root@dus-appsrv01:/etc/opensips# opensipsctl fifo ps

Process::  ID=0 PID=14966 Type=attendant

Process::  ID=1 PID=14967 Type=MI FIFO

Process::  ID=2 PID=14968 Type=time_keeper

Process::  ID=3 PID=14969 Type=timer

Process::  ID=4 PID=14970 Type=SIP receiver udp:1.2.3.4:5060

Process::  ID=5 PID=14975 Type=SIP receiver udp:1.2.3.4:5060

Process::  ID=6 PID=14976 Type=SIP receiver udp:1.2.3.4:5060

Process::  ID=7 PID=14977 Type=SIP receiver udp:1.2.3.4:5060

Process::  ID=8 PID=14978 Type=SIP receiver udp:1.2.3.4:5060

Process::  ID=9 PID=14979 Type=TCP receiver

Process::  ID=10 PID=14982 Type=TCP receiver

Process::  ID=11 PID=14984 Type=TCP receiver

Process::  ID=12 PID=14985 Type=TCP receiver

Process::  ID=13 PID=14986 Type=TCP receiver

Process::  ID=14 PID=14987 Type=TCP receiver

Process::  ID=15 PID=14988 Type=TCP receiver

Process::  ID=16 PID=14989 Type=TCP receiver

Process::  ID=17 PID=14991 Type=Timer handler

Re: [OpenSIPS-Users] Wrong number of children

2018-02-27 Thread Bogdan-Andrei Iancu


Thank you Xaled,

Based on the output you provided I managed to identify the issue. There 
is a tricky internal test that actually forces the TCP layer to start 
more or less all the time.

Let us have this fixed !! I will update you

Best regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  http://www.opensips-solutions.com
OpenSIPS Summit 2018
  http://www.opensips.org/events/Summit-2018Amsterdam

On 02/27/2018 06:30 PM, xaled wrote:


Hi Bogdan,

It’s a different server, but the same tcp issue:

2018-02-27T17:19:29.939207+01:00 dus-ivr01 opensips: DBG:core:main: 
Loaded 1 transport protocols


2018-02-27T17:19:29.939411+01:00 dus-ivr01 opensips: 
DBG:core:socket2str: 


2018-02-27T17:19:29.939630+01:00 dus-ivr01 opensips: 
INFO:core:tcp_init: enabling TCP for proto 5


2018-02-27T17:19:29.939842+01:00 dus-ivr01 opensips: 
DBG:core:ipc_register_handler: IPC type 0 [TCP reporting] registered with


handler 0x5f9fee

2018-02-27T17:19:29.940120+01:00 dus-ivr01 opensips: 
DBG:core:create_status_pipe: pipe created ? rc = 0, errno = Success


2018-02-27T17:19:29.940326+01:00 dus-ivr01 opensips: 
DBG:core:daemonize: waiting for status code from children


2018-02-27T17:19:29.940526+01:00 dus-ivr01 opensips: 
DBG:core:count_init_children: 15 children are going to be inited


2018-02-27T17:19:29.940724+01:00 dus-ivr01 
/usr/local/sbin/opensips[13076]: DBG:core:set_core_dump: core dump 
limits set to 18


446744073709551615

2018-02-27T17:19:29.940951+01:00 dus-ivr01 
/usr/local/sbin/opensips[13076]: NOTICE:core:main: version: opensips 
2.3.3 (x86_64/


linux)

Do you need full logs, or is this enough?

Thanks,

Xale

*From:*Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
*Sent:* Monday, February 26, 2018 10:38 PM
*To:* xaled <xa...@web.de>
*Subject:* Re: [OpenSIPS-Users] Wrong number of children

Please apply the below patch, recompile and send again the startup logs:

diff --git a/net/net_tcp.c b/net/net_tcp.c
index 2dbea49..2d63940 100644
--- a/net/net_tcp.c
+++ b/net/net_tcp.c
@@ -1624,7 +1624,7 @@ int tcp_init(void)
/* first we do auto-detection to see if there are any TCP based
 * protocols loaded */
for ( i=PROTO_FIRST ; i+   if (is_tcp_based_proto(i)) {LM_INFO("enabling TCP for 
proto %d\n",i);tcp_disabled=0;break;}


if (tcp_disabled)
return 0;


Regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
   http://www.opensips-solutions.com
OpenSIPS Summit 2018
   http://www.opensips.org/events/Summit-2018Amsterdam

On 02/26/2018 08:14 PM, xaled wrote:

Hi Bogdan,

would a full debug log will be sufficient?

The config is spread across quite a few files.

Thanks,

Xaled

*From:*Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
*Sent:* Monday, February 26, 2018 5:25 PM
*To:* xaled <xa...@web.de> <mailto:xa...@web.de>; 'OpenSIPS users
mailling list' <users@lists.opensips.org>
<mailto:users@lists.opensips.org>
    *Subject:* Re: [OpenSIPS-Users] Wrong number of children

Hmm that is strange.

Could you send me (off list) your cfg to give it a try - I see you
use the 2.3.3 version , right ?

Regards,


Bogdan-Andrei Iancu

  


OpenSIPS Founder and Developer

   http://www.opensips-solutions.com

OpenSIPS Summit 2018

   http://www.opensips.org/events/Summit-2018Amsterdam

On 02/26/2018 06:27 PM, xaled wrote:

Nothing

root@dus-appsrv01:/etc/opensips# opensipsctl fifo ps

Process::  ID=0 PID=14966 Type=attendant

Process::  ID=1 PID=14967 Type=MI FIFO

Process::  ID=2 PID=14968 Type=time_keeper

Process::  ID=3 PID=14969 Type=timer

Process::  ID=4 PID=14970 Type=SIP receiver udp:1.2.3.4:5060

Process::  ID=5 PID=14975 Type=SIP receiver udp:1.2.3.4:5060

Process::  ID=6 PID=14976 Type=SIP receiver udp:1.2.3.4:5060

Process::  ID=7 PID=14977 Type=SIP receiver udp:1.2.3.4:5060

Process::  ID=8 PID=14978 Type=SIP receiver udp:1.2.3.4:5060

Process::  ID=9 PID=14979 Type=TCP receiver

Process::  ID=10 PID=14982 Type=TCP receiver

Process::  ID=11 PID=14984 Type=TCP receiver

Process::  ID=12 PID=14985 Type=TCP receiver

Process::  ID=13 PID=14986 Type=TCP receiver

Process::  ID=14 PID=14987 Type=TCP receiver

Process::  ID=15 PID=14988 Type=TCP receiver

Process::  ID=16 PID=14989 Type=TCP receiver

Process::  ID=17 PID=14991 Type=Timer handler

Process::  ID=18 PID=14992 Type=TCP main

root@srv01:/etc/opensips# netstat -tlnp | grep opensips

root@srv01:/etc/opensips#

Thanks,

Xaled

*From:*Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
*Sent:* Monday, February 26, 2018 4:57 PM
*To:* xaled <xa...@web.de> <mailto:xa...@web.de>; 'OpenSIPS
users mailling li

Re: [OpenSIPS-Users] Wrong number of children

2018-02-27 Thread Rinor Hoxha

Hi Xaled,

Try adding *tcp_children=0* to the config file.

Br, Rinor
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Wrong number of children

2018-02-26 Thread xaled

Nothing

 

root@dus-appsrv01:/etc/opensips# opensipsctl fifo ps

Process::  ID=0 PID=14966 Type=attendant

Process::  ID=1 PID=14967 Type=MI FIFO

Process::  ID=2 PID=14968 Type=time_keeper

Process::  ID=3 PID=14969 Type=timer

Process::  ID=4 PID=14970 Type=SIP receiver udp:1.2.3.4:5060

Process::  ID=5 PID=14975 Type=SIP receiver udp:1.2.3.4:5060

Process::  ID=6 PID=14976 Type=SIP receiver udp:1.2.3.4:5060

Process::  ID=7 PID=14977 Type=SIP receiver udp:1.2.3.4:5060

Process::  ID=8 PID=14978 Type=SIP receiver udp:1.2.3.4:5060

Process::  ID=9 PID=14979 Type=TCP receiver

Process::  ID=10 PID=14982 Type=TCP receiver

Process::  ID=11 PID=14984 Type=TCP receiver

Process::  ID=12 PID=14985 Type=TCP receiver

Process::  ID=13 PID=14986 Type=TCP receiver

Process::  ID=14 PID=14987 Type=TCP receiver

Process::  ID=15 PID=14988 Type=TCP receiver

Process::  ID=16 PID=14989 Type=TCP receiver

Process::  ID=17 PID=14991 Type=Timer handler

Process::  ID=18 PID=14992 Type=TCP main

root@srv01:/etc/opensips# netstat -tlnp | grep opensips

root@srv01:/etc/opensips#

 

Thanks,

Xaled

From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org] 
Sent: Monday, February 26, 2018 4:57 PM
To: xaled <xa...@web.de>; 'OpenSIPS users mailling list' 
<users@lists.opensips.org>
Subject: Re: [OpenSIPS-Users] Wrong number of children

 

If you do "netstat -tlnp | grep opensips", what do you get ?

The TCP layer automatically enable itself if a TCP-based protocol is used from 
the OpenSIPS config (as listener), like SIP TCP/TLS/WS/WSS , HEP or BIN.

Regards,



Bogdan-Andrei Iancu
 
OpenSIPS Founder and Developer
  http://www.opensips-solutions.com
OpenSIPS Summit 2018
  http://www.opensips.org/events/Summit-2018Amsterdam

On 02/26/2018 05:53 PM, xaled wrote:

Hi Bogdan,

 

nope, non of them.

 

Greetings,

Xaled

 

From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org] 
Sent: Monday, February 26, 2018 4:41 PM
To: OpenSIPS users mailling list  <mailto:users@lists.opensips.org> 
<users@lists.opensips.org>; xaled  <mailto:xa...@web.de> <xa...@web.de>
Subject: Re: [OpenSIPS-Users] Wrong number of children

 

Hi Xaled,

Do you use HEP for tracing or BIN for replication ?

Regards,




Bogdan-Andrei Iancu
 
OpenSIPS Founder and Developer
  http://www.opensips-solutions.com
OpenSIPS Summit 2018
  http://www.opensips.org/events/Summit-2018Amsterdam

On 02/26/2018 01:36 PM, xaled wrote:

Hi Callum,

 

that helped thanks. 

I have 8 TCP receivers and one TCP main process that I did not expected as I 
only listen on udp.

Will have to understand the TCP spawn logic.

 

Greetings,

Xaled

 

From: Users [mailto:users-boun...@lists.opensips.org] On Behalf Of Callum Guy
Sent: Friday, February 23, 2018 2:42 PM
To: OpenSIPS users mailling list  <mailto:users@lists.opensips.org> 
<users@lists.opensips.org>
Subject: Re: [OpenSIPS-Users] Wrong number of children

 

Hi Xaled,

 

If you have the FIFO module loaded you can run "opensipsctl fifo ps" on the 
instance to see full details of each process.

 

https://www.opensips.org/Documentation/Interface-CoreMI-2-2#toc7

 

Hope that helps,

 

Callum

 

On Fri, Feb 23, 2018 at 1:35 PM Daniel Zanutti <daniel.zanu...@gmail.com 
<mailto:daniel.zanu...@gmail.com> > wrote:

Hi

 

You should have 5 per interface + some internal control threads. I'm not sure 
exactly.

 

Regards

 

On Fri, Feb 23, 2018 at 9:25 AM, xaled <xa...@web.de <mailto:xa...@web.de> > 
wrote:

Hi 

 

I have configured 5 children in  opensips.cfg, but 16 get logged and 18 
initiated what could be the cause of it?

I search for word children in opensips directory and it only comes ones in 
opensips.conf.

 

children=5

 

Feb 23 13:07:09 srv01 opensips: DBG:core:daemonize: waiting for status code 
from children

Feb 23 13:07:09 srv01 opensips: DBG:core:count_init_children: 16 children are 
going to be inited

 

root@dus-appsrv01:/var/log/opensips# ps ax|grep sips

14854 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4

14856 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4

14857 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4

14858 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4

14861 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4

14862 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4

14863 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4

14864 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4

14865 ?S  0:0

Re: [OpenSIPS-Users] Wrong number of children

2018-02-26 Thread Bogdan-Andrei Iancu


Hmm that is strange.

Could you send me (off list) your cfg to give it a try - I see you use 
the 2.3.3 version , right ?


Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  http://www.opensips-solutions.com
OpenSIPS Summit 2018
  http://www.opensips.org/events/Summit-2018Amsterdam

On 02/26/2018 06:27 PM, xaled wrote:


Nothing

root@dus-appsrv01:/etc/opensips# opensipsctl fifo ps

Process::  ID=0 PID=14966 Type=attendant

Process::  ID=1 PID=14967 Type=MI FIFO

Process::  ID=2 PID=14968 Type=time_keeper

Process::  ID=3 PID=14969 Type=timer

Process::  ID=4 PID=14970 Type=SIP receiver udp:1.2.3.4:5060

Process::  ID=5 PID=14975 Type=SIP receiver udp:1.2.3.4:5060

Process::  ID=6 PID=14976 Type=SIP receiver udp:1.2.3.4:5060

Process::  ID=7 PID=14977 Type=SIP receiver udp:1.2.3.4:5060

Process::  ID=8 PID=14978 Type=SIP receiver udp:1.2.3.4:5060

Process::  ID=9 PID=14979 Type=TCP receiver

Process::  ID=10 PID=14982 Type=TCP receiver

Process::  ID=11 PID=14984 Type=TCP receiver

Process::  ID=12 PID=14985 Type=TCP receiver

Process::  ID=13 PID=14986 Type=TCP receiver

Process::  ID=14 PID=14987 Type=TCP receiver

Process::  ID=15 PID=14988 Type=TCP receiver

Process::  ID=16 PID=14989 Type=TCP receiver

Process::  ID=17 PID=14991 Type=Timer handler

Process::  ID=18 PID=14992 Type=TCP main

root@srv01:/etc/opensips# netstat -tlnp | grep opensips

root@srv01:/etc/opensips#

Thanks,

Xaled

*From:*Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
*Sent:* Monday, February 26, 2018 4:57 PM
*To:* xaled <xa...@web.de>; 'OpenSIPS users mailling list' 
<users@lists.opensips.org>

*Subject:* Re: [OpenSIPS-Users] Wrong number of children

If you do "netstat -tlnp | grep opensips", what do you get ?

The TCP layer automatically enable itself if a TCP-based protocol is 
used from the OpenSIPS config (as listener), like SIP TCP/TLS/WS/WSS , 
HEP or BIN.


Regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
   http://www.opensips-solutions.com
OpenSIPS Summit 2018
   http://www.opensips.org/events/Summit-2018Amsterdam

On 02/26/2018 05:53 PM, xaled wrote:

Hi Bogdan,

nope, non of them.

Greetings,

Xaled

*From:*Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
*Sent:* Monday, February 26, 2018 4:41 PM
*To:* OpenSIPS users mailling list <users@lists.opensips.org>
<mailto:users@lists.opensips.org>; xaled <xa...@web.de>
<mailto:xa...@web.de>
    *Subject:* Re: [OpenSIPS-Users] Wrong number of children

Hi Xaled,

Do you use HEP for tracing or BIN for replication ?

Regards,


Bogdan-Andrei Iancu

  


OpenSIPS Founder and Developer

   http://www.opensips-solutions.com

OpenSIPS Summit 2018

   http://www.opensips.org/events/Summit-2018Amsterdam

On 02/26/2018 01:36 PM, xaled wrote:

Hi Callum,

that helped thanks.

I have 8 TCP receivers and one TCP main process that I did not
expected as I only listen on udp.

Will have to understand the TCP spawn logic.

Greetings,

Xaled




___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Wrong number of children

2018-02-26 Thread Bogdan-Andrei Iancu


If you do "netstat -tlnp | grep opensips", what do you get ?

The TCP layer automatically enable itself if aTCP-based protocol is used 
from the OpenSIPS config (as listener), like SIP TCP/TLS/WS/WSS , HEP or 
BIN.


Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  http://www.opensips-solutions.com
OpenSIPS Summit 2018
  http://www.opensips.org/events/Summit-2018Amsterdam

On 02/26/2018 05:53 PM, xaled wrote:


Hi Bogdan,

nope, non of them.

Greetings,

Xaled

*From:*Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
*Sent:* Monday, February 26, 2018 4:41 PM
*To:* OpenSIPS users mailling list <users@lists.opensips.org>; xaled 
<xa...@web.de>

*Subject:* Re: [OpenSIPS-Users] Wrong number of children

Hi Xaled,

Do you use HEP for tracing or BIN for replication ?

Regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
   http://www.opensips-solutions.com
OpenSIPS Summit 2018
   http://www.opensips.org/events/Summit-2018Amsterdam

On 02/26/2018 01:36 PM, xaled wrote:

Hi Callum,

that helped thanks.

I have 8 TCP receivers and one TCP main process that I did not
expected as I only listen on udp.

Will have to understand the TCP spawn logic.

Greetings,

Xaled

*From:*Users [mailto:users-boun...@lists.opensips.org] *On Behalf
Of *Callum Guy
*Sent:* Friday, February 23, 2018 2:42 PM
*To:* OpenSIPS users mailling list <users@lists.opensips.org>
<mailto:users@lists.opensips.org>
    *Subject:* Re: [OpenSIPS-Users] Wrong number of children

Hi Xaled,

If you have the FIFO module loaded you can run "opensipsctl fifo
ps" on the instance to see full details of each process.

https://www.opensips.org/Documentation/Interface-CoreMI-2-2#toc7

Hope that helps,

Callum

On Fri, Feb 23, 2018 at 1:35 PM Daniel Zanutti
<daniel.zanu...@gmail.com <mailto:daniel.zanu...@gmail.com>> wrote:

Hi

You should have 5 per interface + some internal control
threads. I'm not sure exactly.

Regards

On Fri, Feb 23, 2018 at 9:25 AM, xaled <xa...@web.de
<mailto:xa...@web.de>> wrote:

Hi

I have configured 5 children in  opensips.cfg, but 16 get
logged and 18 initiated what could be the cause of it?

I search for word children in opensips directory and it
only comes ones in opensips.conf.

children=5

Feb 23 13:07:09 srv01 opensips: DBG:core:daemonize:
waiting for status code from children

Feb 23 13:07:09 srv01 opensips:
DBG:core:count_init_children: 16 children are going to be
inited

root@dus-appsrv01:/var/log/opensips# ps ax|grep sips

14854 ?S  0:00 /usr/sbin/opensips -P
/run/opensips/opensips.pid -f /etc/opensips/opensips.cfg
-m 64 -M 4

14856 ?S  0:00 /usr/sbin/opensips -P
/run/opensips/opensips.pid -f /etc/opensips/opensips.cfg
-m 64 -M 4

14857 ?S  0:00 /usr/sbin/opensips -P
/run/opensips/opensips.pid -f /etc/opensips/opensips.cfg
-m 64 -M 4

14858 ?S  0:00 /usr/sbin/opensips -P
/run/opensips/opensips.pid -f /etc/opensips/opensips.cfg
-m 64 -M 4

14861 ?S  0:00 /usr/sbin/opensips -P
/run/opensips/opensips.pid -f /etc/opensips/opensips.cfg
-m 64 -M 4

14862 ?S  0:00 /usr/sbin/opensips -P
/run/opensips/opensips.pid -f /etc/opensips/opensips.cfg
-m 64 -M 4

14863 ?S  0:00 /usr/sbin/opensips -P
/run/opensips/opensips.pid -f /etc/opensips/opensips.cfg
-m 64 -M 4

14864 ?S  0:00 /usr/sbin/opensips -P
/run/opensips/opensips.pid -f /etc/opensips/opensips.cfg
-m 64 -M 4

14865 ?S  0:00 /usr/sbin/opensips -P
/run/opensips/opensips.pid -f /etc/opensips/opensips.cfg
-m 64 -M 4

14867 ?S  0:00 /usr/sbin/opensips -P
/run/opensips/opensips.pid -f /etc/opensips/opensips.cfg
-m 64 -M 4

14869 ?S  0:00 /usr/sbin/opensips -P
/run/opensips/opensips.pid -f /etc/opensips/opensips.cfg
-m 64 -M 4

14870 ?S  0:00 /usr/sbin/opensips -P
/run/opensips/opensips.pid -f /etc/opensips/opensips.cfg
-m 64 -M 4

14871 ?S  0:00 /usr/sbin/opensips -P
/run/opensips/opensips.pid -f /etc/opensips/opensips.cfg
-m 64 -M 4

14872 ?S  0:00 /usr/sbin/opensips -P
/run/opensips/opensips.pid -f /etc/opensips/opensips.cfg
-m 64 -M 4

14874 ?S

Re: [OpenSIPS-Users] Wrong number of children

2018-02-26 Thread xaled

Hi Bogdan,

 

nope, non of them.

 

Greetings,

Xaled

 

From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org] 
Sent: Monday, February 26, 2018 4:41 PM
To: OpenSIPS users mailling list <users@lists.opensips.org>; xaled 
<xa...@web.de>
Subject: Re: [OpenSIPS-Users] Wrong number of children

 

Hi Xaled,

Do you use HEP for tracing or BIN for replication ?

Regards,



Bogdan-Andrei Iancu
 
OpenSIPS Founder and Developer
  http://www.opensips-solutions.com
OpenSIPS Summit 2018
  http://www.opensips.org/events/Summit-2018Amsterdam

On 02/26/2018 01:36 PM, xaled wrote:

Hi Callum,

 

that helped thanks. 

I have 8 TCP receivers and one TCP main process that I did not expected as I 
only listen on udp.

Will have to understand the TCP spawn logic.

 

Greetings,

Xaled

 

From: Users [mailto:users-boun...@lists.opensips.org] On Behalf Of Callum Guy
Sent: Friday, February 23, 2018 2:42 PM
To: OpenSIPS users mailling list  <mailto:users@lists.opensips.org> 
<users@lists.opensips.org>
Subject: Re: [OpenSIPS-Users] Wrong number of children

 

Hi Xaled,

 

If you have the FIFO module loaded you can run "opensipsctl fifo ps" on the 
instance to see full details of each process.

 

https://www.opensips.org/Documentation/Interface-CoreMI-2-2#toc7

 

Hope that helps,

 

Callum

 

On Fri, Feb 23, 2018 at 1:35 PM Daniel Zanutti <daniel.zanu...@gmail.com 
<mailto:daniel.zanu...@gmail.com> > wrote:

Hi

 

You should have 5 per interface + some internal control threads. I'm not sure 
exactly.

 

Regards

 

On Fri, Feb 23, 2018 at 9:25 AM, xaled <xa...@web.de <mailto:xa...@web.de> > 
wrote:

Hi 

 

I have configured 5 children in  opensips.cfg, but 16 get logged and 18 
initiated what could be the cause of it?

I search for word children in opensips directory and it only comes ones in 
opensips.conf.

 

children=5

 

Feb 23 13:07:09 srv01 opensips: DBG:core:daemonize: waiting for status code 
from children

Feb 23 13:07:09 srv01 opensips: DBG:core:count_init_children: 16 children are 
going to be inited

 

root@dus-appsrv01:/var/log/opensips# ps ax|grep sips

14854 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4

14856 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4

14857 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4

14858 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4

14861 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4

14862 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4

14863 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4

14864 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4

14865 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4

14867 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4

14869 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4

14870 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4

14871 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4

14872 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4

14874 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4

14875 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4

14876 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4

14877 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4

 

With commended children parameter I get 19 children in the log and 21 in 
reality:

 

Feb 23 13:13:24 dus-appsrv01 opensips: DBG:core:daemonize: waiting for status 
code from children

Feb 23 13:13:24 dus-appsrv01 opensips: DBG:core:count_init_children: 19 
children are going to be inited

 

root@srv01:/var/log/opensips# ps ax|grep sips

14723 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4

14725 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4

14726 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -

Re: [OpenSIPS-Users] Wrong number of children

2018-02-26 Thread Bogdan-Andrei Iancu


Hi Xaled,

Do you use HEP for tracing or BIN for replication ?

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  http://www.opensips-solutions.com
OpenSIPS Summit 2018
  http://www.opensips.org/events/Summit-2018Amsterdam

On 02/26/2018 01:36 PM, xaled wrote:


Hi Callum,

that helped thanks.

I have 8 TCP receivers and one TCP main process that I did not 
expected as I only listen on udp.


Will have to understand the TCP spawn logic.

Greetings,

Xaled

*From:*Users [mailto:users-boun...@lists.opensips.org] *On Behalf Of 
*Callum Guy

*Sent:* Friday, February 23, 2018 2:42 PM
*To:* OpenSIPS users mailling list <users@lists.opensips.org>
*Subject:* Re: [OpenSIPS-Users] Wrong number of children

Hi Xaled,

If you have the FIFO module loaded you can run "opensipsctl fifo ps" 
on the instance to see full details of each process.


https://www.opensips.org/Documentation/Interface-CoreMI-2-2#toc7

Hope that helps,

Callum

On Fri, Feb 23, 2018 at 1:35 PM Daniel Zanutti 
<daniel.zanu...@gmail.com <mailto:daniel.zanu...@gmail.com>> wrote:


Hi

You should have 5 per interface + some internal control threads.
I'm not sure exactly.

Regards

On Fri, Feb 23, 2018 at 9:25 AM, xaled <xa...@web.de
<mailto:xa...@web.de>> wrote:

Hi

I have configured 5 children in  opensips.cfg, but 16 get
logged and 18 initiated what could be the cause of it?

I search for word children in opensips directory and it only
comes ones in opensips.conf.

children=5

Feb 23 13:07:09 srv01 opensips: DBG:core:daemonize: waiting
for status code from children

Feb 23 13:07:09 srv01 opensips: DBG:core:count_init_children:
16 children are going to be inited

root@dus-appsrv01:/var/log/opensips# ps ax|grep sips

14854 ?S  0:00 /usr/sbin/opensips -P
/run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64
-M 4

14856 ?S  0:00 /usr/sbin/opensips -P
/run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64
-M 4

14857 ?S  0:00 /usr/sbin/opensips -P
/run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64
-M 4

14858 ?S  0:00 /usr/sbin/opensips -P
/run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64
-M 4

14861 ?S  0:00 /usr/sbin/opensips -P
/run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64
-M 4

14862 ?S  0:00 /usr/sbin/opensips -P
/run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64
-M 4

14863 ?S  0:00 /usr/sbin/opensips -P
/run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64
-M 4

14864 ?S  0:00 /usr/sbin/opensips -P
/run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64
-M 4

14865 ?S  0:00 /usr/sbin/opensips -P
/run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64
-M 4

14867 ?S  0:00 /usr/sbin/opensips -P
/run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64
-M 4

14869 ?S  0:00 /usr/sbin/opensips -P
/run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64
-M 4

14870 ?S  0:00 /usr/sbin/opensips -P
/run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64
-M 4

14871 ?S  0:00 /usr/sbin/opensips -P
/run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64
-M 4

14872 ?S  0:00 /usr/sbin/opensips -P
/run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64
-M 4

14874 ?S  0:00 /usr/sbin/opensips -P
/run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64
-M 4

14875 ?S  0:00 /usr/sbin/opensips -P
/run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64
-M 4

14876 ?S  0:00 /usr/sbin/opensips -P
/run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64
-M 4

14877 ?S  0:00 /usr/sbin/opensips -P
/run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64
-M 4

With commended children parameter I get 19 children in the log
and 21 in reality:

Feb 23 13:13:24 dus-appsrv01 opensips: DBG:core:daemonize:
waiting for status code from children

Feb 23 13:13:24 dus-appsrv01 opensips:
DBG:core:count_init_children: 19 children are going to be inited

root@srv01:/var/log/opensips# ps ax|grep sips

14723 ?S  0:00 /usr/sbin/opensips -P
/run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64
-M 4

14725 ?S  0:00 /us

Re: [OpenSIPS-Users] Wrong number of children

2018-02-26 Thread Ben Newlin

I am seeing this as well while testing out my migration to 2.3.3.

In 1.11, I used the disable_tcp parameter since I don’t use TCP for anything. 
That parameter is no longer available in 2.x and now I get a large number of 
TCP receiver threads starting automatically with OpenSIPS even though I am not 
using TCP and have no modules loaded that use TCP, to my knowledge.

This is very concerning for me that there no longer seems to be any way to stop 
OpenSIPS from starting these TCP receivers in 2.3.3.

Ben Newlin

From: Users <users-boun...@lists.opensips.org> on behalf of xaled <xa...@web.de>
Reply-To: OpenSIPS users mailling list <users@lists.opensips.org>
Date: Monday, February 26, 2018 at 6:29 AM
To: 'OpenSIPS users mailling list' <users@lists.opensips.org>
Subject: Re: [OpenSIPS-Users] Wrong number of children

Hi Callum,

that helped thanks.
I have 8 TCP receivers and one TCP main process that I did not expected as I 
only listen on udp.
Will have to understand the TCP spawn logic.

Greetings,
Xaled

From: Users [mailto:users-boun...@lists.opensips.org] On Behalf Of Callum Guy
Sent: Friday, February 23, 2018 2:42 PM
To: OpenSIPS users mailling list <users@lists.opensips.org>
Subject: Re: [OpenSIPS-Users] Wrong number of children

Hi Xaled,

If you have the FIFO module loaded you can run "opensipsctl fifo ps" on the 
instance to see full details of each process.

https://www.opensips.org/Documentation/Interface-CoreMI-2-2#toc7<https://www.opensips.org/Documentation/Interface-CoreMI-2-2#toc7>

Hope that helps,

Callum

On Fri, Feb 23, 2018 at 1:35 PM Daniel Zanutti 
<daniel.zanu...@gmail.com<mailto:daniel.zanu...@gmail.com>> wrote:
Hi

You should have 5 per interface + some internal control threads. I'm not sure 
exactly.

Regards

On Fri, Feb 23, 2018 at 9:25 AM, xaled <xa...@web.de<mailto:xa...@web.de>> 
wrote:
Hi

I have configured 5 children in  opensips.cfg, but 16 get logged and 18 
initiated what could be the cause of it?
I search for word children in opensips directory and it only comes ones in 
opensips.conf.

children=5

Feb 23 13:07:09 srv01 opensips: DBG:core:daemonize: waiting for status code 
from children
Feb 23 13:07:09 srv01 opensips: DBG:core:count_init_children: 16 children are 
going to be inited

root@dus-appsrv01:/var/log/opensips# ps ax|grep sips
14854 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4
14856 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4
14857 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4
14858 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4
14861 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4
14862 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4
14863 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4
14864 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4
14865 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4
14867 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4
14869 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4
14870 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4
14871 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4
14872 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4
14874 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4
14875 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4
14876 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4
14877 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4

With commended children parameter I get 19 children in the log and 21 in 
reality:

Feb 23 13:13:24 dus-appsrv01 opensips: DBG:core:daemonize: waiting for status 
code from children
Feb 23 13:13:24 dus-appsrv01 opensips: DBG:core:count_init_children: 19 
children are going to be inited

root@srv01:/var/log/opensips# ps ax|grep sips
14723 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4
14725 ?S  0:00 /usr/sbin

Re: [OpenSIPS-Users] Wrong number of children

2018-02-26 Thread xaled

Hi Callum,

 

that helped thanks. 

I have 8 TCP receivers and one TCP main process that I did not expected as I 
only listen on udp.

Will have to understand the TCP spawn logic.

 

Greetings,

Xaled

 

From: Users [mailto:users-boun...@lists.opensips.org] On Behalf Of Callum Guy
Sent: Friday, February 23, 2018 2:42 PM
To: OpenSIPS users mailling list <users@lists.opensips.org>
Subject: Re: [OpenSIPS-Users] Wrong number of children

 

Hi Xaled,

 

If you have the FIFO module loaded you can run "opensipsctl fifo ps" on the 
instance to see full details of each process.

 

https://www.opensips.org/Documentation/Interface-CoreMI-2-2#toc7

 

Hope that helps,

 

Callum

 

On Fri, Feb 23, 2018 at 1:35 PM Daniel Zanutti <daniel.zanu...@gmail.com 
<mailto:daniel.zanu...@gmail.com> > wrote:

Hi

 

You should have 5 per interface + some internal control threads. I'm not sure 
exactly.

 

Regards

 

On Fri, Feb 23, 2018 at 9:25 AM, xaled <xa...@web.de <mailto:xa...@web.de> > 
wrote:

Hi 

 

I have configured 5 children in  opensips.cfg, but 16 get logged and 18 
initiated what could be the cause of it?

I search for word children in opensips directory and it only comes ones in 
opensips.conf.

 

children=5

 

Feb 23 13:07:09 srv01 opensips: DBG:core:daemonize: waiting for status code 
from children

Feb 23 13:07:09 srv01 opensips: DBG:core:count_init_children: 16 children are 
going to be inited

 

root@dus-appsrv01:/var/log/opensips# ps ax|grep sips

14854 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4

14856 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4

14857 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4

14858 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4

14861 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4

14862 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4

14863 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4

14864 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4

14865 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4

14867 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4

14869 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4

14870 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4

14871 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4

14872 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4

14874 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4

14875 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4

14876 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4

14877 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4

 

With commended children parameter I get 19 children in the log and 21 in 
reality:

 

Feb 23 13:13:24 dus-appsrv01 opensips: DBG:core:daemonize: waiting for status 
code from children

Feb 23 13:13:24 dus-appsrv01 opensips: DBG:core:count_init_children: 19 
children are going to be inited

 

root@srv01:/var/log/opensips# ps ax|grep sips

14723 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4

14725 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4

14726 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4

14727 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4

14730 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4

14731 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4

14732 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4

14733 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f 
/etc/opensips/opensips.cfg -m 64 -M 4

14734 ?S  0:00 /usr/sbi

Re: [OpenSIPS-Users] Wrong number of children

2018-02-23 Thread Callum Guy

Hi Xaled,

If you have the FIFO module loaded you can run "opensipsctl fifo ps" on the
instance to see full details of each process.

https://www.opensips.org/Documentation/Interface-CoreMI-2-2#toc7

Hope that helps,

Callum

On Fri, Feb 23, 2018 at 1:35 PM Daniel Zanutti 
wrote:

> Hi
>
> You should have 5 per interface + some internal control threads. I'm not
> sure exactly.
>
> Regards
>
> On Fri, Feb 23, 2018 at 9:25 AM, xaled  wrote:
>
>> Hi
>>
>>
>>
>> I have configured 5 children in  opensips.cfg, but 16 get logged and 18
>> initiated what could be the cause of it?
>>
>> I search for word children in opensips directory and it only comes ones
>> in opensips.conf.
>>
>>
>>
>> children=5
>>
>>
>>
>> Feb 23 13:07:09 srv01 opensips: DBG:core:daemonize: waiting for status
>> code from children
>>
>> Feb 23 13:07:09 srv01 opensips: DBG:core:count_init_children: 16 children
>> are going to be inited
>>
>>
>>
>> root@dus-appsrv01:/var/log/opensips# ps ax|grep sips
>>
>> 14854 ?S  0:00 /usr/sbin/opensips -P
>> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>>
>> 14856 ?S  0:00 /usr/sbin/opensips -P
>> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>>
>> 14857 ?S  0:00 /usr/sbin/opensips -P
>> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>>
>> 14858 ?S  0:00 /usr/sbin/opensips -P
>> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>>
>> 14861 ?S  0:00 /usr/sbin/opensips -P
>> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>>
>> 14862 ?S  0:00 /usr/sbin/opensips -P
>> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>>
>> 14863 ?S  0:00 /usr/sbin/opensips -P
>> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>>
>> 14864 ?S  0:00 /usr/sbin/opensips -P
>> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>>
>> 14865 ?S  0:00 /usr/sbin/opensips -P
>> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>>
>> 14867 ?S  0:00 /usr/sbin/opensips -P
>> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>>
>> 14869 ?S  0:00 /usr/sbin/opensips -P
>> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>>
>> 14870 ?S  0:00 /usr/sbin/opensips -P
>> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>>
>> 14871 ?S  0:00 /usr/sbin/opensips -P
>> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>>
>> 14872 ?S  0:00 /usr/sbin/opensips -P
>> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>>
>> 14874 ?S  0:00 /usr/sbin/opensips -P
>> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>>
>> 14875 ?S  0:00 /usr/sbin/opensips -P
>> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>>
>> 14876 ?S  0:00 /usr/sbin/opensips -P
>> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>>
>> 14877 ?S  0:00 /usr/sbin/opensips -P
>> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>>
>>
>>
>> With commended children parameter I get 19 children in the log and 21 in
>> reality:
>>
>>
>>
>> Feb 23 13:13:24 dus-appsrv01 opensips: DBG:core:daemonize: waiting for
>> status code from children
>>
>> Feb 23 13:13:24 dus-appsrv01 opensips: DBG:core:count_init_children: 19
>> children are going to be inited
>>
>>
>>
>> root@srv01:/var/log/opensips# ps ax|grep sips
>>
>> 14723 ?S  0:00 /usr/sbin/opensips -P
>> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>>
>> 14725 ?S  0:00 /usr/sbin/opensips -P
>> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>>
>> 14726 ?S  0:00 /usr/sbin/opensips -P
>> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>>
>> 14727 ?S  0:00 /usr/sbin/opensips -P
>> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>>
>> 14730 ?S  0:00 /usr/sbin/opensips -P
>> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>>
>> 14731 ?S  0:00 /usr/sbin/opensips -P
>> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>>
>> 14732 ?S  0:00 /usr/sbin/opensips -P
>> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>>
>> 14733 ?S  0:00 /usr/sbin/opensips -P
>> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>>
>> 14734 ?S  0:00 /usr/sbin/opensips -P
>> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>>
>> 14736 ?S  0:00 /usr/sbin/opensips -P
>> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>>
>> 14737 ?S  0:00 /usr/sbin/opensips -P
>>

Re: [OpenSIPS-Users] Wrong number of children

2018-02-23 Thread Daniel Zanutti

Hi

You should have 5 per interface + some internal control threads. I'm not
sure exactly.

Regards

On Fri, Feb 23, 2018 at 9:25 AM, xaled  wrote:

> Hi
>
>
>
> I have configured 5 children in  opensips.cfg, but 16 get logged and 18
> initiated what could be the cause of it?
>
> I search for word children in opensips directory and it only comes ones in
> opensips.conf.
>
>
>
> children=5
>
>
>
> Feb 23 13:07:09 srv01 opensips: DBG:core:daemonize: waiting for status
> code from children
>
> Feb 23 13:07:09 srv01 opensips: DBG:core:count_init_children: 16 children
> are going to be inited
>
>
>
> root@dus-appsrv01:/var/log/opensips# ps ax|grep sips
>
> 14854 ?S  0:00 /usr/sbin/opensips -P
> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>
> 14856 ?S  0:00 /usr/sbin/opensips -P
> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>
> 14857 ?S  0:00 /usr/sbin/opensips -P
> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>
> 14858 ?S  0:00 /usr/sbin/opensips -P
> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>
> 14861 ?S  0:00 /usr/sbin/opensips -P
> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>
> 14862 ?S  0:00 /usr/sbin/opensips -P
> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>
> 14863 ?S  0:00 /usr/sbin/opensips -P
> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>
> 14864 ?S  0:00 /usr/sbin/opensips -P
> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>
> 14865 ?S  0:00 /usr/sbin/opensips -P
> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>
> 14867 ?S  0:00 /usr/sbin/opensips -P
> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>
> 14869 ?S  0:00 /usr/sbin/opensips -P
> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>
> 14870 ?S  0:00 /usr/sbin/opensips -P
> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>
> 14871 ?S  0:00 /usr/sbin/opensips -P
> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>
> 14872 ?S  0:00 /usr/sbin/opensips -P
> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>
> 14874 ?S  0:00 /usr/sbin/opensips -P
> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>
> 14875 ?S  0:00 /usr/sbin/opensips -P
> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>
> 14876 ?S  0:00 /usr/sbin/opensips -P
> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>
> 14877 ?S  0:00 /usr/sbin/opensips -P
> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>
>
>
> With commended children parameter I get 19 children in the log and 21 in
> reality:
>
>
>
> Feb 23 13:13:24 dus-appsrv01 opensips: DBG:core:daemonize: waiting for
> status code from children
>
> Feb 23 13:13:24 dus-appsrv01 opensips: DBG:core:count_init_children: 19
> children are going to be inited
>
>
>
> root@srv01:/var/log/opensips# ps ax|grep sips
>
> 14723 ?S  0:00 /usr/sbin/opensips -P
> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>
> 14725 ?S  0:00 /usr/sbin/opensips -P
> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>
> 14726 ?S  0:00 /usr/sbin/opensips -P
> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>
> 14727 ?S  0:00 /usr/sbin/opensips -P
> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>
> 14730 ?S  0:00 /usr/sbin/opensips -P
> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>
> 14731 ?S  0:00 /usr/sbin/opensips -P
> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>
> 14732 ?S  0:00 /usr/sbin/opensips -P
> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>
> 14733 ?S  0:00 /usr/sbin/opensips -P
> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>
> 14734 ?S  0:00 /usr/sbin/opensips -P
> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>
> 14736 ?S  0:00 /usr/sbin/opensips -P
> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>
> 14737 ?S  0:00 /usr/sbin/opensips -P
> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>
> 14738 ?S  0:00 /usr/sbin/opensips -P
> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>
> 14739 ?S  0:00 /usr/sbin/opensips -P
> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>
> 14741 ?S  0:00 /usr/sbin/opensips -P
> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
>
> 14742 ?S

[OpenSIPS-Users] Wrong number of children

2018-02-23 Thread xaled

Hi 

 

I have configured 5 children in  opensips.cfg, but 16 get logged and 18
initiated what could be the cause of it?

I search for word children in opensips directory and it only comes ones in
opensips.conf.

 

children=5

 

Feb 23 13:07:09 srv01 opensips: DBG:core:daemonize: waiting for status code
from children

Feb 23 13:07:09 srv01 opensips: DBG:core:count_init_children: 16 children
are going to be inited

 

root@dus-appsrv01:/var/log/opensips# ps ax|grep sips

14854 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid
-f /etc/opensips/opensips.cfg -m 64 -M 4

14856 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid
-f /etc/opensips/opensips.cfg -m 64 -M 4

14857 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid
-f /etc/opensips/opensips.cfg -m 64 -M 4

14858 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid
-f /etc/opensips/opensips.cfg -m 64 -M 4

14861 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid
-f /etc/opensips/opensips.cfg -m 64 -M 4

14862 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid
-f /etc/opensips/opensips.cfg -m 64 -M 4

14863 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid
-f /etc/opensips/opensips.cfg -m 64 -M 4

14864 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid
-f /etc/opensips/opensips.cfg -m 64 -M 4

14865 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid
-f /etc/opensips/opensips.cfg -m 64 -M 4

14867 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid
-f /etc/opensips/opensips.cfg -m 64 -M 4

14869 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid
-f /etc/opensips/opensips.cfg -m 64 -M 4

14870 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid
-f /etc/opensips/opensips.cfg -m 64 -M 4

14871 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid
-f /etc/opensips/opensips.cfg -m 64 -M 4

14872 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid
-f /etc/opensips/opensips.cfg -m 64 -M 4

14874 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid
-f /etc/opensips/opensips.cfg -m 64 -M 4

14875 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid
-f /etc/opensips/opensips.cfg -m 64 -M 4

14876 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid
-f /etc/opensips/opensips.cfg -m 64 -M 4

14877 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid
-f /etc/opensips/opensips.cfg -m 64 -M 4

 

With commended children parameter I get 19 children in the log and 21 in
reality:

 

Feb 23 13:13:24 dus-appsrv01 opensips: DBG:core:daemonize: waiting for
status code from children

Feb 23 13:13:24 dus-appsrv01 opensips: DBG:core:count_init_children: 19
children are going to be inited

 

root@srv01:/var/log/opensips# ps ax|grep sips

14723 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid
-f /etc/opensips/opensips.cfg -m 64 -M 4

14725 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid
-f /etc/opensips/opensips.cfg -m 64 -M 4

14726 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid
-f /etc/opensips/opensips.cfg -m 64 -M 4

14727 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid
-f /etc/opensips/opensips.cfg -m 64 -M 4

14730 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid
-f /etc/opensips/opensips.cfg -m 64 -M 4

14731 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid
-f /etc/opensips/opensips.cfg -m 64 -M 4

14732 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid
-f /etc/opensips/opensips.cfg -m 64 -M 4

14733 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid
-f /etc/opensips/opensips.cfg -m 64 -M 4

14734 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid
-f /etc/opensips/opensips.cfg -m 64 -M 4

14736 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid
-f /etc/opensips/opensips.cfg -m 64 -M 4

14737 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid
-f /etc/opensips/opensips.cfg -m 64 -M 4

14738 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid
-f /etc/opensips/opensips.cfg -m 64 -M 4

14739 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid
-f /etc/opensips/opensips.cfg -m 64 -M 4

14741 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid
-f /etc/opensips/opensips.cfg -m 64 -M 4

14742 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid
-f /etc/opensips/opensips.cfg -m 64 -M 4

14743 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid
-f /etc/opensips/opensips.cfg -m 64 -M 4

14744 ?S  0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid
-f /etc/opensips/opensips.cfg -m 64 -M 4

14745 ?S  0:00 /usr/sbin/opensips -P

Re: [OpenSIPS-Users] Wrong number of children

Re: [OpenSIPS-Users] Wrong number of children

Re: [OpenSIPS-Users] Wrong number of children

Re: [OpenSIPS-Users] Wrong number of children

Re: [OpenSIPS-Users] Wrong number of children

Re: [OpenSIPS-Users] Wrong number of children

Re: [OpenSIPS-Users] Wrong number of children

Re: [OpenSIPS-Users] Wrong number of children

Re: [OpenSIPS-Users] Wrong number of children

Re: [OpenSIPS-Users] Wrong number of children

Re: [OpenSIPS-Users] Wrong number of children

Re: [OpenSIPS-Users] Wrong number of children

Re: [OpenSIPS-Users] Wrong number of children

Re: [OpenSIPS-Users] Wrong number of children

Re: [OpenSIPS-Users] Wrong number of children

[OpenSIPS-Users] Wrong number of children

16 matches

Site Navigation

Mail list logo

Footer information