Summary: | ASTERISK-19193: Asterisk ended with exit status 134 | ||
Reporter: | Gerald Lim (teotech) | Labels: | |
Date Opened: | 2012-01-12 08:04:55.000-0600 | Date Closed: | 2012-01-30 06:58:54.000-0600 |
Priority: | Major | Regression? | |
Status: | Closed/Complete | Components: | |
Versions: | 1.8.7.2 | 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.2 | Attachments: | ( 0) Bt_and_Bt_full_log.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) 2012-01-12 08:05:51.361-0600 BT and BT full log attached. By: Matt Jordan (mjordan) 2012-01-12 09:48:50.654-0600 1.8.7 has some known issues with chan_dahdi and sig_pri that were resolved in 1.8.8.1. Can you retest with that version of Asterisk? By: Gerald Lim (teotech) 2012-01-29 02:10:24.399-0600 Upgraded to 1.8.8.1 and the problem is solved. Thanks. |