when i re-built my 4.1 presence server, i noticed these compiler warning
that i don't remember seeing before:
CC (cc) [M presence_dialoginfo.so] notify_body.o
notify_body.c: In function 'agregate_xmls':
notify_body.c:104:28: warning: unused variable 'priority' [-Wunused-variable]
notify_body.c:104:6: warning: unused variable 'winner_priority' [-Wunused-variable]
-- juha
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#427 - kamailio sometimes crash when handling failure events
User who did this - Pawel Sternal (Sternik)
----------
Ok, and another crash. Few minutes ago.
<code>
May 12 11:21:33 node03 /usr/sbin/kamailio[23017]: : <core> [mem/q_malloc.c:468]: qm_free(): BUG: qm_free: freeing already freed pointer (0xa4ab1644), called from dialog: dlg_cb.c: destroy_dlg_
callbacks_list(80), first free dialog: dlg_cb.c: destroy_dlg_callbacks_list(80) - aborting
May 12 11:22:02 node03 /usr/sbin/kamailio[22924]: ALERT: <core> [main.c:775]: handle_sigs(): child process 23017 exited by a signal 6
May 12 11:22:02 node03 /usr/sbin/kamailio[22924]: ALERT: <core> [main.c:778]: handle_sigs(): core was generated
</code>
gdb bt full included.
----------
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#comment1435
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.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#427 - kamailio sometimes crash when handling failure events
User who did this - Pawel Sternal (Sternik)
----------
After more digginng in log files i've found 8 restarts after upgrade to kamailio 4.1.3. All ends after processing fail event.
There's a list:
1.
<code>
May 7 12:30:17 node02 /usr/sbin/kamailio[23300]: ALERT: <core> [main.c:775]: handle_sigs(): child process 23313 exited by a signal 11
</code>
Not found trying to double free. Last fork used to process ACK event.
-- ACK
<code>
May 7 12:28:34 node02 /usr/sbin/kamailio[23313]: WARNING: tm [t_lookup.c:1537]: t_unref(): WARNING: script writer didn't release transaction
</code>
2.
<code>
May 9 13:57:39 node02 /usr/sbin/kamailio[26402]: ALERT: <core> [main.c:775]: handle_sigs(): child process 26533 exited by a signal 6
</code>
-- failure_route
<code>
May 9 13:57:25 node02 /usr/sbin/kamailio[26533]: : <core> [mem/q_malloc.c:468]: qm_free(): BUG: qm_free: freeing already freed pointer (0xa5f53d00), called from dialog: dlg_cb.c: destroy_dlg_callbacks_list(80), first free dialog: dlg_cb.c: destroy_dlg_callbacks_list(80) - aborting
</code>
3.
<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
</code>
-- failure_route
<code>
May 9 20:16:23 node02 /usr/sbin/kamailio[4389]: : <core> [mem/q_malloc.c:468]: qm_free(): BUG: qm_free: freeing already freed pointer (0xa606a7f0), called from dialog: dlg_cb.c: destroy_dlg_callbacks_list(80), first free dialog: dlg_cb.c: destroy_dlg_callbacks_list(80) - aborting
</code>
4.
<code>
07/08/node03.log:May 7 06:13:04 node03 /usr/sbin/kamailio[9784]: ALERT: <core> [main.c:775]: handle_sigs(): child process 9821 exited by a signal 6
</code>
-- failure_route
<code>
May 7 06:12:40 node03 /usr/sbin/kamailio[9821]: : <core> [mem/q_malloc.c:468]: qm_free(): BUG: qm_free: freeing already freed pointer (0xa5dd9af4), called from dialog: dlg_cb.c: destroy_dlg_callbacks_list(80), first free dialog: dlg_cb.c: destroy_dlg_callbacks_list(80) - aborting
</code>
5.
<code>
07/13/node03.log:May 7 11:23:12 node03 /usr/sbin/kamailio[2924]: ALERT: <core> [main.c:775]: handle_sigs(): child process 2936 exited by a signal 6
</code>
-- failure_route
<code>
May 7 11:23:05 node03 /usr/sbin/kamailio[2936]: : <core> [mem/q_malloc.c:468]: qm_free(): BUG: qm_free: freeing already freed pointer (0xa5b073e4), called from dialog: dlg_cb.c: destroy_dlg_callbacks_list(80), first free dialog: dlg_cb.c: destroy_dlg_callbacks_list(80) - aborting
</code>
6.
<code>
May 7 14:25:33 node03 /usr/sbin/kamailio[10812]: ALERT: <core> [main.c:775]: handle_sigs(): child process 10822 exited by a signal 6
</code>
-- failure_route
<code>
May 7 14:25:27 node03 /usr/sbin/kamailio[10822]: : <core> [mem/q_malloc.c:468]: qm_free(): BUG: qm_free: freeing already freed pointer (0xa5bf8028), called from dialog: dlg_cb.c: destroy_dlg_callbacks_list(80), first free dialog: dlg_cb.c: destroy_dlg_callbacks_list(80) - aborting
</code>
7.
<code>
08/08/node03.log:May 8 06:43:03 node03 /usr/sbin/kamailio[20901]: ALERT: <core> [main.c:775]: handle_sigs(): child process 20968 exited by a signal 11
</code>
Not found trying to double free. Last fork used to process ACK event.
-- ACK
<code>
May 8 06:35:25 node03 /usr/sbin/kamailio[20968]: WARNING: tm [t_lookup.c:1537]: t_unref(): WARNING: script writer didn't release transaction
</code>
8.
<code>
10/13/node03.log: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
</code>
Not found trying to double free. Last fork used to process ACK event.
-- ACK
<code>
May 10 11:49:19 node03 /usr/sbin/kamailio[28897]: WARNING: tm [t_lookup.c:1537]: t_unref(): WARNING: script writer didn't release transaction
</code>
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=427#comment1434
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.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#427 - kamailio sometimes crash when handling failure events
User who did this - Pawel Sternal (Sternik)
----------
For pid 4389:
<code>
May 9 20:16:23 node02 /usr/sbin/kamailio[4389]: : <core> [mem/q_malloc.c:468]: qm_free(): BUG: qm_free: freeing already freed pointer (0xa606a7f0), called from dialog: dlg_cb.c: destroy_dlg_callbacks_list(80), first free dialog: dlg_cb.c: destroy_dlg_callbacks_list(80) - aborting
</code>
For pid 28897 I haven't found any of that. Only that might look suspicious:
<code>
May 10 11:25:13 node03 /usr/sbin/kamailio[28897]: WARNING: tm [t_lookup.c:1537]: t_unref(): WARNING: script writer didn't release transaction
May 10 11:34:33 node03 /usr/sbin/kamailio[28897]: WARNING: tm [t_lookup.c:1537]: t_unref(): WARNING: script writer didn't release transaction
May 10 11:43:37 node03 /usr/sbin/kamailio[28897]: WARNING: tm [t_lookup.c:1537]: t_unref(): WARNING: script writer didn't release transaction
May 10 11:49:19 node03 /usr/sbin/kamailio[28897]: WARNING: tm [t_lookup.c:1537]: t_unref(): WARNING: script writer didn't release transaction
</code>
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=427#comment1433
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.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#427 - kamailio sometimes crash when handling failure events
User who did this - Daniel-Constantin Mierla (miconda)
----------
Btw, should be something like:
<code>
BUG: qm_free: freeing already freed pointer ...
</code>
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=427#comment1432
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.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#427 - kamailio sometimes crash when handling failure events
User who did this - Daniel-Constantin Mierla (miconda)
----------
Looks like double free from dialog module, can you get the log messages from syslog printed by PIDs 4389 and 28897 before crash?
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=427#comment1431
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.