Hi,
Those messages say that OpenSIPS tried to open a TCP connection to a
party which does not respond -> there was a timeout for connect in 10
seconds. Because of this blocking in connects, there were not more
opensips workers available to handle other traffic.
So what you need to do is :
- minimize the impact of the blocking connect - see my previous
email on reducing the connect timeout
- you may configure OpenSIPS not to open new TCP connect (but to
reuse the existing ones, open by clients). See tcp_no_new_conn_bflag
http://www.opensips.org/Documentation/Script-CoreParameters-1-11#toc96
- try to understand the SIP patterns where such TCP connect fails
so you can avoid them at script level.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 24.06.2014 21:34, Gary Nyquist wrote:
Hi,
The following lines are repeating in the log.
ERROR:core:tcp_blocking_connect: timeout 10 s elapsed from 10 s
ERROR:core:tcpconn_connect: tcp_blocking_connect failed
ERROR:core:tcp_send: connect failed
ERROR:tm:msg_send: tcp_send failed
INFO:core:send2child: no free tcp receiver, connection passed to the
least busy one
Any guess, what could be the reason?
Best
--Gary
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
