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