Indeed the very same problem occured after a while :-(
It looks my new configuration only "delayed" it.
The symptoms are:
- errors in log file:
May 27 14:20:11 server2-operations /usr/local/sbin/kamailio[26227]: WARNING:core:send2child: no free tcp receiver, connection passed to the leastbusy one (1)
May 27 14:20:13 server2-operations /usr/local/sbin/kamailio[26221]: ERROR:core:tcp_blocking_connect: timeout 10 s elapsed from 10 s
May 27 14:20:13 server2-operations /usr/local/sbin/kamailio[26221]: ERROR:core:tcpconn_connect: tcp_blocking_connect failed
May 27 14:20:13 server2-operations /usr/local/sbin/kamailio[26221]: ERROR:core:tcp_send: connect failed
May 27 14:20:13 server2-operations /usr/local/sbin/kamailio[26221]: ERROR:sl:msg_send: tcp_send failed
- in
top kamailio process have high values in the %CPU column such as 50% or 99% !?
- when all kamailio processes have reached this top values, it is impossible to connect a new client untill we reset kamailio :-/
I will try the parameter
modparam("registrar", "tcp_persistent_flag", 7)
from the registrar module.
-pascal