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: <udp:46.236.205.196:5080>
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:[email protected]]
*Sent:* Monday, February 26, 2018 10:38 PM
*To:* xaled <[email protected]>
*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<PROTO_LAST ; 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:[email protected]]
*Sent:* Monday, February 26, 2018 5:25 PM
*To:* xaled <[email protected]> <mailto:[email protected]>; 'OpenSIPS users
mailling list' <[email protected]>
<mailto:[email protected]>
*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:[email protected]]
*Sent:* Monday, February 26, 2018 4:57 PM
*To:* xaled <[email protected]> <mailto:[email protected]>; 'OpenSIPS
users mailling list' <[email protected]>
<mailto:[email protected]>
*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:[email protected]]
*Sent:* Monday, February 26, 2018 4:41 PM
*To:* OpenSIPS users mailling list
<[email protected]>
<mailto:[email protected]>; xaled <[email protected]>
<mailto:[email protected]>
*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
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
