12 Jan
2009
12 Jan
'09
1:55 p.m.
Adding to the below
I am getting these errors
Jan 12 12:35:30 sero /usr/local/sbin/openser[30076]:
ERROR:core:tcpconn_connect: tcp_blocking_connect failed
Jan 12 12:35:30 sero /usr/local/sbin/openser[30076]:
ERROR:core:tcp_send: connect failed
Jan 12 12:35:30 sero /usr/local/sbin/openser[30076]: ERROR:sl:msg_send:
tcp_send failed
Jan 12 12:35:30 sero /usr/local/sbin/openser[30076]:
ERROR:auth:challenge: failed to send the response
Jan 12 12:35:31 sero /usr/local/sbin/openser[30076]:
ERROR:core:tcp_blocking_connect: poll error: flags 18
Jan 12 12:35:31 sero /usr/local/sbin/openser[30076]:
ERROR:core:tcp_blocking_connect: failed to retrieve SO_ERROR (111)
Connection refused
With Regards
Ali Jawad
System Administrator
Splendor Telecom (www.splendor.net <outbind://210/www.splendor.net> )
Beirut, Lebanon
Phone: +961 1 373725
Fax: + 961 1 375554
________________________________
From: Ali Jawad
Sent: 2009-01-12 12:33
To: Ali Jawad; users(a)lists.opensips.org
Cc: users(a)lists.kamailio.org
Subject: RE: [OpenSIPS-Users] WARNING:core:send2child: no free tcp
receiver
As an update I have retrieved this
[root@sero ~]# /usr/local/sbin/openserctl ps
Process:: ID=0 PID=30033 Type=attendant
Process:: ID=1 PID=30036 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=2 PID=30037 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=3 PID=30038 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=4 PID=30039 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=5 PID=30041 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=6 PID=30042 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=7 PID=30043 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=8 PID=30044 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=9 PID=30045 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=10 PID=30046 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=11 PID=30047 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=12 PID=30048 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=13 PID=30049 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=14 PID=30050 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=15 PID=30051 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=16 PID=30052 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=17 PID=30053 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=18 PID=30054 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=19 PID=30055 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=20 PID=30056 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=21 PID=30057 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=22 PID=30060 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=23 PID=30062 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=24 PID=30064 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=25 PID=30065 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=26 PID=30066 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=27 PID=30067 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=28 PID=30068 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=29 PID=30069 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=30 PID=30070 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=31 PID=30071 Type=timer
Process:: ID=32 PID=30072 Type=timer
Process:: ID=33 PID=30073 Type=MI FIFO
Process:: ID=34 PID=30074 Type=TCP receiver
Process:: ID=35 PID=30075 Type=TCP receiver
Process:: ID=36 PID=30076 Type=TCP receiver
Process:: ID=37 PID=30077 Type=TCP receiver
Process:: ID=38 PID=30079 Type=TCP receiver
Process:: ID=39 PID=30080 Type=TCP receiver
Process:: ID=40 PID=30081 Type=TCP receiver
Process:: ID=41 PID=30082 Type=TCP receiver
Process:: ID=42 PID=30084 Type=TCP receiver
Process:: ID=43 PID=30085 Type=TCP receiver
Process:: ID=44 PID=30086 Type=TCP receiver
Process:: ID=45 PID=30087 Type=TCP receiver
Process:: ID=46 PID=30090 Type=TCP receiver
Process:: ID=47 PID=30091 Type=TCP receiver
Process:: ID=48 PID=30092 Type=TCP receiver
Process:: ID=49 PID=30094 Type=TCP receiver
Process:: ID=50 PID=30095 Type=TCP receiver
Process:: ID=51 PID=30096 Type=TCP receiver
Process:: ID=52 PID=30097 Type=TCP receiver
Process:: ID=53 PID=30098 Type=TCP receiver
Process:: ID=54 PID=30099 Type=TCP receiver
Process:: ID=55 PID=30100 Type=TCP receiver
Process:: ID=56 PID=30101 Type=TCP receiver
Process:: ID=57 PID=30102 Type=TCP receiver
Process:: ID=58 PID=30103 Type=TCP receiver
Process:: ID=59 PID=30104 Type=TCP receiver
Process:: ID=60 PID=30105 Type=TCP receiver
Process:: ID=61 PID=30107 Type=TCP receiver
Process:: ID=62 PID=30109 Type=TCP receiver
Process:: ID=63 PID=30110 Type=TCP receiver
Process:: ID=64 PID=30111 Type=TCP main
With Regards
Ali Jawad
System Administrator
Splendor Telecom (www.splendor.net <outbind://206/www.splendor.net> )
Beirut, Lebanon
Phone: +961 1 373725
Fax: + 961 1 375554
________________________________
From: users-bounces(a)lists.opensips.org
[mailto:users-bounces@lists.opensips.org] On Behalf Of Ali Jawad
Sent: 2009-01-12 02:31
To: users(a)lists.opensips.org
Cc: users(a)lists.kamailio.org
Subject: [OpenSIPS-Users] WARNING:core:send2child: no free tcp receiver
Hi All
I am getting a lot of WARNING:core:send2child: no free tcp receiver,
connection passed to the leastbusy one (7)
I tried setting children to 20 that did not help, these warning start
being displayed right after I start openser. Users frequently get
service unavailable errors randomly when they try to connect, but I dont
know if this is related to this warning message or not.
As for the server there is plenty of CPU and RAM left, users range from
140 to 250 online all using tls. As for server limits
I have set them to the following :
You have new mail in /var/spool/mail/root
[root@sero openser]# ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
file size (blocks, -f) unlimited
pending signals (-i) 1024
max locked memory (kbytes, -l) 32
max memory size (kbytes, -m) unlimited
open files (-n) 101024
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
stack size (kbytes, -s) 10240
cpu time (seconds, -t) unlimited
max user processes (-u) 16382
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
Is this warning message related to the serice unavailable problem, what
does the warning message mean in more depth and how to get rid of it ?
Thanks
Getting alot of
Jan 12 00:00:32 sero /usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to the
leastbusy one (7)
Jan 12 00:00:32 sero /usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to the
leastbusy one (7)
Jan 12 00:00:32 sero /usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to the
leastbusy one (7)
Jan 12 00:00:33 sero /usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to the
leastbusy one (8)
Jan 12 00:00:33 sero /usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to the
leastbusy one (8)
Jan 12 00:00:33 sero /usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to the
leastbusy one (8)
Jan 12 00:00:33 sero /usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to the
leastbusy one (8)
Jan 12 00:00:33 sero /usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to the
leastbusy one (9)
Jan 12 00:00:33 sero /usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to the
leastbusy one (9)
Jan 12 00:00:33 sero /usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to the
leastbusy one (9)
Jan 12 00:00:34 sero /usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to the
leastbusy one (9)
Jan 12 00:00:34 sero /usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to the
leastbusy one (10)
Jan 12 00:00:34 sero /usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to the
leastbusy one (10)
Jan 12 00:00:34 sero /usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to the
leastbusy one (10)
Jan 12 00:00:35 sero /usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to the
leastbusy one (10)
Jan 12 00:00:35 sero /usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to the
leastbusy one (10)
Jan 12 00:00:35 sero /usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to the
leastbusy one (10)
12 Jan
12 Jan
2:39 p.m.
New subject: [Kamailio-Users] [OpenSIPS-Users] WARNING:core:send2child: no free tcp receiver
Probably the proxy tries to open new tcp connections. This will fail
after some timeout. During waiting for the timeout the TCP processes are
busy, thus they can not handle new requests (as the warning says)
klaus
Ali Jawad schrieb:
Adding to the below
I am getting these errors
Jan 12 12:35:30 sero /usr/local/sbin/openser[30076]:
ERROR:core:tcpconn_connect: tcp_blocking_connect failed
Jan 12 12:35:30 sero /usr/local/sbin/openser[30076]:
ERROR:core:tcp_send: connect failed
Jan 12 12:35:30 sero /usr/local/sbin/openser[30076]: ERROR:sl:msg_send:
tcp_send failed
Jan 12 12:35:30 sero /usr/local/sbin/openser[30076]:
ERROR:auth:challenge: failed to send the response
Jan 12 12:35:31 sero /usr/local/sbin/openser[30076]:
ERROR:core:tcp_blocking_connect: poll error: flags 18
Jan 12 12:35:31 sero /usr/local/sbin/openser[30076]:
ERROR:core:tcp_blocking_connect: failed to retrieve SO_ERROR (111)
Connection refused
With Regards
Ali Jawad
System Administrator
Splendor Telecom (www.splendor.net <outbind://210/www.splendor.net>)
Beirut, Lebanon
Phone: +961 1 373725
Fax: + 961 1 375554
------------------------------------------------------------------------
*From:* Ali Jawad
*Sent:* 2009-01-12 12:33
*To:* Ali Jawad; users(a)lists.opensips.org
*Cc:* users(a)lists.kamailio.org
*Subject:* RE: [OpenSIPS-Users] WARNING:core:send2child: no free tcp
receiver
As an update I have retrieved this
[root@sero ~]# /usr/local/sbin/openserctl ps
Process:: ID=0 PID=30033 Type=attendant
Process:: ID=1 PID=30036 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=2 PID=30037 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=3 PID=30038 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=4 PID=30039 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=5 PID=30041 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=6 PID=30042 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=7 PID=30043 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=8 PID=30044 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=9 PID=30045 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=10 PID=30046 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=11 PID=30047 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=12 PID=30048 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=13 PID=30049 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=14 PID=30050 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=15 PID=30051 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=16 PID=30052 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=17 PID=30053 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=18 PID=30054 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=19 PID=30055 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=20 PID=30056 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=21 PID=30057 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=22 PID=30060 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=23 PID=30062 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=24 PID=30064 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=25 PID=30065 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=26 PID=30066 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=27 PID=30067 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=28 PID=30068 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=29 PID=30069 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=30 PID=30070 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=31 PID=30071 Type=timer
Process:: ID=32 PID=30072 Type=timer
Process:: ID=33 PID=30073 Type=MI FIFO
Process:: ID=34 PID=30074 Type=TCP receiver
Process:: ID=35 PID=30075 Type=TCP receiver
Process:: ID=36 PID=30076 Type=TCP receiver
Process:: ID=37 PID=30077 Type=TCP receiver
Process:: ID=38 PID=30079 Type=TCP receiver
Process:: ID=39 PID=30080 Type=TCP receiver
Process:: ID=40 PID=30081 Type=TCP receiver
Process:: ID=41 PID=30082 Type=TCP receiver
Process:: ID=42 PID=30084 Type=TCP receiver
Process:: ID=43 PID=30085 Type=TCP receiver
Process:: ID=44 PID=30086 Type=TCP receiver
Process:: ID=45 PID=30087 Type=TCP receiver
Process:: ID=46 PID=30090 Type=TCP receiver
Process:: ID=47 PID=30091 Type=TCP receiver
Process:: ID=48 PID=30092 Type=TCP receiver
Process:: ID=49 PID=30094 Type=TCP receiver
Process:: ID=50 PID=30095 Type=TCP receiver
Process:: ID=51 PID=30096 Type=TCP receiver
Process:: ID=52 PID=30097 Type=TCP receiver
Process:: ID=53 PID=30098 Type=TCP receiver
Process:: ID=54 PID=30099 Type=TCP receiver
Process:: ID=55 PID=30100 Type=TCP receiver
Process:: ID=56 PID=30101 Type=TCP receiver
Process:: ID=57 PID=30102 Type=TCP receiver
Process:: ID=58 PID=30103 Type=TCP receiver
Process:: ID=59 PID=30104 Type=TCP receiver
Process:: ID=60 PID=30105 Type=TCP receiver
Process:: ID=61 PID=30107 Type=TCP receiver
Process:: ID=62 PID=30109 Type=TCP receiver
Process:: ID=63 PID=30110 Type=TCP receiver
Process:: ID=64 PID=30111 Type=TCP main
With Regards
Ali Jawad
System Administrator
Splendor Telecom (www.splendor.net <outbind://206/www.splendor.net>)
Beirut, Lebanon
Phone: +961 1 373725
Fax: + 961 1 375554
------------------------------------------------------------------------
*From:* users-bounces(a)lists.opensips.org
[mailto:users-bounces@lists.opensips.org] *On Behalf Of *Ali Jawad
*Sent:* 2009-01-12 02:31
*To:* users(a)lists.opensips.org
*Cc:* users(a)lists.kamailio.org
*Subject:* [OpenSIPS-Users] WARNING:core:send2child: no free tcp receiver
Hi All
I am getting a lot of WARNING:core:send2child: no free tcp receiver,
connection passed to the leastbusy one (7)
I tried setting children to 20 that did not help, these warning start
being displayed right after I start openser. Users frequently get
service unavailable errors randomly when they try to connect, but I dont
know if this is related to this warning message or not.
As for the server there is plenty of CPU and RAM left, users range from
140 to 250 online all using tls. As for server limits
I have set them to the following :
You have new mail in /var/spool/mail/root
[root@sero openser]# ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
file size (blocks, -f) unlimited
pending signals (-i) 1024
max locked memory (kbytes, -l) 32
max memory size (kbytes, -m) unlimited
open files (-n) 101024
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
stack size (kbytes, -s) 10240
cpu time (seconds, -t) unlimited
max user processes (-u) 16382
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
Is this warning message related to the serice unavailable problem, what
does the warning message mean in more depth and how to get rid of it ?
Thanks
Getting alot of
Jan 12 00:00:32 sero /usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to the
leastbusy one (7)
Jan 12 00:00:32 sero /usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to the
leastbusy one (7)
Jan 12 00:00:32 sero /usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to the
leastbusy one (7)
Jan 12 00:00:33 sero /usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to the
leastbusy one (8)
Jan 12 00:00:33 sero /usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to the
leastbusy one (8)
Jan 12 00:00:33 sero /usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to the
leastbusy one (8)
Jan 12 00:00:33 sero /usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to the
leastbusy one (8)
Jan 12 00:00:33 sero /usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to the
leastbusy one (9)
Jan 12 00:00:33 sero /usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to the
leastbusy one (9)
Jan 12 00:00:33 sero /usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to the
leastbusy one (9)
Jan 12 00:00:34 sero /usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to the
leastbusy one (9)
Jan 12 00:00:34 sero /usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to the
leastbusy one (10)
Jan 12 00:00:34 sero /usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to the
leastbusy one (10)
Jan 12 00:00:34 sero /usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to the
leastbusy one (10)
Jan 12 00:00:35 sero /usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to the
leastbusy one (10)
Jan 12 00:00:35 sero /usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to the
leastbusy one (10)
Jan 12 00:00:35 sero /usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to the
leastbusy one (10)
------------------------------------------------------------------------
_______________________________________________
Users mailing list
Users(a)lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
6:26 p.m.
New subject: [Kamailio-Users] [OpenSIPS-Users] WARNING:core:send2child: no free tcp receiver
But there are roughly only 100 users ...this is a quadro core server.
Fax: +961 1 375554
-----Original Message-----
From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at]
Sent: 2009-01-12 15:40
To: Ali Jawad
Cc: users(a)lists.opensips.org; users(a)lists.kamailio.org
Subject: Re: [OpenSIPS-Users] WARNING:core:send2child: no free tcp
receiver
Probably the proxy tries to open new tcp connections. This will fail
after some timeout. During waiting for the timeout the TCP processes are
busy, thus they can not handle new requests (as the warning says)
klaus
Ali Jawad schrieb:
Adding to the below
I am getting these errors
Jan 12 12:35:30 sero /usr/local/sbin/openser[30076]:
ERROR:core:tcpconn_connect: tcp_blocking_connect failed Jan 12
12:35:30 sero /usr/local/sbin/openser[30076]:
ERROR:core:tcp_send: connect failed
Jan 12 12:35:30 sero /usr/local/sbin/openser[30076]:
ERROR:sl:msg_send:
tcp_send failed
Jan 12 12:35:30 sero /usr/local/sbin/openser[30076]:
ERROR:auth:challenge: failed to send the response Jan 12 12:35:31 sero
/usr/local/sbin/openser[30076]:
ERROR:core:tcp_blocking_connect: poll error: flags 18 Jan 12 12:35:31
sero /usr/local/sbin/openser[30076]:
ERROR:core:tcp_blocking_connect: failed to retrieve SO_ERROR (111)
Connection refused
With Regards
Ali Jawad
System Administrator
Splendor Telecom (www.splendor.net <outbind://210/www.splendor.net>)
Beirut, Lebanon
Phone: +961 1 373725
Fax: + 961 1 375554
----------------------------------------------------------------------
--
*From:* Ali Jawad
*Sent:* 2009-01-12 12:33
*To:* Ali Jawad; users(a)lists.opensips.org
*Cc:* users(a)lists.kamailio.org
*Subject:* RE: [OpenSIPS-Users] WARNING:core:send2child: no free tcp
receiver
As an update I have retrieved this
[root@sero ~]# /usr/local/sbin/openserctl ps
Process:: ID=0 PID=30033 Type=attendant
Process:: ID=1 PID=30036 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=2 PID=30037 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=3 PID=30038 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=4 PID=30039 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=5 PID=30041 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=6 PID=30042 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=7 PID=30043 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=8 PID=30044 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=9 PID=30045 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=10 PID=30046 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=11 PID=30047 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=12 PID=30048 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=13 PID=30049 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=14 PID=30050 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=15 PID=30051 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=16 PID=30052 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=17 PID=30053 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=18 PID=30054 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=19 PID=30055 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=20 PID=30056 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=21 PID=30057 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=22 PID=30060 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=23 PID=30062 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=24 PID=30064 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=25 PID=30065 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=26 PID=30066 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=27 PID=30067 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=28 PID=30068 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=29 PID=30069 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=30 PID=30070 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=31 PID=30071 Type=timer
Process:: ID=32 PID=30072 Type=timer
Process:: ID=33 PID=30073 Type=MI FIFO
Process:: ID=34 PID=30074 Type=TCP receiver
Process:: ID=35 PID=30075 Type=TCP receiver
Process:: ID=36 PID=30076 Type=TCP receiver
Process:: ID=37 PID=30077 Type=TCP receiver
Process:: ID=38 PID=30079 Type=TCP receiver
Process:: ID=39 PID=30080 Type=TCP receiver
Process:: ID=40 PID=30081 Type=TCP receiver
Process:: ID=41 PID=30082 Type=TCP receiver
Process:: ID=42 PID=30084 Type=TCP receiver
Process:: ID=43 PID=30085 Type=TCP receiver
Process:: ID=44 PID=30086 Type=TCP receiver
Process:: ID=45 PID=30087 Type=TCP receiver
Process:: ID=46 PID=30090 Type=TCP receiver
Process:: ID=47 PID=30091 Type=TCP receiver
Process:: ID=48 PID=30092 Type=TCP receiver
Process:: ID=49 PID=30094 Type=TCP receiver
Process:: ID=50 PID=30095 Type=TCP receiver
Process:: ID=51 PID=30096 Type=TCP receiver
Process:: ID=52 PID=30097 Type=TCP receiver
Process:: ID=53 PID=30098 Type=TCP receiver
Process:: ID=54 PID=30099 Type=TCP receiver
Process:: ID=55 PID=30100 Type=TCP receiver
Process:: ID=56 PID=30101 Type=TCP receiver
Process:: ID=57 PID=30102 Type=TCP receiver
Process:: ID=58 PID=30103 Type=TCP receiver
Process:: ID=59 PID=30104 Type=TCP receiver
Process:: ID=60 PID=30105 Type=TCP receiver
Process:: ID=61 PID=30107 Type=TCP receiver
Process:: ID=62 PID=30109 Type=TCP receiver
Process:: ID=63 PID=30110 Type=TCP receiver
Process:: ID=64 PID=30111 Type=TCP main
With Regards
Ali Jawad
System Administrator
Splendor Telecom (www.splendor.net <outbind://206/www.splendor.net>)
Beirut, Lebanon
Phone: +961 1 373725
Fax: + 961 1 375554
----------------------------------------------------------------------
--
*From:* users-bounces(a)lists.opensips.org
[mailto:users-bounces@lists.opensips.org] *On Behalf Of *Ali Jawad
*Sent:* 2009-01-12 02:31
*To:* users(a)lists.opensips.org
*Cc:* users(a)lists.kamailio.org
*Subject:* [OpenSIPS-Users] WARNING:core:send2child: no free tcp
receiver
Hi All
I am getting a lot of WARNING:core:send2child: no free tcp receiver,
connection passed to the leastbusy one (7) I tried setting children to
20 that did not help, these warning start being
displayed right after
I start openser. Users frequently get service unavailable errors
randomly when they try to connect, but I dont know if this is related
to this warning message or not.
As for the server there is plenty of CPU and RAM left, users range
from 140 to 250 online all using tls. As for server limits
I have set them to the following :
You have new mail in /var/spool/mail/root [root@sero openser]# ulimit
-a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
file size (blocks, -f) unlimited
pending signals (-i) 1024
max locked memory (kbytes, -l) 32
max memory size (kbytes, -m) unlimited
open files (-n) 101024
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
stack size (kbytes, -s) 10240
cpu time (seconds, -t) unlimited
max user processes (-u) 16382
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
Is this warning message related to the serice unavailable problem,
what does the warning message mean in more depth and how to get rid of
it ?
Thanks
Getting alot of
Jan 12 00:00:32 sero /usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to
the leastbusy one (7) Jan 12 00:00:32 sero
/usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to
the leastbusy one (7) Jan 12 00:00:32 sero
/usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to
the leastbusy one (7) Jan 12 00:00:33 sero
/usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to
the leastbusy one (8) Jan 12 00:00:33 sero
/usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to
the leastbusy one (8) Jan 12 00:00:33 sero
/usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to
the leastbusy one (8) Jan 12 00:00:33 sero
/usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to
the leastbusy one (8) Jan 12 00:00:33 sero
/usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to
the leastbusy one (9) Jan 12 00:00:33 sero
/usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to
the leastbusy one (9) Jan 12 00:00:33 sero
/usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to
the leastbusy one (9) Jan 12 00:00:34 sero
/usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to
the leastbusy one (9) Jan 12 00:00:34 sero
/usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to
the leastbusy one (10)
Jan 12 00:00:34 sero /usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to
the leastbusy one (10)
Jan 12 00:00:34 sero /usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to
the leastbusy one (10)
Jan 12 00:00:35 sero /usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to
the leastbusy one (10)
Jan 12 00:00:35 sero /usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to
the leastbusy one (10)
Jan 12 00:00:35 sero /usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to
the leastbusy one (10)
----------------------------------------------------------------------
--
_______________________________________________
Users mailing list
Users(a)lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
10:54 p.m.
New subject: [Kamailio-Users] [OpenSIPS-Users] WARNING:core:send2child: no free tcp receiver
Ali Jawad wrote:
But there are roughly only 100 users ...this is a
quadro core server.
The TCP timeout is usually some seconds. Thus, during this time the TCP
process is blocked completely.
I described this a few weeks ago very detailed on the list - please read
this thread:
http://lists.kamailio.org/pipermail/users/2008-December/020845.html
klaus
Fax: +961 1 375554
-----Original Message-----
From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at]
Sent: 2009-01-12 15:40
To: Ali Jawad
Cc: users(a)lists.opensips.org; users(a)lists.kamailio.org
Subject: Re: [OpenSIPS-Users] WARNING:core:send2child: no free tcp
receiver
Probably the proxy tries to open new tcp connections. This will fail
after some timeout. During waiting for the timeout the TCP processes are
busy, thus they can not handle new requests (as the warning says)
klaus
Ali Jawad schrieb:
Adding to the below
I am getting these errors
Jan 12 12:35:30 sero /usr/local/sbin/openser[30076]:
ERROR:core:tcpconn_connect: tcp_blocking_connect failed Jan 12
12:35:30 sero /usr/local/sbin/openser[30076]:
ERROR:core:tcp_send: connect failed
Jan 12 12:35:30 sero /usr/local/sbin/openser[30076]:
ERROR:sl:msg_send:
tcp_send failed
Jan 12 12:35:30 sero /usr/local/sbin/openser[30076]:
ERROR:auth:challenge: failed to send the response Jan 12 12:35:31 sero
/usr/local/sbin/openser[30076]:
ERROR:core:tcp_blocking_connect: poll error: flags 18 Jan 12 12:35:31
sero /usr/local/sbin/openser[30076]:
ERROR:core:tcp_blocking_connect: failed to retrieve SO_ERROR (111)
Connection refused
With Regards
Ali Jawad
System Administrator
Splendor Telecom (www.splendor.net <outbind://210/www.splendor.net>)
Beirut, Lebanon
Phone: +961 1 373725
Fax: + 961 1 375554
----------------------------------------------------------------------
--
*From:* Ali Jawad
*Sent:* 2009-01-12 12:33
*To:* Ali Jawad; users(a)lists.opensips.org
*Cc:* users(a)lists.kamailio.org
*Subject:* RE: [OpenSIPS-Users] WARNING:core:send2child: no free tcp
receiver
As an update I have retrieved this
[root@sero ~]# /usr/local/sbin/openserctl ps
Process:: ID=0 PID=30033 Type=attendant
Process:: ID=1 PID=30036 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=2 PID=30037 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=3 PID=30038 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=4 PID=30039 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=5 PID=30041 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=6 PID=30042 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=7 PID=30043 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=8 PID=30044 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=9 PID=30045 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=10 PID=30046 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=11 PID=30047 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=12 PID=30048 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=13 PID=30049 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=14 PID=30050 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=15 PID=30051 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=16 PID=30052 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=17 PID=30053 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=18 PID=30054 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=19 PID=30055 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=20 PID=30056 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=21 PID=30057 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=22 PID=30060 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=23 PID=30062 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=24 PID=30064 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=25 PID=30065 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=26 PID=30066 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=27 PID=30067 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=28 PID=30068 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=29 PID=30069 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=30 PID=30070 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=31 PID=30071 Type=timer
Process:: ID=32 PID=30072 Type=timer
Process:: ID=33 PID=30073 Type=MI FIFO
Process:: ID=34 PID=30074 Type=TCP receiver
Process:: ID=35 PID=30075 Type=TCP receiver
Process:: ID=36 PID=30076 Type=TCP receiver
Process:: ID=37 PID=30077 Type=TCP receiver
Process:: ID=38 PID=30079 Type=TCP receiver
Process:: ID=39 PID=30080 Type=TCP receiver
Process:: ID=40 PID=30081 Type=TCP receiver
Process:: ID=41 PID=30082 Type=TCP receiver
Process:: ID=42 PID=30084 Type=TCP receiver
Process:: ID=43 PID=30085 Type=TCP receiver
Process:: ID=44 PID=30086 Type=TCP receiver
Process:: ID=45 PID=30087 Type=TCP receiver
Process:: ID=46 PID=30090 Type=TCP receiver
Process:: ID=47 PID=30091 Type=TCP receiver
Process:: ID=48 PID=30092 Type=TCP receiver
Process:: ID=49 PID=30094 Type=TCP receiver
Process:: ID=50 PID=30095 Type=TCP receiver
Process:: ID=51 PID=30096 Type=TCP receiver
Process:: ID=52 PID=30097 Type=TCP receiver
Process:: ID=53 PID=30098 Type=TCP receiver
Process:: ID=54 PID=30099 Type=TCP receiver
Process:: ID=55 PID=30100 Type=TCP receiver
Process:: ID=56 PID=30101 Type=TCP receiver
Process:: ID=57 PID=30102 Type=TCP receiver
Process:: ID=58 PID=30103 Type=TCP receiver
Process:: ID=59 PID=30104 Type=TCP receiver
Process:: ID=60 PID=30105 Type=TCP receiver
Process:: ID=61 PID=30107 Type=TCP receiver
Process:: ID=62 PID=30109 Type=TCP receiver
Process:: ID=63 PID=30110 Type=TCP receiver
Process:: ID=64 PID=30111 Type=TCP main
With Regards
Ali Jawad
System Administrator
Splendor Telecom (www.splendor.net <outbind://206/www.splendor.net>)
Beirut, Lebanon
Phone: +961 1 373725
Fax: + 961 1 375554
----------------------------------------------------------------------
--
*From:* users-bounces(a)lists.opensips.org
[mailto:users-bounces@lists.opensips.org] *On Behalf Of *Ali Jawad
*Sent:* 2009-01-12 02:31
*To:* users(a)lists.opensips.org
*Cc:* users(a)lists.kamailio.org
*Subject:* [OpenSIPS-Users] WARNING:core:send2child: no free tcp
receiver
Hi All
I am getting a lot of WARNING:core:send2child: no free tcp receiver,
connection passed to the leastbusy one (7) I tried setting children to
20 that did not help, these warning start being
displayed right after
I start openser. Users frequently get service unavailable errors
randomly when they try to connect, but I dont know if this is related
to this warning message or not.
As for the server there is plenty of CPU and RAM left, users range
from 140 to 250 online all using tls. As for server limits
I have set them to the following :
You have new mail in /var/spool/mail/root [root@sero openser]# ulimit
-a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
file size (blocks, -f) unlimited
pending signals (-i) 1024
max locked memory (kbytes, -l) 32
max memory size (kbytes, -m) unlimited
open files (-n) 101024
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
stack size (kbytes, -s) 10240
cpu time (seconds, -t) unlimited
max user processes (-u) 16382
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
Is this warning message related to the serice unavailable problem,
what does the warning message mean in more depth and how to get rid of
it ?
>
> Thanks
>
>
>
> Getting alot of
>
> Jan 12 00:00:32 sero /usr/local/sbin/openser[28281]:
> WARNING:core:send2child: no free tcp receiver, connection passed to
> the leastbusy one (7) Jan 12 00:00:32 sero
> /usr/local/sbin/openser[28281]:
> WARNING:core:send2child: no free tcp receiver, connection passed to
> the leastbusy one (7) Jan 12 00:00:32 sero
> /usr/local/sbin/openser[28281]:
> WARNING:core:send2child: no free tcp receiver, connection passed to
> the leastbusy one (7) Jan 12 00:00:33 sero
> /usr/local/sbin/openser[28281]:
> WARNING:core:send2child: no free tcp receiver, connection passed to
> the leastbusy one (8) Jan 12 00:00:33 sero
> /usr/local/sbin/openser[28281]:
> WARNING:core:send2child: no free tcp receiver, connection passed to
> the leastbusy one (8) Jan 12 00:00:33 sero
> /usr/local/sbin/openser[28281]:
> WARNING:core:send2child: no free tcp receiver, connection passed to
> the leastbusy one (8) Jan 12 00:00:33 sero
> /usr/local/sbin/openser[28281]:
> WARNING:core:send2child: no free tcp receiver, connection passed to
> the leastbusy one (8) Jan 12 00:00:33 sero
> /usr/local/sbin/openser[28281]:
> WARNING:core:send2child: no free tcp receiver, connection passed to
> the leastbusy one (9) Jan 12 00:00:33 sero
> /usr/local/sbin/openser[28281]:
> WARNING:core:send2child: no free tcp receiver, connection passed to
> the leastbusy one (9) Jan 12 00:00:33 sero
> /usr/local/sbin/openser[28281]:
> WARNING:core:send2child: no free tcp receiver, connection passed to
> the leastbusy one (9) Jan 12 00:00:34 sero
> /usr/local/sbin/openser[28281]:
> WARNING:core:send2child: no free tcp receiver, connection passed to
> the leastbusy one (9) Jan 12 00:00:34 sero
> /usr/local/sbin/openser[28281]:
> WARNING:core:send2child: no free tcp receiver, connection passed to
> the leastbusy one (10)
>
> Jan 12 00:00:34 sero /usr/local/sbin/openser[28281]:
> WARNING:core:send2child: no free tcp receiver, connection passed to
> the leastbusy one (10)
>
> Jan 12 00:00:34 sero /usr/local/sbin/openser[28281]:
> WARNING:core:send2child: no free tcp receiver, connection passed to
> the leastbusy one (10)
>
> Jan 12 00:00:35 sero /usr/local/sbin/openser[28281]:
> WARNING:core:send2child: no free tcp receiver, connection passed to
> the leastbusy one (10)
>
> Jan 12 00:00:35 sero /usr/local/sbin/openser[28281]:
> WARNING:core:send2child: no free tcp receiver, connection passed to
> the leastbusy one (10)
>
> Jan 12 00:00:35 sero /usr/local/sbin/openser[28281]:
> WARNING:core:send2child: no free tcp receiver, connection passed to
> the leastbusy one (10)
>
>
>
>
> ----------------------------------------------------------------------
> --
>
> _______________________________________________
> Users mailing list
> Users(a)lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users 
13 Jan
13 Jan
12:55 p.m.
New subject: [Kamailio-Users] [OpenSIPS-Users] WARNING:core:send2child: no free tcp receiver
Hi Ali,
An easy way to reduce the IO waiting time is to reduce the timeouts for TCP:
1) timeout for setting up a new tcp connection - tcp_connect_timeout:
http://www.opensips.org/index.php?n=Resources.DocsCoreFcn#toc68
default 10 seconds, set it to 2 secs
2) timeout for sending a package - tcp_send_timeout:
http://www.opensips.org/index.php?n=Resources.DocsCoreFcn#toc67
default 10 secs, set it to 2
Also, do you have clients behind NATs?
Regards,
Bogdan
Ali Jawad wrote:
But there are roughly only 100 users ...this is a
quadro core server.
Fax: +961 1 375554
-----Original Message-----
From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at]
Sent: 2009-01-12 15:40
To: Ali Jawad
Cc: users(a)lists.opensips.org; users(a)lists.kamailio.org
Subject: Re: [OpenSIPS-Users] WARNING:core:send2child: no free tcp
receiver
Probably the proxy tries to open new tcp connections. This will fail
after some timeout. During waiting for the timeout the TCP processes are
busy, thus they can not handle new requests (as the warning says)
klaus
Ali Jawad schrieb:
Adding to the below
I am getting these errors
Jan 12 12:35:30 sero /usr/local/sbin/openser[30076]:
ERROR:core:tcpconn_connect: tcp_blocking_connect failed Jan 12
12:35:30 sero /usr/local/sbin/openser[30076]:
ERROR:core:tcp_send: connect failed
Jan 12 12:35:30 sero /usr/local/sbin/openser[30076]:
ERROR:sl:msg_send:
tcp_send failed
Jan 12 12:35:30 sero /usr/local/sbin/openser[30076]:
ERROR:auth:challenge: failed to send the response Jan 12 12:35:31 sero
/usr/local/sbin/openser[30076]:
ERROR:core:tcp_blocking_connect: poll error: flags 18 Jan 12 12:35:31
sero /usr/local/sbin/openser[30076]:
ERROR:core:tcp_blocking_connect: failed to retrieve SO_ERROR (111)
Connection refused
With Regards
Ali Jawad
System Administrator
Splendor Telecom (www.splendor.net <outbind://210/www.splendor.net>)
Beirut, Lebanon
Phone: +961 1 373725
Fax: + 961 1 375554
----------------------------------------------------------------------
--
*From:* Ali Jawad
*Sent:* 2009-01-12 12:33
*To:* Ali Jawad; users(a)lists.opensips.org
*Cc:* users(a)lists.kamailio.org
*Subject:* RE: [OpenSIPS-Users] WARNING:core:send2child: no free tcp
receiver
As an update I have retrieved this
[root@sero ~]# /usr/local/sbin/openserctl ps
Process:: ID=0 PID=30033 Type=attendant
Process:: ID=1 PID=30036 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=2 PID=30037 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=3 PID=30038 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=4 PID=30039 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=5 PID=30041 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=6 PID=30042 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=7 PID=30043 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=8 PID=30044 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=9 PID=30045 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=10 PID=30046 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=11 PID=30047 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=12 PID=30048 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=13 PID=30049 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=14 PID=30050 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=15 PID=30051 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=16 PID=30052 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=17 PID=30053 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=18 PID=30054 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=19 PID=30055 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=20 PID=30056 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=21 PID=30057 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=22 PID=30060 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=23 PID=30062 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=24 PID=30064 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=25 PID=30065 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=26 PID=30066 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=27 PID=30067 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=28 PID=30068 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=29 PID=30069 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=30 PID=30070 Type=SIP receiver udp:xx.yy.zz.aa:5060
Process:: ID=31 PID=30071 Type=timer
Process:: ID=32 PID=30072 Type=timer
Process:: ID=33 PID=30073 Type=MI FIFO
Process:: ID=34 PID=30074 Type=TCP receiver
Process:: ID=35 PID=30075 Type=TCP receiver
Process:: ID=36 PID=30076 Type=TCP receiver
Process:: ID=37 PID=30077 Type=TCP receiver
Process:: ID=38 PID=30079 Type=TCP receiver
Process:: ID=39 PID=30080 Type=TCP receiver
Process:: ID=40 PID=30081 Type=TCP receiver
Process:: ID=41 PID=30082 Type=TCP receiver
Process:: ID=42 PID=30084 Type=TCP receiver
Process:: ID=43 PID=30085 Type=TCP receiver
Process:: ID=44 PID=30086 Type=TCP receiver
Process:: ID=45 PID=30087 Type=TCP receiver
Process:: ID=46 PID=30090 Type=TCP receiver
Process:: ID=47 PID=30091 Type=TCP receiver
Process:: ID=48 PID=30092 Type=TCP receiver
Process:: ID=49 PID=30094 Type=TCP receiver
Process:: ID=50 PID=30095 Type=TCP receiver
Process:: ID=51 PID=30096 Type=TCP receiver
Process:: ID=52 PID=30097 Type=TCP receiver
Process:: ID=53 PID=30098 Type=TCP receiver
Process:: ID=54 PID=30099 Type=TCP receiver
Process:: ID=55 PID=30100 Type=TCP receiver
Process:: ID=56 PID=30101 Type=TCP receiver
Process:: ID=57 PID=30102 Type=TCP receiver
Process:: ID=58 PID=30103 Type=TCP receiver
Process:: ID=59 PID=30104 Type=TCP receiver
Process:: ID=60 PID=30105 Type=TCP receiver
Process:: ID=61 PID=30107 Type=TCP receiver
Process:: ID=62 PID=30109 Type=TCP receiver
Process:: ID=63 PID=30110 Type=TCP receiver
Process:: ID=64 PID=30111 Type=TCP main
With Regards
Ali Jawad
System Administrator
Splendor Telecom (www.splendor.net <outbind://206/www.splendor.net>)
Beirut, Lebanon
Phone: +961 1 373725
Fax: + 961 1 375554
----------------------------------------------------------------------
--
*From:* users-bounces(a)lists.opensips.org
[mailto:users-bounces@lists.opensips.org] *On Behalf Of *Ali Jawad
*Sent:* 2009-01-12 02:31
*To:* users(a)lists.opensips.org
*Cc:* users(a)lists.kamailio.org
*Subject:* [OpenSIPS-Users] WARNING:core:send2child: no free tcp
receiver
Hi All
I am getting a lot of WARNING:core:send2child: no free tcp receiver,
connection passed to the leastbusy one (7) I tried setting children to
20 that did not help, these warning start being
displayed right after
I start openser. Users frequently get service unavailable errors
randomly when they try to connect, but I dont know if this is related
to this warning message or not.
As for the server there is plenty of CPU and RAM left, users range
from 140 to 250 online all using tls. As for server limits
I have set them to the following :
You have new mail in /var/spool/mail/root [root@sero openser]# ulimit
-a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
file size (blocks, -f) unlimited
pending signals (-i) 1024
max locked memory (kbytes, -l) 32
max memory size (kbytes, -m) unlimited
open files (-n) 101024
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
stack size (kbytes, -s) 10240
cpu time (seconds, -t) unlimited
max user processes (-u) 16382
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
Is this warning message related to the serice unavailable problem,
what does the warning message mean in more depth and how to get rid of
it ?
Thanks
Getting alot of
Jan 12 00:00:32 sero /usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to
the leastbusy one (7) Jan 12 00:00:32 sero
/usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to
the leastbusy one (7) Jan 12 00:00:32 sero
/usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to
the leastbusy one (7) Jan 12 00:00:33 sero
/usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to
the leastbusy one (8) Jan 12 00:00:33 sero
/usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to
the leastbusy one (8) Jan 12 00:00:33 sero
/usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to
the leastbusy one (8) Jan 12 00:00:33 sero
/usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to
the leastbusy one (8) Jan 12 00:00:33 sero
/usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to
the leastbusy one (9) Jan 12 00:00:33 sero
/usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to
the leastbusy one (9) Jan 12 00:00:33 sero
/usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to
the leastbusy one (9) Jan 12 00:00:34 sero
/usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to
the leastbusy one (9) Jan 12 00:00:34 sero
/usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to
the leastbusy one (10)
Jan 12 00:00:34 sero /usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to
the leastbusy one (10)
Jan 12 00:00:34 sero /usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to
the leastbusy one (10)
Jan 12 00:00:35 sero /usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to
the leastbusy one (10)
Jan 12 00:00:35 sero /usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to
the leastbusy one (10)
Jan 12 00:00:35 sero /usr/local/sbin/openser[28281]:
WARNING:core:send2child: no free tcp receiver, connection passed to
the leastbusy one (10)
----------------------------------------------------------------------
--
_______________________________________________
Users mailing list
Users(a)lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
Users(a)lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
5605
days inactive
5606
days old
4 comments
3 participants
participants (3)
-
Ali Jawad -
Bogdan-Andrei Iancu -
Klaus Darilion