Summary:	ASTERISK-18735: Asterisk spontaneous reboot
Reporter:	Jonas Kellens (jonaskellens)	Labels:
Date Opened:	2011-10-19 06:53:16	Date Closed:	2011-10-31 13:37:33
Priority:	Critical	Regression?	Yes
Status:	Closed/Complete	Components:	Core/PBX
Versions:	1.6.2.20	Frequency of Occurrence	Frequent
Related Issues:
Environment:	Linux sip1.server.be 2.6.18-274.3.1.el5 #1 SMP Tue Sep 6 20:13:52 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux	Attachments:
Description:	For some unknown reason, my Asterisk 1.6.2.20 spontaneous reboots. I have attached the created core dump file.
Comments:	By: David Woolley (davidw) 2011-10-19 09:09:40.945-0500 Per the Asterisk maintenance timeline page at http://www.asterisk.org/asterisk-versions maintenance (bug) support for the 1.4 and 1.6.x branches has ended. For continued maintenance support please move to the 1.8 branch which is a long term support (LTS) branch. For more information about branch support, please see https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions. After testing with Asterisk 1.8, if you find this problem has not been resolved, please open a new issue against Asterisk 1.8. Do you mean reboot? If you really mean reboot, I'm surprised there is a crash dump.  Also, a reboot would indicate a kernel panic, which would put the bug in the kernel or a device driver, not Asterisk. By: David Woolley (davidw) 2011-10-19 09:11:48.731-0500 Also, core dumps are no use except on the machine that created them; you need to provide a backtrace, which needs to be from a version of Asterisk compiled with compiler optimisations disabled. By: Jonas Kellens (jonaskellens) 2011-10-19 09:14:38.793-0500 I know that asterisk spontaneous restarts because the number of calls when doing "core show channels" is reset. OK, I will have to generate a backtrace on this asterisk server then this evening, and get back here with results. By: Paul Belanger (pabelanger) 2011-10-19 09:37:33.456-0500 Thank you for your bug report. In order to move your issue forward, we require a backtrace[1] from the core file produced after the crash. Also, be sure you have DONT_OPTIMIZE enabled in menuselect within the Compiler Flags section, then: make install After enabling, reproduce the crash, and then execute the backtrace[1] instructions. When complete, attach that file to this issue report. [1] https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace By: Jonas Kellens (jonaskellens) 2011-10-19 13:25:05.587-0500 GDB trace not working : # gdb -se "asterisk" -c core.sip1.server.be | tee /tmp/backtrace.txt [New Thread 12325] [New Thread 12324] [New Thread 12323 warning: ] [New Thread 12322] no loadable sections found in added symbol-file system-supplied DSO at 0x7fffe65fd000 Core was generated by `/usr/sbin/asterisk -f -vvvg -c'. Program terminated with signal 11, Segmentation fault. #0  0x0000000000000020 in ?? () (gdb) bt #0  0x0000000000000020 in ?? () (gdb) bt full #0  0x0000000000000020 in ?? () No symbol table info available. What is this ??? What am I doing wrong ? By: Richard Mudgett (rmudgett) 2011-10-19 13:44:10.949-0500 Gdb must be run with the same permissions that Asterisk had when it crashed. By: Jonas Kellens (jonaskellens) 2011-10-19 13:50:39.114-0500 Strange... asterisk is run as root... and I use gdb also as root... [root@sip1 admin]# ps aux | grep asterisk root     21262  0.0  0.0  65936   592 pts/0    S    20:39   0:00 /bin/sh /usr/sbin/safe_asterisk root     21264  4.0  2.2 589040 39524 pts/0    Sl   20:39   0:24 /usr/sbin/asterisk -f -vvvg -c root     21678  0.0  0.0  61184   768 pts/0    S+   20:50   0:00 grep asterisk By: Jonas Kellens (jonaskellens) 2011-10-22 10:46:55.672-0500 Hello, this backtrace thing is till not working : [root@sip1 admin]# ls -l -rw------- 1 root root 77074432 Oct 19 20:11 core.sip1.server.be [root@sip1 admin]# gdb -se "asterisk" -ex "bt full" -ex "thread apply all bt" --batch -c core.sip1.server.be > backtrace.txt asterisk: No such file or directory. warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fffe65fd000 By: Leif Madsen (lmadsen) 2011-10-31 13:37:33.025-0500 I'm closing this as it being reported against a version of Asterisk that is no longer being supported. Additionally, please use the asterisk-users mailing list or the #asterisk IRC channel for help with producing a valid backtrace.