THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - Pawel Sternal (Sternik)
Attached to Project - sip-router
Summary - kamailio sometimes crash when handling failure events
Task Type - Bug Report
Category - Core
Status - Unconfirmed
Assigned To -
Operating System - Linux
Severity - Low
Priority - Normal
Reported Version - 4.1
Due in Version - Undecided
Due Date - Undecided
Details - Hello. I notice that about once a day kamailio in version 4.1.3 crash when
handling failure events. I can't reproduce that situation.
Recently we upgraded prod proxies from 3.3.6 to 4.1.3. Maybe i'm using obsolete
configuration logic, while processing this events.
GDB 'bt full' included.
20140509
<code>
May 9 20:16:40 node02 /usr/sbin/kamailio[4372]: ALERT: <core> [main.c:775]:
handle_sigs(): child process 4389 exited by a signal 6
May 9 20:16:40 node02 /usr/sbin/kamailio[4372]: ALERT: <core> [main.c:778]:
handle_sigs(): core was generatedc
</code>
20140510
<code>
May 10 11:52:56 node03 /usr/sbin/kamailio[28876]: ALERT: <core> [main.c:775]:
handle_sigs(): child process 28897 exited by a signal 11
May 10 11:52:56 node03 /usr/sbin/kamailio[28876]: ALERT: <core> [main.c:778]:
handle_sigs(): core was generated
</code>
One or more files have been attached.
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=427
You are receiving this message because you have requested it from the Flyspray bugtracking
system. If you did not expect this message or don't want to receive mails in future,
you can change your notification settings at the URL shown above.