Re: [sr-dev] Crash bug

This was a rather peculiar crash: From the logs, it would appear that Kamailio simply stopped processing messages at some point. There's about 8 minutes of zero log output at a time of constantly incoming traffic. At some point, this situation is resolved when all Kamailio processes die with a normal SIGTERM, when someone manually restarted it: Mar 26 20:40:10 Proxy1 /usr/local/sbin/kamailio[27498]: NOTICE: <core> [main.c:739]: handle_sigs(): Thank you for flying kamailio!!! Mar 26 20:40:10 Proxy1 /usr/local/sbin/kamailio[27535]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received. ... But there are a few things here that are difficult to explain from the log: 1. Why was there no SIP stack response for 8 minutes, no logging activity, etc? 2. We have a script that checks if Kamailio processes are running every 1 second, and restarts Kamailio if it's not. It sends an e-mail informing us of that development also. It's a rather naive check: ps aux | grep kamailio | grep -v 'grep kamailio' | wc -l But in this case, the script was not triggered, which would imply that some Kamailio processes--perhaps all--remained running. There is no indication in the logs that any process died for any reason, except for the 'signal 15' received by all processes at the time of manual restart. 3. Why was a core dump generated at the time of the restart, if nothing crashed? #3 is most interesting to me, because if it were some other problem, e.g. blocking of SIP worker threads for some reason, then I wouldn't expect a core dump upon service shutdown. There is no other indication of any child process dying with SIGSEGV or SIGABRT. -- Alex On 03/27/2015 06:17 AM, Alex Balashov wrote: