Summary:	ASTERISK-15832: channel.c:2753 __ast_read: Exception flag set on 'SIP/XXXXXXXX-000000e3', but no exception handler
Reporter:	Hamid Bilal (hamidbilal)	Labels:
Date Opened:	2010-03-17 11:02:11	Date Closed:	2011-06-07 14:00:36
Priority:	Critical	Regression?	No
Status:	Closed/Complete	Components:	Applications/app_dial
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:	( 0) gdb.txt ( 1) gdb1030.txt ( 2) gdb1230.txt ( 3) jeff-gdb.txt
Description:	Hi All! We are using asterisk 1.6.2 but asterisk get crashed very often. We start receiving  error channel.c:2753 __ast_read: Exception flag set on 'SIP/XXXXXXXX-000000e3', but no exception handler Then asterisk get restart automatically. Dial plan is very simple and it also include our own developed application whcich make simple querys to mysql db. Please suggest us solution. I have also attached gdb output.
Comments:	By: Leif Madsen (lmadsen) 2010-03-17 14:02:58 Your backtrace has a lot of <value optimized out> in it, which typically means the DONT_OPTIMIZE flag was enabled in menuselect prior to installing Asterisk. Could you provide a backtrace after enabling this option? More information is available in the doc/backtrace.txt file of your Asterisk source. By: Leif Madsen (lmadsen) 2010-03-17 14:03:23 Also, please provide the dialplan and exact version you're running in order to attempt to reproduce this. By: Hamid Bilal (hamidbilal) 2010-03-17 14:46:05 Ok. I will enable it and get back to you shortly. By: Leif Madsen (lmadsen) 2010-03-18 14:09:27 Please also provide the dialplan information for exactly how you are causing this crash to happen. By: Hamid Bilal (hamidbilal) 2010-03-18 16:33:33 I have compiled with DONT_OPTIMIZE flag. Now asterisk is running since last 22 hours and did not crash even once. I am still investigating the reason System uptime: 22 hours, 30 minutes, 46 seconds Last reload: 22 hours, 30 minutes, 46 seconds Asterisk version is 1.6.2.5 Here is my dial plan. exten => _8998.,1,Authenticat() ; MySQL routine exten => _8998.,2,Dial(SIP/Uk0/11022${EXTEN:4}) exten => h,1,NoOp( total duration is ${CDR(billsec)}) exten => h,2,UpdateCDR() ; MySQL routine By: Jeff Hoppe (jhoppebugs) 2010-07-15 08:14:51 I am having the same issue.   Asterisk version 1.6.2.6 will occasionally crash unexpectantly.  Sometimes it takes 7 days, sometimes it takes 1 day before it will suddenly restart.   I get this alot as well: Exception flag set on 'SIP/XXXXXXXX-000000e3', but no exception handle. I notice that this bug has no notes since March.  I assume hamidbilal has not had a crash since. I don't know if I should create a new bug report or add on to this one.  I decided to add on to this one. I will catch a backtrace the next time it auto restarts and send it to this bug in the tracker. By: Leif Madsen (lmadsen) 2010-07-15 09:29:01 Console output just prior to the crash may also be helpful. Be sure your Asterisk is compiled with DONT_OPTIMIZE in order to produce a useful backtrace. --- Thank you for your bug report. In order to move your issue forward, we require a backtrace from the core file produced after the crash. Please see the doc/backtrace.txt file in your Asterisk source directory. 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 instructions in doc/backtrace.txt. When complete, attach that file to this issue report. Thanks! By: Jeff Hoppe (jhoppebugs) 2010-07-15 09:40:23 Is there a way to get console output when Asterisk just restarts on its own? By: Leif Madsen (lmadsen) 2010-07-15 11:52:53 Have it written to a log file. By: Jeff Hoppe (jhoppebugs) 2010-07-16 10:52:08 I added jeff-gdb.txt from our crash yesterday.  I will include console output and jeff-2-gdb.txt at our next crash. By: Jeff Hoppe (jhoppebugs) 2010-07-16 12:35:58 gdb1030.txt and gdb1230.txt have more information then the previously loaded jeff-gdb.txt. By: Jeff Hoppe (jhoppebugs) 2010-07-20 09:06:56 I am going to stop adding to this thread.  Please ignore my last two additions.   I have upgraded to the 1.6.2.9 and will see if this solves my issue.  I will start a new bug tracker issue if this version crashes and no one else has the same issue already added. By: Leif Madsen (lmadsen) 2010-07-20 11:13:00 OK I'm going to close this issue then. Please open a new issue when you have additional information to move this forward. Thanks!