Re: [SR-Users] Kamailio 1.5.5 No TLS Segmentation Fault
When the system core dumps, there are usually two core dump files. Below is the backtrace from the core file with the earliest time stamp. #0 0x7f85626fe275 in raise () from /lib64/libc.so.6 Missing separate debuginfos, use: debuginfo-install bzip2-libs-1.0.5-5.fc11.x86_64 db4-4.7.25-11.fc11.x86_64 e2fsprogs-libs-1.41.9-2.fc11.x86_64 elfutils-libelf-0.147-1.fc11.x86_64 glibc-2.10.2-1.x86_64 keyutils-libs-1.2-5.fc11.x86_64 krb5-libs-1.6.3-31.fc11.x86_64 libacl-2.2.49-3.fc11.x86_64 libattr-2.4.43-3.fc11.x86_64 libcap-2.16-4.fc11.1.x86_64 libconfuse-2.6-2.fc11.x86_64 libgcc-4.4.1-2.fc11.x86_64 libselinux-2.0.80-1.fc11.x86_64 lm_sensors-3.1.0-1.fc11.x86_64 lua-5.1.4-3.fc11.x86_64 mysql-libs-5.1.46-1.fc11.x86_64 net-snmp-libs-5.4.2.1-13.fc11.x86_64 nspr-devel-4.8.4-1.3.fc11.x86_64 nss-devel-3.12.6-1.2.fc11.x86_64 nss-softokn-freebl-3.12.6-1.2.fc11.x86_64 openssl-0.9.8n-1.fc11.x86_64 pcre-7.8-2.fc11.x86_64 perl-libs-5.10.0-82.fc11.x86_64 popt-1.13-5.fc11.x86_64 radiusclient-ng-0.5.6-4.fc11.x86_64 rpm-libs-4.7.2-1.fc11.x86_64 tcp_wrappers-libs-7.6-55.fc11.x86_64 xz-libs-4.999.9-0.1.beta.20091007git.fc11.x86_64 zlib-1.2.3-22.fc11.x86_64 (gdb) bt full #0 0x7f85626fe275 in raise () from /lib64/libc.so.6 No symbol table info available. #1 0x7f85626ffa55 in abort () from /lib64/libc.so.6 No symbol table info available. #2 0x7f855fa9acf9 in t_check (p_msg=0x77a158, param_branch=0x7fff4b00b780) at t_lookup.c:972 local_branch = 0 __FUNCTION__ = t_check #3 0x7f855faa961a in reply_received (p_msg=0x77a158) at t_reply.c:1395 msg_status = 0 last_uac_status = 7519264 branch = 0 reply_status = 0 timer = 7519264 cancel_bitmap = 0 uac = 0x72bc60 t = 0x10046ad79 backup_list = 0x7fff4b00b7e0 reply_route = 0 __FUNCTION__ = reply_received #4 0x0041c768 in forward_reply (msg=0x77a158) at forward.c:576 new_buf = 0x0 to = 0x0 new_len = 0 mod = 0x7349d0 proto = 1258338384 id = 0 send_sock = 0x44d3ef s = 0x0 len = 0 __FUNCTION__ = forward_reply #5 0x0043c12a in receive_msg ( buf=0x70a9a0 SIP/2.0 200 OK\r\nVia: SIP/2.0/UDP xxx.xxx.34.37;branch=z9hG4bK9152.396285a3.0\r\nVia: SIP/2.0/UDP 74.3.224.66;branch=z9hG4bK9152.b99a879.0\r\nVia: SIP/2.0/UDP 208.113.68.10:5160;received=208.113.68.10;rport=5..., len=1069, rcv_info=0x7fff4b00b8d0) at receive.c:212 msg = 0x77a158 ---Type return to continue, or q return to quit--- __FUNCTION__ = receive_msg #6 0x00468459 in udp_rcv_loop () at udp_server.c:449 len = 1069 buf = SIP/2.0 200 OK\r\nVia: SIP/2.0/UDP xxx.xxx.34.37;branch=z9hG4bK9152.396285a3.0\r\nVia: SIP/2.0/UDP 74.3.224.66;branch=z9hG4bK9152.b99a879.0\r\nVia: SIP/2.0/UDP 208.113.68.10:5160;received=208.113.68.10;rport=5160;branch=z9hG4bKm6QQemUgXZyKB\r\nFrom: \5615424952\ sip:starpound-corp@74.3.224.66;transport=udp;tag=85mDg5a1358Fa\r\nTo: sip:8453598595@74.3.224.66;tag=SDen8i499-1b3f1afd+1+d0c0069+78211853\r\nCall-ID: bf9d2acd-b555-122e-01ac-00166e0003f5\r\nCSeq: 8643980 INVITE\r\nRecord-Route: sip:xxx.xxx.34.37;r2=on;lr=on;did=217.6aa80985\r\nRecord-Route: sip:xxx.xxx.32.37;r2=on;lr=on;did=217.6aa80985\r\nRecord-Route: sip:74.3.224.66;lr=on\r\nServer: DC-SIP/2.0\r\nSupported: 100rel,timer\r\nRequire: timer\r\nSession-Expires: 1800;refresher=uas\r\nContact: sip:8453598595@209.253.114.147:5060;user=phone;transport=udp\r\nContent-Type: application/sdp\r\nContent-Length: 220\r\n\r\nv=0\r\no=- 3506948892 3506948922 IN IP4 209.253.114.147\r\ns=-\r\nc=IN IP4 209.253.114.147\r\nt=0 0\r\nm=audio 10174 RTP/AVP 0 101\r\na=sendrecv\r\na=ptime:20\r\na=rtpmap:0 PCMU/8000\r\na=rtpmap:101 telephone-event/8000\r\na=fmtp:101 0-15\r\n\0\n\0\60-16\r\na=silenceSupp:off - - - -\r\na=ptime:20\r\n\0- -\r\na=ptime:20\r\n\0\60\r\n\0=z9hG4bKa60b.86cb9332.2\r\nVia: SIP/2.0/UDP xxx.xxx.34.37;branch=z9hG4bKa60b.86cb9332.2\r\nVia: SIP/2.0/UDP xxx.xxx.34.37;branch=z9hG4bKa60b.86cb9332.2\r\nVia: SIP/2.0/UDP xxx.xxx.34.37;branch=z9hG4bKa60b.86cb9332.2\r\nVia: SIP/2.0/UDP xxx.xxx.34.37;branch=z9hG4bKa60b.86cb9332.2\r\nVia: SIP/2.0/UDP xxx.xxx.34.37;branch=z9hG4bKa60b.86cb9332.2\r\nVia: SIP/2.0/UDP xxx.xxx.34.37;branch=z9hG4bKa60b.86cb9332.2\r\nVia: SIP/2.0/UDP xxx.xxx.34.37;branch=z9hG4bKa60b.86cb9332.2\r\nVia: SIP/2.0/UDP xxx.xxx.34.37;branch=z9hG4bKa60b.86cb9332.2\r\nVia: SIP/2.0/UDP xxx.xxx.34.37;branch=z9hG4bKa60b.86cb9332.2\r\nVia: SIP/2.0/UDP xxx.xxx.34.37;branch=z9hG4bKa60b.86cb9332.2\r\nVia: SIP/2.0/UDP xxx.xxx.34.37;branch=z9hG4bKa60b.86cb9332.2\r\nVia: SIP/2.0/UDP xxx.xxx.34.37;branch=z9hG4bKa60b.86cb9332.2\r\nVia: SIP/2.0/UDP xxx.xxx.34.37;branch=z9hG4bKa60b.86cb9332.2\r\nVia: SIP/2.0/UDP xxx.xxx.34.37;branch=z9hG4bKa60b.86cb9332.2\r\nVia: SIP/2.0/UDP xxx.xxx.34.37;branch=z9hG4bKa60b.86cb9332.2\r\nVia: SIP/2.0/UDP
Re: [SR-Users] Kamailio 1.5.5 No TLS Segmentation Fault
Hello, On 2/17/11 5:41 PM, Stagg Shelton wrote: Hi Timo, I have not tried the latest SVN yet. My system just did another core again today. The backtrace seems to show it at the same location. Below is the backtrace from today. If grabbing the latest SVN is the only chance of stopping this behavior I can do that, but I have to be as careful as possible to try and ensure that new anomalies are not introduced as a result of a code change. Is the information from the backtrace even helpful for identifying the root cause of the issue? I recommend using 1.5 from SVN branch. Since 1.5.5 was released on Oct 20, there were some fixes related to dialog, very likely to fix the problem you report. On the other hand, with Kamailio we do only bug fixes between minor releases. A major release has always the ending digit 0. Version x.y.z is a new major release if z=0, then z=1 or greater means we have found and fixed issues in x.y.0. There is no new feature, therefore no new bugs should be introduced. We don't do minor releases as we find and fix one issue, but wait 1-2 months to accumulate more. Using a stable branch, being it SVN or GIT should be safer than using a tarball with a release. Summarizing: - new features are brought by versions changing x or y numbers - fixed issues are brought by versions changing z number -- in this case the config file format and database structure are the same for any of z numbers when x.y is the same Cheers, Daniel Core was generated by `/sbin/kamailio -m 512'. Program terminated with signal 11, Segmentation fault. #0 0x7f85596b0fa7 in unref_dlg (dlg=0x7f853f9d1588, cnt=1) at dlg_hash.c:474 474 d_entry =(d_table-entries[dlg-h_entry]); Missing separate debuginfos, use: debuginfo-install bzip2-libs-1.0.5-5.fc11.x86_64 db4-4.7.25-11.fc11.x86_64 e2fsprogs-libs-1.41.9-2.fc11.x86_64 elfutils-libelf-0.147-1.fc11.x86_64 glibc-2.10.2-1.x86_64 keyutils-libs-1.2-5.fc11.x86_64 krb5-libs-1.6.3-31.fc11.x86_64 libacl-2.2.49-3.fc11.x86_64 libattr-2.4.43-3.fc11.x86_64 libcap-2.16-4.fc11.1.x86_64 libconfuse-2.6-2.fc11.x86_64 libgcc-4.4.1-2.fc11.x86_64 libselinux-2.0.80-1.fc11.x86_64 lm_sensors-3.1.0-1.fc11.x86_64 lua-5.1.4-3.fc11.x86_64 mysql-libs-5.1.46-1.fc11.x86_64 net-snmp-libs-5.4.2.1-13.fc11.x86_64 nspr-devel-4.8.4-1.3.fc11.x86_64 nss-devel-3.12.6-1.2.fc11.x86_64 nss-softokn-freebl-3.12.6-1.2.fc11.x86_64 openssl-0.9.8n-1.fc11.x86_64 pcre-7.8-2.fc11.x86_64 perl-libs-5.10.0-82.fc11.x86_64 popt-1.13-5.fc11.x86_64 radiusclient-ng-0.5.6-4.fc11.x86_64 rpm-libs-4.7.2-1.fc11.x86_64 tcp_wrappers-libs-7.6-55.fc11.x86_64 xz-libs-4.999.9-0.1.beta.20091007git.fc11.x86_64 zlib-1.2.3-22.fc11.x86_64 (gdb) bt full #0 0x7f85596b0fa7 in unref_dlg (dlg=0x7f853f9d1588, cnt=1) at dlg_hash.c:474 d_entry = 0x0 __FUNCTION__ = unref_dlg #1 0x7f85596ac80f in unref_dlg_from_cb (t=0x7f853f91d1b0, type=4096, param=0x7f855fcc56e0) at dlg_handlers.c:622 dlg = 0x7f853f9d1588 #2 0x7f855fa93ea3 in run_trans_callbacks (type=4096, trans=0x7f853f91d1b0, req=0x0, rpl=0x0, code=0) at t_hooks.c:240 cbp = 0x7f853f76e278 backup = 0x71a9d0 trans_backup = 0x __FUNCTION__ = run_trans_callbacks #3 0x7f855fa823cc in free_cell (dead_cell=0x7f853f91d1b0) at h_table.c:132 b = 0x0 i = 1 rpl = 0x0 tt = 0x0 foo = 0x0 p = 0x7f853f73bc30 #4 0x7f855fa82bb6 in free_hash_table () at h_table.c:345 p_cell = 0x7f853f91d1b0 tmp_cell = 0x0 i = 6172 #5 0x7f855fa8f2a4 in tm_shutdown () at t_funcs.c:109 __FUNCTION__ = tm_shutdown #6 0x004529f6 in destroy_modules () at sr_module.c:321 t = 0x7349d0 foo = 0x734910 __FUNCTION__ = destroy_modules #7 0x0041f6b4 in cleanup (show_status=1) at main.c:331 No locals. #8 0x00420597 in handle_sigs () at main.c:517 chld = 0 chld_status = 134 i = 10 do_exit = 1 ---Typereturn to continue, or qreturn to quit--- shutdown_time = 60 __FUNCTION__ = handle_sigs #9 0x004217b5 in main_loop () at main.c:859 chd_rank = 12 i = 4 pid = 29418 si = 0x0 __FUNCTION__ = main_loop #10 0x00423410 in main (argc=3, argv=0x7fff4b00bb18) at main.c:1321 cfg_log_stderr = 0 cfg_stream = 0x225a010 c = -1 r = 0 tmp_len = 0 port = 0 proto = 4910128 ret = -1 rfd = 4 tmp = 0x7fff4b00cf84 options = 0x4b77e0 f:cCm:b:l:n:N:rRvdDFETSVhw:t:u:g:P:G:W: rand_source = 0x4b7d9c /dev/urandom seed = 3664355638 __FUNCTION__ = main --Stagg On Feb 15, 2011, at 4:39 AM, Timo Reimann wrote: Hi Stagg, with regards to the failing function, there was a bugfix in the dialog module which, unfortunately, didn't make it
Re: [SR-Users] Kamailio 1.5.5 No TLS Segmentation Fault
Thanks Daniel. I've downloaded the source from subversion for the 1.5 branch. I am planning on building it tonight, and performing a maintenance on my production server late tomorrow night. I noticed in the svn code that TLS comes down with it. I have always used the -notls released source. Are there any special flags that I need to pass in the build to ensure that tls does not get built. I do hope that the new code resolves the issue. Thanks Stagg On Feb 17, 2011, at 12:53 PM, Daniel-Constantin Mierla wrote: Hello, On 2/17/11 5:41 PM, Stagg Shelton wrote: Hi Timo, I have not tried the latest SVN yet. My system just did another core again today. The backtrace seems to show it at the same location. Below is the backtrace from today. If grabbing the latest SVN is the only chance of stopping this behavior I can do that, but I have to be as careful as possible to try and ensure that new anomalies are not introduced as a result of a code change. Is the information from the backtrace even helpful for identifying the root cause of the issue? I recommend using 1.5 from SVN branch. Since 1.5.5 was released on Oct 20, there were some fixes related to dialog, very likely to fix the problem you report. On the other hand, with Kamailio we do only bug fixes between minor releases. A major release has always the ending digit 0. Version x.y.z is a new major release if z=0, then z=1 or greater means we have found and fixed issues in x.y.0. There is no new feature, therefore no new bugs should be introduced. We don't do minor releases as we find and fix one issue, but wait 1-2 months to accumulate more. Using a stable branch, being it SVN or GIT should be safer than using a tarball with a release. Summarizing: - new features are brought by versions changing x or y numbers - fixed issues are brought by versions changing z number -- in this case the config file format and database structure are the same for any of z numbers when x.y is the same Cheers, Daniel Core was generated by `/sbin/kamailio -m 512'. Program terminated with signal 11, Segmentation fault. #0 0x7f85596b0fa7 in unref_dlg (dlg=0x7f853f9d1588, cnt=1) at dlg_hash.c:474 474 d_entry =(d_table-entries[dlg-h_entry]); Missing separate debuginfos, use: debuginfo-install bzip2-libs-1.0.5-5.fc11.x86_64 db4-4.7.25-11.fc11.x86_64 e2fsprogs-libs-1.41.9-2.fc11.x86_64 elfutils-libelf-0.147-1.fc11.x86_64 glibc-2.10.2-1.x86_64 keyutils-libs-1.2-5.fc11.x86_64 krb5-libs-1.6.3-31.fc11.x86_64 libacl-2.2.49-3.fc11.x86_64 libattr-2.4.43-3.fc11.x86_64 libcap-2.16-4.fc11.1.x86_64 libconfuse-2.6-2.fc11.x86_64 libgcc-4.4.1-2.fc11.x86_64 libselinux-2.0.80-1.fc11.x86_64 lm_sensors-3.1.0-1.fc11.x86_64 lua-5.1.4-3.fc11.x86_64 mysql-libs-5.1.46-1.fc11.x86_64 net-snmp-libs-5.4.2.1-13.fc11.x86_64 nspr-devel-4.8.4-1.3.fc11.x86_64 nss-devel-3.12.6-1.2.fc11.x86_64 nss-softokn-freebl-3.12.6-1.2.fc11.x86_64 openssl-0.9.8n-1.fc11.x86_64 pcre-7.8-2.fc11.x86_64 perl-libs-5.10.0-82.fc11.x86_64 popt-1.13-5.fc11.x86_64 radiusclient-ng-0.5.6-4.fc11.x86_64 rpm-libs-4.7.2-1.fc11.x86_64 tcp_wrappers-libs-7.6-55.fc11.x86_64 xz-libs-4.999.9-0.1.beta.20091007git.fc11.x86_64 zlib-1.2.3-22.fc11.x86_64 (gdb) bt full #0 0x7f85596b0fa7 in unref_dlg (dlg=0x7f853f9d1588, cnt=1) at dlg_hash.c:474 d_entry = 0x0 __FUNCTION__ = unref_dlg #1 0x7f85596ac80f in unref_dlg_from_cb (t=0x7f853f91d1b0, type=4096, param=0x7f855fcc56e0) at dlg_handlers.c:622 dlg = 0x7f853f9d1588 #2 0x7f855fa93ea3 in run_trans_callbacks (type=4096, trans=0x7f853f91d1b0, req=0x0, rpl=0x0, code=0) at t_hooks.c:240 cbp = 0x7f853f76e278 backup = 0x71a9d0 trans_backup = 0x __FUNCTION__ = run_trans_callbacks #3 0x7f855fa823cc in free_cell (dead_cell=0x7f853f91d1b0) at h_table.c:132 b = 0x0 i = 1 rpl = 0x0 tt = 0x0 foo = 0x0 p = 0x7f853f73bc30 #4 0x7f855fa82bb6 in free_hash_table () at h_table.c:345 p_cell = 0x7f853f91d1b0 tmp_cell = 0x0 i = 6172 #5 0x7f855fa8f2a4 in tm_shutdown () at t_funcs.c:109 __FUNCTION__ = tm_shutdown #6 0x004529f6 in destroy_modules () at sr_module.c:321 t = 0x7349d0 foo = 0x734910 __FUNCTION__ = destroy_modules #7 0x0041f6b4 in cleanup (show_status=1) at main.c:331 No locals. #8 0x00420597 in handle_sigs () at main.c:517 chld = 0 chld_status = 134 i = 10 do_exit = 1 ---Typereturn to continue, or qreturn to quit--- shutdown_time = 60 __FUNCTION__ = handle_sigs #9 0x004217b5 in main_loop () at main.c:859 chd_rank = 12 i = 4 pid = 29418 si = 0x0 __FUNCTION__ = main_loop #10 0x00423410 in main (argc=3, argv=0x7fff4b00bb18) at
Re: [SR-Users] Kamailio 1.5.5 No TLS Segmentation Fault
Hey Stagg, On 17.02.2011 17:41, Stagg Shelton wrote: I have not tried the latest SVN yet. My system just did another core again today. The backtrace seems to show it at the same location. Below is the backtrace from today. If grabbing the latest SVN is the only chance of stopping this behavior I can do that, but I have to be as careful as possible to try and ensure that new anomalies are not introduced as a result of a code change. Is the information from the backtrace even helpful for identifying the root cause of the issue? I am quite sure the segfault you are experiencing stems from a bug which has been fixed in revision 6049. Basically, your backtrace indicates that Kamailio is trying to shut down. Along the way, unref_dlg_from_cb() is called from a tm callback with the purpose of decreasing the dialog reference counter. Prior to revision 6049, the function didn't verify that (a) the dialog is still valid and (b) no shutdown is in progress but went straight onward calling unref_dlg(). Since your dialog pointer looks fine, condition (b) must be affecting you in dlg_hash.c:474 where things start to go wrong. There, the dialog's hash table entry is used as the lookup key for the the dialog hash table d_table. However, the latter has been deallocated and nullified before (during dialog module shutdown), thereby triggering the segfault when d_table is touched. That pretty much sums up what must have likely happened. I strongly suggest you upgrade to the latest SVN version of the 1.5 branch and don't worry too much about any anomalies possibly introduced. Between the release 1.5.5 and now, only 4 commits were done in the 1.5 branch, each and everyone of them being bugfixes. Hope this helps. Cheers, --Timo Core was generated by `/sbin/kamailio -m 512'. Program terminated with signal 11, Segmentation fault. #0 0x7f85596b0fa7 in unref_dlg (dlg=0x7f853f9d1588, cnt=1) at dlg_hash.c:474 474 d_entry = (d_table-entries[dlg-h_entry]); Missing separate debuginfos, use: debuginfo-install bzip2-libs-1.0.5-5.fc11.x86_64 db4-4.7.25-11.fc11.x86_64 e2fsprogs-libs-1.41.9-2.fc11.x86_64 elfutils-libelf-0.147-1.fc11.x86_64 glibc-2.10.2-1.x86_64 keyutils-libs-1.2-5.fc11.x86_64 krb5-libs-1.6.3-31.fc11.x86_64 libacl-2.2.49-3.fc11.x86_64 libattr-2.4.43-3.fc11.x86_64 libcap-2.16-4.fc11.1.x86_64 libconfuse-2.6-2.fc11.x86_64 libgcc-4.4.1-2.fc11.x86_64 libselinux-2.0.80-1.fc11.x86_64 lm_sensors-3.1.0-1.fc11.x86_64 lua-5.1.4-3.fc11.x86_64 mysql-libs-5.1.46-1.fc11.x86_64 net-snmp-libs-5.4.2.1-13.fc11.x86_64 nspr-devel-4.8.4-1.3.fc11.x86_64 nss-devel-3.12.6-1.2.fc11.x86_64 nss-softokn-freebl-3.12.6-1.2.fc11.x86_64 openssl-0.9.8n-1.fc11.x86_64 pcre-7.8-2.fc11.x86_64 perl-libs-5.10.0-82.fc11.x86_64 popt-1.13-5.fc11.x86_64 radiusclient-ng-0.5.6-4.fc11.x86_64 rpm-libs-4.7.2-1.fc11.x86_64 tcp_wrappers-libs-7.6-55.fc11.x86_64 xz-libs-4.999.9-0.1.beta.20091007git.fc11.x86_64 zlib-1.2.3-22.fc11.x86_64 (gdb) bt full #0 0x7f85596b0fa7 in unref_dlg (dlg=0x7f853f9d1588, cnt=1) at dlg_hash.c:474 d_entry = 0x0 __FUNCTION__ = unref_dlg #1 0x7f85596ac80f in unref_dlg_from_cb (t=0x7f853f91d1b0, type=4096, param=0x7f855fcc56e0) at dlg_handlers.c:622 dlg = 0x7f853f9d1588 #2 0x7f855fa93ea3 in run_trans_callbacks (type=4096, trans=0x7f853f91d1b0, req=0x0, rpl=0x0, code=0) at t_hooks.c:240 cbp = 0x7f853f76e278 backup = 0x71a9d0 trans_backup = 0x __FUNCTION__ = run_trans_callbacks #3 0x7f855fa823cc in free_cell (dead_cell=0x7f853f91d1b0) at h_table.c:132 b = 0x0 i = 1 rpl = 0x0 tt = 0x0 foo = 0x0 p = 0x7f853f73bc30 #4 0x7f855fa82bb6 in free_hash_table () at h_table.c:345 p_cell = 0x7f853f91d1b0 tmp_cell = 0x0 i = 6172 #5 0x7f855fa8f2a4 in tm_shutdown () at t_funcs.c:109 __FUNCTION__ = tm_shutdown #6 0x004529f6 in destroy_modules () at sr_module.c:321 t = 0x7349d0 foo = 0x734910 __FUNCTION__ = destroy_modules #7 0x0041f6b4 in cleanup (show_status=1) at main.c:331 No locals. #8 0x00420597 in handle_sigs () at main.c:517 chld = 0 chld_status = 134 i = 10 do_exit = 1 ---Type return to continue, or q return to quit--- shutdown_time = 60 __FUNCTION__ = handle_sigs #9 0x004217b5 in main_loop () at main.c:859 chd_rank = 12 i = 4 pid = 29418 si = 0x0 __FUNCTION__ = main_loop #10 0x00423410 in main (argc=3, argv=0x7fff4b00bb18) at main.c:1321 cfg_log_stderr = 0 cfg_stream = 0x225a010 c = -1 r = 0 tmp_len = 0 port = 0 proto = 4910128 ret = -1 rfd = 4 tmp = 0x7fff4b00cf84 options = 0x4b77e0
Re: [SR-Users] Kamailio 1.5.5 No TLS Segmentation Fault
Hi Stagg, with regards to the failing function, there was a bugfix in the dialog module which, unfortunately, didn't make it into 1.5.5 in time (revision 6049). Could you try the latest SVN of 1.5 and see if it solves the issue? Thanks. Cheers, --Timo On 14.02.2011 21:07, Stagg Shelton wrote: Hello, We have been having a problem with Kamilio faulting and dumping core files on occasion. I have not been able to reproduce the failure at will, but notice the back trace seems to point toward actions with the dialogue. Below is from a backtrace of a core file from just a few minutes ago. Can anyone determine what may have caused the system to error and stop processing? Thanks Stagg Core was generated by `/sbin/kamailio -m 512'. Program terminated with signal 11, Segmentation fault. #0 0x7f8a11d55fa7 in unref_dlg (dlg=0x7f89f7e07470, cnt=1) at dlg_hash.c:474 474 d_entry = (d_table-entries[dlg-h_entry]); Missing separate debuginfos, use: debuginfo-install bzip2-libs-1.0.5-5.fc11.x86_64 db4-4.7.25-11.fc11.x86_64 e2fsprogs-libs-1.41.9-2.fc11.x86_64 elfutils-libelf-0.147-1.fc11.x86_64 glibc-2.10.2-1.x86_64 keyutils-libs-1.2-5.fc11.x86_64 krb5-libs-1.6.3-31.fc11.x86_64 libacl-2.2.49-3.fc11.x86_64 libattr-2.4.43-3.fc11.x86_64 libcap-2.16-4.fc11.1.x86_64 libconfuse-2.6-2.fc11.x86_64 libgcc-4.4.1-2.fc11.x86_64 libselinux-2.0.80-1.fc11.x86_64 lm_sensors-3.1.0-1.fc11.x86_64 lua-5.1.4-3.fc11.x86_64 mysql-libs-5.1.46-1.fc11.x86_64 net-snmp-libs-5.4.2.1-13.fc11.x86_64 nspr-devel-4.8.4-1.3.fc11.x86_64 nss-devel-3.12.6-1.2.fc11.x86_64 nss-softokn-freebl-3.12.6-1.2.fc11.x86_64 openssl-0.9.8n-1.fc11.x86_64 pcre-7.8-2.fc11.x86_64 perl-libs-5.10.0-82.fc11.x86_64 popt-1.13-5.fc11.x86_64 radiusclient-ng-0.5.6-4.fc11.x86_64 rpm-libs-4.7.2-1.fc11.x86_64 tcp_wrappers-libs-7.6-55.fc11.x86_64 xz-libs-4.999.9-0.1.beta.20091007git.fc11.x86_64 zlib-1.2.3-22.fc11.x86_64 (gdb) bt full #0 0x7f8a11d55fa7 in unref_dlg (dlg=0x7f89f7e07470, cnt=1) at dlg_hash.c:474 d_entry = 0x0 __FUNCTION__ = unref_dlg #1 0x7f8a11d5180f in unref_dlg_from_cb (t=0x7f89f7d9c660, type=4096, param=0x7f8a1836a6e0) at dlg_handlers.c:622 dlg = 0x7f89f7e07470 #2 0x7f8a18138ea3 in run_trans_callbacks (type=4096, trans=0x7f89f7d9c660, req=0x0, rpl=0x0, code=0) at t_hooks.c:240 cbp = 0x7f89f7dc30e8 backup = 0x71a9d0 trans_backup = 0x __FUNCTION__ = run_trans_callbacks #3 0x7f8a181273cc in free_cell (dead_cell=0x7f89f7d9c660) at h_table.c:132 b = 0x0 i = 1 rpl = 0x0 tt = 0x0 foo = 0x7fff4282f190 p = 0x7f89f7d3b068 #4 0x7f8a18127bb6 in free_hash_table () at h_table.c:345 p_cell = 0x7f89f7d9c660 tmp_cell = 0x0 i = 4075 #5 0x7f8a181342a4 in tm_shutdown () at t_funcs.c:109 __FUNCTION__ = tm_shutdown #6 0x004529f6 in destroy_modules () at sr_module.c:321 t = 0x7349d0 foo = 0x734910 __FUNCTION__ = destroy_modules #7 0x0041f6b4 in cleanup (show_status=1) at main.c:331 No locals. #8 0x00420597 in handle_sigs () at main.c:517 chld = 0 chld_status = 134 i = 12 do_exit = 1 ---Type return to continue, or q return to quit--- shutdown_time = 60 __FUNCTION__ = handle_sigs #9 0x004217b5 in main_loop () at main.c:859 chd_rank = 12 i = 4 pid = 21442 si = 0x0 __FUNCTION__ = main_loop #10 0x00423410 in main (argc=3, argv=0x7fff4282f498) at main.c:1321 cfg_log_stderr = 0 cfg_stream = 0x1fe1010 c = -1 r = 0 tmp_len = 0 port = 0 proto = 4910128 ret = -1 rfd = 4 tmp = 0x7fff4282ff8a options = 0x4b77e0 f:cCm:b:l:n:N:rRvdDFETSVhw:t:u:g:P:G:W: rand_source = 0x4b7d9c /dev/urandom seed = 3628387751 __FUNCTION__ = main (gdb) (gdb) quit ___ 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 ___ 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
[SR-Users] Kamailio 1.5.5 No TLS Segmentation Fault
Hello, We have been having a problem with Kamilio faulting and dumping core files on occasion. I have not been able to reproduce the failure at will, but notice the back trace seems to point toward actions with the dialogue. Below is from a backtrace of a core file from just a few minutes ago. Can anyone determine what may have caused the system to error and stop processing? Thanks Stagg Core was generated by `/sbin/kamailio -m 512'. Program terminated with signal 11, Segmentation fault. #0 0x7f8a11d55fa7 in unref_dlg (dlg=0x7f89f7e07470, cnt=1) at dlg_hash.c:474 474 d_entry = (d_table-entries[dlg-h_entry]); Missing separate debuginfos, use: debuginfo-install bzip2-libs-1.0.5-5.fc11.x86_64 db4-4.7.25-11.fc11.x86_64 e2fsprogs-libs-1.41.9-2.fc11.x86_64 elfutils-libelf-0.147-1.fc11.x86_64 glibc-2.10.2-1.x86_64 keyutils-libs-1.2-5.fc11.x86_64 krb5-libs-1.6.3-31.fc11.x86_64 libacl-2.2.49-3.fc11.x86_64 libattr-2.4.43-3.fc11.x86_64 libcap-2.16-4.fc11.1.x86_64 libconfuse-2.6-2.fc11.x86_64 libgcc-4.4.1-2.fc11.x86_64 libselinux-2.0.80-1.fc11.x86_64 lm_sensors-3.1.0-1.fc11.x86_64 lua-5.1.4-3.fc11.x86_64 mysql-libs-5.1.46-1.fc11.x86_64 net-snmp-libs-5.4.2.1-13.fc11.x86_64 nspr-devel-4.8.4-1.3.fc11.x86_64 nss-devel-3.12.6-1.2.fc11.x86_64 nss-softokn-freebl-3.12.6-1.2.fc11.x86_64 openssl-0.9.8n-1.fc11.x86_64 pcre-7.8-2.fc11.x86_64 perl-libs-5.10.0-82.fc11.x86_64 popt-1.13-5.fc11.x86_64 radiusclient-ng-0.5.6-4.fc11.x86_64 rpm-libs-4.7.2-1.fc11.x86_64 tcp_wrappers-libs-7.6-55.fc11.x86_64 xz-libs-4.999.9-0.1.beta.20091007git.fc11.x86_64 zlib-1.2.3-22.fc11.x86_64 (gdb) bt full #0 0x7f8a11d55fa7 in unref_dlg (dlg=0x7f89f7e07470, cnt=1) at dlg_hash.c:474 d_entry = 0x0 __FUNCTION__ = unref_dlg #1 0x7f8a11d5180f in unref_dlg_from_cb (t=0x7f89f7d9c660, type=4096, param=0x7f8a1836a6e0) at dlg_handlers.c:622 dlg = 0x7f89f7e07470 #2 0x7f8a18138ea3 in run_trans_callbacks (type=4096, trans=0x7f89f7d9c660, req=0x0, rpl=0x0, code=0) at t_hooks.c:240 cbp = 0x7f89f7dc30e8 backup = 0x71a9d0 trans_backup = 0x __FUNCTION__ = run_trans_callbacks #3 0x7f8a181273cc in free_cell (dead_cell=0x7f89f7d9c660) at h_table.c:132 b = 0x0 i = 1 rpl = 0x0 tt = 0x0 foo = 0x7fff4282f190 p = 0x7f89f7d3b068 #4 0x7f8a18127bb6 in free_hash_table () at h_table.c:345 p_cell = 0x7f89f7d9c660 tmp_cell = 0x0 i = 4075 #5 0x7f8a181342a4 in tm_shutdown () at t_funcs.c:109 __FUNCTION__ = tm_shutdown #6 0x004529f6 in destroy_modules () at sr_module.c:321 t = 0x7349d0 foo = 0x734910 __FUNCTION__ = destroy_modules #7 0x0041f6b4 in cleanup (show_status=1) at main.c:331 No locals. #8 0x00420597 in handle_sigs () at main.c:517 chld = 0 chld_status = 134 i = 12 do_exit = 1 ---Type return to continue, or q return to quit--- shutdown_time = 60 __FUNCTION__ = handle_sigs #9 0x004217b5 in main_loop () at main.c:859 chd_rank = 12 i = 4 pid = 21442 si = 0x0 __FUNCTION__ = main_loop #10 0x00423410 in main (argc=3, argv=0x7fff4282f498) at main.c:1321 cfg_log_stderr = 0 cfg_stream = 0x1fe1010 c = -1 r = 0 tmp_len = 0 port = 0 proto = 4910128 ret = -1 rfd = 4 tmp = 0x7fff4282ff8a options = 0x4b77e0 f:cCm:b:l:n:N:rRvdDFETSVhw:t:u:g:P:G:W: rand_source = 0x4b7d9c /dev/urandom seed = 3628387751 __FUNCTION__ = main (gdb) (gdb) quit ___ 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
