[prev in list] [next in list] [prev in thread] [next in thread]
List: serusers
Subject: Re: [SR-Users] segfault at 18 error 4 in auth_db.so on Version 4.0.6-1 Release
From: Jonathan Hunter <hunterj91 () hotmail ! com>
Date: 2014-06-26 9:07:50
Message-ID: DUB127-W35657EADB7CA454973A402BD180 () phx ! gbl
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Hi Daniel,
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? Thanks
Jon
Jun 26 09:38:09 pbx /usr/sbin/kamailio[18529]: ALERT: <core> [main.c:788]: \
handle_sigs(): child process 18532 exited by a signal 11Jun 26 09:38:09 pbx \
/usr/sbin/kamailio[18529]: ALERT: <core> [main.c:791]: handle_sigs(): core was not \
generatedJun 26 09:38:09 pbx /usr/sbin/kamailio[18529]: INFO: <core> [main.c:803]: \
handle_sigs(): INFO: terminating due to SIGCHLDJun 26 09:38:09 pbx \
/usr/sbin/kamailio[18531]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 \
receivedJun 26 09:38:09 pbx /usr/sbin/kamailio[18533]: INFO: <core> [main.c:854]: \
sig_usr(): INFO: signal 15 receivedJun 26 09:38:09 pbx /usr/sbin/kamailio[18537]: \
INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 receivedJun 26 09:38:09 pbx \
/usr/sbin/kamailio[18534]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 \
receivedJun 26 09:38:09 pbx /usr/sbin/kamailio[18535]: INFO: <core> [main.c:854]: \
sig_usr(): INFO: signal 15 receivedJun 26 09:38:09 pbx /usr/sbin/kamailio[18538]: \
INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 receivedJun 26 09:38:09 pbx \
/usr/sbin/kamailio[18530]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 \
receivedJun 26 09:38:09 pbx /usr/sbin/kamailio[18539]: INFO: <core> [main.c:854]: \
sig_usr(): INFO: signal 15 receivedJun 26 09:38:09 pbx /usr/sbin/kamailio[18536]: \
INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 receivedJun 26 09:38:09 pbx \
kamailio[2076]: ERROR: <script>: Failed Reg Block Traffic from 194.72.34.18Jun 26 \
09:38:09 pbx kamailio[2075]: ERROR: <script>: Failed Reg Block Traffic from \
194.72.34.18Jun 26 09:38:09 pbx kamailio[2074]: ERROR: <script>: Routing Call To \
Asterisk serverJun 26 09:38:09 pbx kamailio[2074]: INFO: <script>: Routing Call to \
Dispatcher group 1 -Asterisk Media ServersJun 26 09:38:10 pbx kamailio[2072]: ALERT: \
<core> [main.c:788]: handle_sigs(): child process 2075 exited by a signal 11Jun 26 \
09:38:10 pbx kamailio[2072]: ALERT: <core> [main.c:791]: handle_sigs(): core was \
generatedJun 26 09:38:10 pbx kamailio[2072]: INFO: <core> [main.c:803]: \
handle_sigs(): INFO: terminating due to SIGCHLDJun 26 09:38:10 pbx kamailio[2074]: \
INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 receivedJun 26 09:38:10 pbx \
kamailio[2078]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 receivedJun 26 \
09:38:10 pbx kamailio[2076]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 \
receivedJun 26 09:38:10 pbx kamailio[2077]: INFO: <core> [main.c:854]: sig_usr(): \
INFO: signal 15 receivedJun 26 09:38:10 pbx kamailio[2079]: INFO: <core> \
[main.c:854]: sig_usr(): INFO: signal 15 receivedJun 26 09:38:10 pbx kamailio[2073]: \
INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 receivedJun 26 09:38:10 pbx \
kamailio[2080]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 receivedJun 26 \
09:38:10 pbx kamailio[2081]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 \
receivedJun 26 09:38:10 pbx kamailio[2082]: INFO: <core> [main.c:854]: sig_usr(): \
INFO: signal 15 receivedJun 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
[Attachment #5 (text/html)]
<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Hi Daniel,<div><br></div><div>Ok great will \
try that.</div><div><br></div><div>Ive just had another crash today on same release, \
this time affecting the child processes, please see below.</div><div><br></div><div>I \
presume again I would need to capture debug/traces at the time of failure to see \
possible cause?</div><div><br></div><div>Thanks</div><div><br></div><div>Jon</div><div><br></div><div><div>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</div><div>Jun 26 09:38:09 \
pbx /usr/sbin/kamailio[18529]: ALERT: <core> [main.c:791]: handle_sigs(): core \
was not generated</div><div>Jun 26 09:38:09 pbx /usr/sbin/kamailio[18529]: INFO: \
<core> [main.c:803]: handle_sigs(): INFO: terminating due to \
SIGCHLD</div><div>Jun 26 09:38:09 pbx /usr/sbin/kamailio[18531]: INFO: <core> \
[main.c:854]: sig_usr(): INFO: signal 15 received</div><div>Jun 26 09:38:09 pbx \
/usr/sbin/kamailio[18533]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal \
15 received</div><div>Jun 26 09:38:09 pbx /usr/sbin/kamailio[18537]: INFO: \
<core> [main.c:854]: sig_usr(): INFO: signal 15 received</div><div>Jun 26 \
09:38:09 pbx /usr/sbin/kamailio[18534]: INFO: <core> [main.c:854]: sig_usr(): \
INFO: signal 15 received</div><div>Jun 26 09:38:09 pbx /usr/sbin/kamailio[18535]: \
INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received</div><div>Jun 26 \
09:38:09 pbx /usr/sbin/kamailio[18538]: INFO: <core> [main.c:854]: sig_usr(): \
INFO: signal 15 received</div><div>Jun 26 09:38:09 pbx /usr/sbin/kamailio[18530]: \
INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received</div><div>Jun 26 \
09:38:09 pbx /usr/sbin/kamailio[18539]: INFO: <core> [main.c:854]: sig_usr(): \
INFO: signal 15 received</div><div>Jun 26 09:38:09 pbx /usr/sbin/kamailio[18536]: \
INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received</div><div>Jun 26 \
09:38:09 pbx kamailio[2076]: ERROR: <script>: Failed Reg Block Traffic from \
194.72.34.18</div><div>Jun 26 09:38:09 pbx kamailio[2075]: ERROR: <script>: \
Failed Reg Block Traffic from 194.72.34.18</div><div>Jun 26 09:38:09 pbx \
kamailio[2074]: ERROR: <script>: Routing Call To Asterisk server</div><div>Jun \
26 09:38:09 pbx kamailio[2074]: INFO: <script>: Routing Call to Dispatcher \
group 1 -Asterisk Media Servers</div><div>Jun 26 09:38:10 pbx kamailio[2072]: ALERT: \
<core> [main.c:788]: handle_sigs(): child process 2075 exited by a signal \
11</div><div>Jun 26 09:38:10 pbx kamailio[2072]: ALERT: <core> [main.c:791]: \
handle_sigs(): core was generated</div><div>Jun 26 09:38:10 pbx kamailio[2072]: INFO: \
<core> [main.c:803]: handle_sigs(): INFO: terminating due to \
SIGCHLD</div><div>Jun 26 09:38:10 pbx kamailio[2074]: INFO: <core> \
[main.c:854]: sig_usr(): INFO: signal 15 received</div><div>Jun 26 09:38:10 pbx \
kamailio[2078]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 \
received</div><div>Jun 26 09:38:10 pbx kamailio[2076]: INFO: <core> \
[main.c:854]: sig_usr(): INFO: signal 15 received</div><div>Jun 26 09:38:10 pbx \
kamailio[2077]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 \
received</div><div>Jun 26 09:38:10 pbx kamailio[2079]: INFO: <core> \
[main.c:854]: sig_usr(): INFO: signal 15 received</div><div>Jun 26 09:38:10 pbx \
kamailio[2073]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 \
received</div><div>Jun 26 09:38:10 pbx kamailio[2080]: INFO: <core> \
[main.c:854]: sig_usr(): INFO: signal 15 received</div><div>Jun 26 09:38:10 pbx \
kamailio[2081]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 \
received</div><div>Jun 26 09:38:10 pbx kamailio[2082]: INFO: <core> \
[main.c:854]: sig_usr(): INFO: signal 15 received</div><div>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)</div></div><div><br><div><hr id="stopSpelling">Date: Wed, 25 Jun 2014 18:33:59 \
+0200<br>From: miconda@gmail.com<br>To: sr-users@lists.sip-router.org<br>Subject: Re: \
[SR-Users] segfault at 18 error 4 in auth_db.so on Version 4.0.6-1 Release<br><br>
Hello,<br>
<br>
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.<br>
<br>
Before starting kamailio, enable core dumping via:<br>
<br>
ulimit -c unlimited<br>
<br>
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.<br>
<br>
Cheers,<br>
Daniel<br>
<br>
<div class="ecxmoz-cite-prefix">On 25/06/14 18:00, Jonathan Hunter
wrote:<br>
</div>
<blockquote cite="mid:DUB127-W7875F19D8CD070902C280BD190@phx.gbl">
<style><!--
.ExternalClass .ecxhmmessage P {
padding:0px;
}
.ExternalClass body.ecxhmmessage {
font-size:12pt;
font-family:Calibri;
}
--></style>
<div dir="ltr">
<div>Hi Guys,</div>
<div><br>
</div>
<div>We had our kamailio instance crash today, it appeared to be
after multiple registration failures, the resulting logs
showing;</div>
<div><br>
</div>
<div><br>
</div>
<div>Jun 25 15:47:55 kernel: : kamailio[14993]: segfault at 18
ip 00007f03102f9609 sp 00007fff1b346500 error 4 in
auth_db.so[7f03102f1000+b000]</div>
<div>Jun 25 15:47:55 /usr/sbin/kamailio[14989]: ALERT:
<core> [main.c:788]: handle_sigs(): child process 14993
exited by a signal 11</div>
<div>Jun 25 15:47:55 /usr/sbin/kamailio[14989]: ALERT:
<core> [main.c:791]: handle_sigs(): core was not
generated</div>
<div>Jun 25 15:47:55 /usr/sbin/kamailio[14989]: INFO:
<core> [main.c:803]: handle_sigs(): INFO: terminating
due to SIGCHLD</div>
<div><br>
</div>
<div><br>
</div>
<div>Any comments welcome.</div>
<div><br>
</div>
<div>thanks</div>
<div><br>
</div>
<div>Jon</div>
</div>
<br>
<fieldset class="ecxmimeAttachmentHeader"></fieldset>
<br>
<pre>_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
<a class="ecxmoz-txt-link-abbreviated" \
href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a> <a \
class="ecxmoz-txt-link-freetext" \
href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" \
target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a> \
</pre> </blockquote>
<br>
<pre class="ecxmoz-signature">--
Daniel-Constantin Mierla - <a class="ecxmoz-txt-link-freetext" \
href="http://www.asipto.com" target="_blank">http://www.asipto.com</a> <a \
class="ecxmoz-txt-link-freetext" href="http://twitter.com/#%21/miconda" \
target="_blank">http://twitter.com/#!/miconda</a> - <a \
class="ecxmoz-txt-link-freetext" href="http://www.linkedin.com/in/miconda" \
target="_blank">http://www.linkedin.com/in/miconda</a></pre>
<br>_______________________________________________
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</div></div> \
</div></body> </html>
_______________________________________________
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
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic