THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#122 - Kamailio 3.1.3 crash
User who did this - Jasmin Schnatterbeck (jasmin)
----------
Hello,
the cfg for the query is:
route["CDR_FINALIZE"] {
sql_query("kdb","UPDATE `kamailio_cdr` SET `state`='completed', `utctime_dlgend`=UTC_TIMESTAMP() WHERE `hash_id`='$dlg(h_id)' AND `hash_entry`=$dlg(h_entry)","res");
}
This route is called from event_route[tm:local-request] if request method is BYE (triggered by mediaproxy) and from normal request route, if loose routing and request method is BYE.
I am wondering why the $dlg variables were not set in the case, which you extracted from the gdb output.
Furthermore I guess that the query failed, because the following is invalid:
WHERE `hash_id`='<null>' AND `hash_entry`=<null>
Because <null> is not a valid integer...
Is it possible, that a failed query results in a crash? Because normally, the request works (no <null> values) and kamailio (normally) does not crash...
Another idea: that is a result of the crashing child, because then kamailio terminates all childs and (guess) as a result of that, mediaproxy signals BYE to all dialogs - and the dialogs do not exist anymore (because kamailio is terminating), then $dlg is not available...
Jasmin
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=122#comment180
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#122 - Kamailio 3.1.3 crash
User who did this - marius zbihlei (marius.zbihlei)
----------
Sorry, last comment was a dupe
I see now that the usage looks ok. Can you also paste the cfg line where this query (that caused the crash ) gets executed "UPDATE `kamailio_cdr` SET `state`='completed', `utctime_dlgend`=UTC_TIMESTAMP() WHERE `hash_id`='<null>' AND `hash_entry`=<null>"
Also, it looks like the avp you passed there is not correct(not set yet), but that should not cause any problems.
Marius
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=122#comment179
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#122 - Kamailio 3.1.3 crash
User who did this - marius zbihlei (marius.zbihlei)
----------
Hello
>From the looks of things, the crash happens when you do a sql query from the cfg file. The problem is that the associated connection seems to not support raw queries, ,as the pointer in the db export con->dbf.raw_query is NULL so the top frame is completely bogus (address 0x00000000 is not a valid IP). What type of db backend do you use? What is the connect url you give to sqlops?
Anyway, even if the backend doesn't support raw queries, a crash is not wanted... better a error message should be reported.
Thanks,
Marius
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=122#comment178
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#118 - db_mysql fails to load on centos 5 due to bad simbol ref
User who did this - Costin Radu (ctradu)
----------
This does not seem to reproduce any more.
I have built from sources both kamailio 3.1.3 and kamailio head.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=118#comment177
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#122 - Kamailio 3.1.3 crash
User who did this - Jasmin Schnatterbeck (jasmin)
----------
Hello,
hmm... that's interesting. We use sqlops with the db_mysql module for several months now.
The connect url is:
modparam("sqlops","sqlcon","kdb=>mysql://sys_kamailio:xxxxx@localhost/config")
Thank you!
Jasmin
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=122#comment176
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#122 - Kamailio 3.1.3 crash
User who did this - marius zbihlei (marius.zbihlei)
----------
Hello
>From the looks of things, the crash happens when you do a sql query from the cfg file. The problem is that the associated connection seems to not support raw queries, ,as the pointer in the db export con->dbf.raw_query is NULL so the top frame is completely bogus (address 0x00000000 is not a valid IP). What type of db backend do you use? What is the connect url you give to sqlops?
Anyway, even if the backend doesn't support raw queries, a crash is not wanted... better a error message should be reported.
Thanks,
Marius
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=122#comment175
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#122 - Kamailio 3.1.3 crash
User who did this - Jasmin Schnatterbeck (jasmin)
----------
Hello,
thanks for your message
I attached the output of the gdb command.
Regarding the logging lines, unfortunately they are not available anymore (kamailio runs in a screen terminal). But as I remember them (when I copied the lines, which are pasted above) there was only output triggered by config-file/xlog.
Jasmin
----------
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=122#comment174
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#122 - Kamailio 3.1.3 crash
User who did this - marius zbihlei (marius.zbihlei)
----------
Hello,
Can you also provide this 2 essential infos:
1. Previous 10-20 lines of logging before the actual crash (before the lines you pasted)
2. Load the core file with gdb (gdb kamailio core.file) and issue the command bt full . Paste the output of the gdb command
Thank you
Marius
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=122#comment173
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.
marius zbihlei has taken ownership of the following task:
FS#122 - Kamailio 3.1.3 crash
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=122
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.
A new Flyspray task has been opened. Details are below.
User who did this - Jasmin Schnatterbeck (jasmin)
Attached to Project - sip-router
Summary - Kamailio 3.1.3 crash
Task Type - Bug Report
Category - Core
Status - Assigned
Assigned To - Andrei Pelinescu-Onciul
Operating System - Linux
Severity - Critical
Priority - Normal
Reported Version - 3.1
Due in Version - Undecided
Due Date - Undecided
Details - Hello,
after approx 8-14hrs of operation, our kamailio 3.1.3 crashes. We had the same problem with 3.1.2:
5(22376) : <core> [pass_fd.c:293]: ERROR: receive_fd: EOF on 27
0(22334) ALERT: <core> [main.c:741]: child process 22352 exited by a signal 11
0(22334) ALERT: <core> [main.c:744]: core was generated
0(22334) INFO: <core> [main.c:756]: INFO: terminating due to SIGCHLD
24(22374) INFO: <core> [main.c:807]: INFO: signal 15 received
22(22370) INFO: <core> [main.c:807]: INFO: signal 15 received
19(22364) INFO: <core> [main.c:807]: INFO: signal 15 received
15(22356) INFO: <core> [main.c:807]: INFO: signal 15 received
17(22360) INFO: <core> [main.c:807]: INFO: signal 15 received
20(22366) INFO: <core> [main.c:807]: INFO: signal 15 received
13(22351) INFO: <core> [main.c:807]: INFO: signal 15 received
4(22338) INFO: <core> [main.c:807]: INFO: signal 15 received
6(22340) INFO: <core> [main.c:807]: INFO: signal 15 received
11(22347) INFO: <core> [main.c:807]: INFO: signal 15 received
8(22342) INFO: <core> [main.c:807]: INFO: signal 15 received
3(22337) INFO: <core> [main.c:807]: INFO: signal 15 received
16(22358) INFO: <core> [main.c:807]: INFO: signal 15 received
10(22344) INFO: <core> [main.c:807]: INFO: signal 15 received
7(22341) INFO: <core> [main.c:807]: INFO: signal 15 received
18(22362) INFO: <core> [main.c:807]: INFO: signal 15 received
25(22376) INFO: <core> [main.c:807]: INFO: signal 15 received
9(22343) INFO: <core> [main.c:807]: INFO: signal 15 received
5(22339) INFO: <core> [main.c:807]: INFO: signal 15 received
1(22335) INFO: <core> [main.c:807]: INFO: signal 15 received
23(22372) INFO: <core> [main.c:807]: INFO: signal 15 received
2(22336) INFO: <core> [main.c:807]: INFO: signal 15 received
12(22348) INFO: <core> [main.c:807]: INFO: signal 15 received
21(22368) INFO: <core> [main.c:807]: INFO: signal 15 received
Corefile is available.
We were not able to reproduce those crashes (e.g. when sip msg XXX received), it just happens after some hours of normal operation.
What would you suggest?
Jasmin
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=122
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.
