Ok great will try that.
Ive just had another crash today on same release, this time affecting the child processes, please see below.
I presume again I would need to capture debug/traces at the time of failure to see possible cause?
Jun 26 09:38:09 pbx /usr/sbin/kamailio[18529]: ALERT: <core> [main.c:788]: handle_sigs(): child process 18532 exited by a signal 11
Jun 26 09:38:09 pbx /usr/sbin/kamailio[18529]: ALERT: <core> [main.c:791]: handle_sigs(): core was not generated
Jun 26 09:38:09 pbx /usr/sbin/kamailio[18529]: INFO: <core> [main.c:803]: handle_sigs(): INFO: terminating due to SIGCHLD
Jun 26 09:38:09 pbx /usr/sbin/kamailio[18531]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received
Jun 26 09:38:09 pbx /usr/sbin/kamailio[18533]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received
Jun 26 09:38:09 pbx /usr/sbin/kamailio[18537]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received
Jun 26 09:38:09 pbx /usr/sbin/kamailio[18534]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received
Jun 26 09:38:09 pbx /usr/sbin/kamailio[18535]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received
Jun 26 09:38:09 pbx /usr/sbin/kamailio[18538]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received
Jun 26 09:38:09 pbx /usr/sbin/kamailio[18530]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received
Jun 26 09:38:09 pbx /usr/sbin/kamailio[18539]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received
Jun 26 09:38:09 pbx /usr/sbin/kamailio[18536]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received
Jun 26 09:38:09 pbx kamailio[2076]: ERROR: <script>: Failed Reg Block Traffic from 194.72.34.18
Jun 26 09:38:09 pbx kamailio[2075]: ERROR: <script>: Failed Reg Block Traffic from 194.72.34.18
Jun 26 09:38:09 pbx kamailio[2074]: ERROR: <script>: Routing Call To Asterisk server
Jun 26 09:38:09 pbx kamailio[2074]: INFO: <script>: Routing Call to Dispatcher group 1 -Asterisk Media Servers
Jun 26 09:38:10 pbx kamailio[2072]: ALERT: <core> [main.c:788]: handle_sigs(): child process 2075 exited by a signal 11
Jun 26 09:38:10 pbx kamailio[2072]: ALERT: <core> [main.c:791]: handle_sigs(): core was generated
Jun 26 09:38:10 pbx kamailio[2072]: INFO: <core> [main.c:803]: handle_sigs(): INFO: terminating due to SIGCHLD
Jun 26 09:38:10 pbx kamailio[2074]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received
Jun 26 09:38:10 pbx kamailio[2078]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received
Jun 26 09:38:10 pbx kamailio[2076]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received
Jun 26 09:38:10 pbx kamailio[2077]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received
Jun 26 09:38:10 pbx kamailio[2079]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received
Jun 26 09:38:10 pbx kamailio[2073]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received
Jun 26 09:38:10 pbx kamailio[2080]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received
Jun 26 09:38:10 pbx kamailio[2081]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received
Jun 26 09:38:10 pbx kamailio[2082]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received
Jun 26 09:38:10 pbx kamailio[2072]: ERROR: ctl [ctl.c:379]: mod_destroy(): ERROR: ctl: could not delete unix socket /tmp/kamailio_ctl: No such file or directory (2)
Date: Wed, 25 Jun 2014 18:33:59 +0200
From: miconda@gmail.com
To: sr-users@lists.sip-router.org
Subject: Re: [SR-Users] segfault at 18 error 4 in auth_db.so on Version 4.0.6-1 Release
Hello,
might not be the same, but I just pushed to branch 4.0 a fix for the
case when a request has both Proxy-Authorization and Authorization
headers that led to a wrong selection of the credentials, ending up
in a crash. Pull the latest branch 4.0 and try to see if goes fine
this time.
Before starting kamailio, enable core dumping via:
ulimit -c unlimited
in the terminal. Also, if you have /etc/default/kamailio, edit to
enable the core there. On some systems, you need to run kamailio as
root, because the kernel forbids dumping core files for unprivileged
users. The coredump file allows to get the backtrace and identify
what was the line of code causing the issue.
Cheers,
Daniel
On 25/06/14 18:00, Jonathan Hunter
wrote:
Hi Guys,
We had our kamailio instance crash today, it appeared to be
after multiple registration failures, the resulting logs
showing;
Jun 25 15:47:55 kernel: : kamailio[14993]: segfault at 18
ip 00007f03102f9609 sp 00007fff1b346500 error 4 in
auth_db.so[7f03102f1000+b000]
Jun 25 15:47:55 /usr/sbin/kamailio[14989]: ALERT:
<core> [main.c:788]: handle_sigs(): child process 14993
exited by a signal 11
Jun 25 15:47:55 /usr/sbin/kamailio[14989]: ALERT:
<core> [main.c:791]: handle_sigs(): core was not
generated
Jun 25 15:47:55 /usr/sbin/kamailio[14989]: INFO:
<core> [main.c:803]: handle_sigs(): INFO: terminating
due to SIGCHLD
Any comments welcome.
thanks
Jon
_______________________________________________
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
--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
_______________________________________________
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