[Home]

Summary:ASTERISK-19135: Asterisk ended with exit status 134
Reporter:Gerald Lim (teotech)Labels:asterisk
Date Opened:2011-12-29 03:15:40.000-0600Date Closed:2011-12-30 16:25:42.000-0600
Priority:CriticalRegression?
Status:Closed/CompleteComponents:
Versions:1.8.7.0 Frequency of
Occurrence		Constant
Related
Issues:
Environment:Kernel Linux(x86_64) 2.6.18, Elastix ver 2.2.0. freePBX ver 2.8.1, dahdi 2.4.1.2Attachments:( 0) bt_and_bt_full.txt
( 1) bt_and_bt_full_GOOD.txt
( 2) Bt_and_Bt_full_log_Updated.txt
Description:We're running Elastix 2.2.0, with Asterisk 1.8.7.0 on CentOS. We are running into frequent Segmentation faults, which usually crashes once or twice a day and automatically restart asterisk. There is no noticable error log, we can only see that a reload has been done just after the error time but nothing [notice] error just before the crash. Can you please advise please.

Error at the prompt:

[root@pbx ~]# /usr/sbin/safe_asterisk: line 145: 21799 Segmentation fault (core dumped) nice -n $PRIORITY ${ASTSBINDIR}/asterisk -f ${CLIARGS} ${ASTARGS} > /dev/${TTY} 2>&1 < /dev/${TTY}
Asterisk ended with exit status 139
Asterisk exited on signal 11.
Automatically restarting Asterisk.


[root@pbx ~]# /usr/sbin/safe_asterisk: line 145: 1652 Aborted (core dumped) nice -n $PRIORITY ${ASTSBINDIR}/asterisk -f ${CLIARGS} ${ASTARGS} > /dev/${TTY} 2>&1 < /dev/${TTY}
Asterisk ended with exit status 134
Asterisk exited on signal 6.
Comments:By: Gerald Lim (teotech) 2011-12-29 03:17:38.589-0600

Bt and BT full error log
By: Gerald Lim (teotech) 2011-12-29 08:36:57.520-0600

Real Error Log
By: Matt Jordan (mjordan) 2011-12-29 08:51:37.849-0600

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: Gerald Lim (teotech) 2011-12-29 09:07:11.805-0600

Dear Matt,

I can't see any <value optimized out> in the bt and bt full log. Please consider the filename bt and bt full GOOD.txt log file.

There is actually not clear explaination about how to use the DONT_OPTIMIZE function.

Can you clarify this to me please. How to proceed to install or use the DONT_OPTIMIZE function?

I have yum install the gbd and then type the command gdb asterisk /tmp/corefile...

By: Matt Jordan (mjordan) 2011-12-29 14:43:28.524-0600

Gerald,

The backtraces you've attached contain no debug symbols.  There is no way for us to determine where Asterisk crashes when the only information contained in the backtrace is "??".  From your "good" backtrace, its possible to ascertain that its dying in chan_sip during a scheduled deletion, but that's still like trying to find a needle in a stack of needles.

In order for you to obtain a useful backtrace, you will need to checkout the Asterisk source corresponding to the version of Asterisk you are running with [1].  From there, you'll need to compile it using the menuselect tool - in there you can specify to not optimize out any methods.  This produces usable backtraces in the event of a crash.

[1] https://wiki.asterisk.org/wiki/display/AST/Installing+Asterisk+From+Source
By: Gerald Lim (teotech) 2011-12-30 02:21:05.320-0600

Dear Matt,

Actually i have install the Elastix 2.2 distro which have Asterisk 1.8.7.0. From this distro, i do not have the Menuselect option. How can i have the menuselect from this distro which is in production. Should a recompile?
By: Paul Belanger (pabelanger) 2011-12-30 09:29:09.294-0600

The issue tracker is not a place to get support, please using the mailing lists or IRC.
By: Matt Jordan (mjordan) 2011-12-30 16:25:35.282-0600

As Paul stated, we cannot provide support for Elastix.

If you'd like support for Asterisk, please use the Asterisk mailing lists or the IRC chatroom #asterisk.  That would be the appropriate place to learn how to configure and install Asterisk from source.

When you are able to produce a backtrace using the previous instructions from a supported version of Asterisk compiled with the DONT_OPTIMIZE flag, please request a bug marshal in #asterisk-bugs on the IRC network irc.freenode.net to reopen the issue.  Further information can be found at http://www.asterisk.org/developers/bug-guidelines


By: Gerald Lim (teotech) 2012-01-12 08:01:24.078-0600

Update Bt as requested.