Hello,
do you get other error messages in syslog before the one "CRITICAL: ..."?
It is hard to say it is from something already known or new. Right now there is an open issue for saving dialog variables in database that was not yet sorted out. Another one related to tm and memory manager, reported after 4.3.1, got a safety fix. Apart of these two, I don't remember any active crash report for the moment.
If you get it very often, then it should be easy to catch and troubleshoot properly. Can you run it so it generates a core file?
The easiest way is to run it as root, with 'ulimit -c unlimited' executed before starting kamailio.
Can you share what operating system are you using and exact version of kamailio (output of kamailio -v)?
Cheers, Daniel
On 09/09/15 12:15, Thibault Gueslin wrote:
After upgrading to kamailio 4.3.1 and modifying the config, I get this crash very often: ...
CRITICAL: <core> [pass_fd.c:275]: receive_fd(): EOF on 21
ALERT: <core> [main.c:728]: handle_sigs(): child process 9341 exited by a signal 11
ALERT: <core> [main.c:731]: handle_sigs(): core was not generated
INFO: <core> [main.c:743]: handle_sigs(): terminating due to SIGCHLD
INFO: <core> [main.c:794]: sig_usr(): signal 15 received
INFO: <core> [main.c:794]: sig_usr(): signal 15 received
INFO: <core> [main.c:794]: sig_usr(): signal 15 received
...
Is it known ? or may be related to my config ?
Thank you
Thibault
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users