THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Andrey 'Krieger' Utkin (andrey.utkin.2) Attached to Project - sip-router Summary - Crash at t_reply.c:668 Task Type - Bug Report Category - tm Status - Assigned Assigned To - Andrei Pelinescu-Onciul Operating System - Linux Severity - Low Priority - Normal Reported Version - Development Due in Version - Undecided Due Date - Undecided Details - Hello all. Last days i notice frequent Kamailio crashes in testing environment and cores have mutual last point of gdb backtrace. in _reply (trans=0xb5ae4198, p_msg=0x0, code=500, text=0xbfe9fad0 "I'm terribly sorry, server error occurred (1/TM)", lock=0) at t_reply.c:668 I attach logs of recent crash. There is SIP communication between two kamailio installations (let's name them 'a' and 'b') and phones ('A' and 'B'). I'll try to explain the crash in few words as i understood it. Phone A@a sends SUBSCRIBE on B to kamailio on host a. Proxy 'a' looks up for B resource location (host 'b') and rewrites request URI substituting 'b' as host part, and calls t_relay(). Proxy 'b' receives "SUBSCRIBE sip:B@b...", processes handle_subscribe(), t_release(), as in sample config from distribtion. Proxy 'b' replies '202 OK', and NOTIFY within that dialog. Proxy 'a' receives NOTIFY and routes it to wrong place that does not reply to this request. Proxy 'b' retransmits NOTIFY 7 times. After these retransmits, proxy 'a' replies "SIP/2.0 500 I'm terribly sorry, server error occurred (1/TM)" to NOTIFY. Proxy 'b' crashes. GDB backtrace: 17:48root@oba ~ # gdb /usr/sbin/kamailio /core ....skipped... Core was generated by `kamailio'. Program terminated with signal 11, Segmentation fault. ....skipped... #0 0xb7c880e5 in _reply (trans=0xb5a442c0, p_msg=0x0, code=500, text=0xbfe2bd30 "I'm terribly sorry, server error occurred (1/TM)", lock=0) at t_reply.c:668 668 t_reply.c: No such file or directory. in t_reply.c (gdb) thread apply 1 bt Thread 1 (process 8261): #0 0xb7c880e5 in _reply (trans=0xb5a442c0, p_msg=0x0, code=500, text=0xbfe2bd30 "I'm terribly sorry, server error occurred (1/TM)", lock=0) at t_reply.c:668 #1 0xb7c8a829 in t_reply_unsafe (t=0xb5a442c0, p_msg=0x0, code=500, text=0xbfe2bd30 "I'm terribly sorry, server error occurred (1/TM)") at t_reply.c:1362 #2 0xb7c6c0d9 in kill_transaction_unsafe (trans=0xb5a442c0, error=-1) at t_funcs.c:236 #3 0xb7c8a2bb in t_should_relay_response (Trans=0xb5a442c0, new_code=500, branch=0, should_store=0xbfe2be60, should_relay=0xbfe2be5c, cancel_bitmap=0xbfe2c044, reply=0x82a2024) at t_reply.c:1278 #4 0xb7c8c778 in local_reply (t=0xb5a442c0, p_msg=0x82a2024, branch=0, msg_status=500, cancel_bitmap=0xbfe2c044) at t_reply.c:1776 #5 0xb7c8db15 in reply_received (p_msg=0x82a2024) at t_reply.c:2102 #6 0x0807af05 in forward_reply (msg=0x82a2024) at forward.c:689 #7 0x080a491f in receive_msg ( buf=0x8218440 "SIP/2.0 500 I'm terribly sorry, server error occurred (1/TM)\r\nVia: SIP/2.0/UDP 192.168.1.113;branch=z9hG4bKd44d.cf568782.0;rport=5060\r\nTo: sip:2020@192.168.1.124;tag=849224948\r\nFrom: sip:1010@192.168."..., len=557, rcv_info=0xbfe2c230) at receive.c:257 #8 0x081008ec in udp_rcv_loop () at udp_server.c:520 #9 0x08083e8e in main_loop () at main.c:1446 #10 0x08085da8 in main (argc=1, argv=0xbfe2c444) at main.c:2243 (gdb) System details: I use git branch 'kamailio_3.0' and check for new upstream commits once in several days. I have kamailio running with experimental module of sqlite database driver. 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=21 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.