Summary:	ASTERISK-14981: channel.c:2711 __ast_read: Exception flag set on 'SIP/xxx', but no exception handler
Reporter:	Michael Cramer (micc)	Labels:
Date Opened:	2009-10-13 16:17:33	Date Closed:	2011-07-27 09:18:36
Priority:	Minor	Regression?	No
Status:	Closed/Complete	Components:	Channels/General
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:	( 0) messages.broken.gz
Description:	I'm running asterisk 1.6.1.6 and have been seeing this problem for about a week or two. This happens seemingly randomly and on different channels. And when it happens it fills the logs and the CLI with these messages as fast as it can, jumping the cpu way up, probably 100% on one core. I will try to get a sip debug when it happens, but I wanted to at least get this on the issue tracker in case someone already knows what it is. ****** ADDITIONAL INFORMATION ****** I have the patch for urgent voicemails installed.
Comments:	By: Michael Cramer (micc) 2009-10-13 16:20:12 We also have the multi-tenant parking patch installed from issue 0015538 By: Elazar Broad (ebroad) 2009-10-14 11:01:06 Is there any reason why this needs to be marked private? By: Michael Cramer (micc) 2009-10-16 13:04:28 This can be public I guess. I was unable to get a good sip debug trace because it scrolled too fast and filled up my scroll back buffer. By: Elazar Broad (ebroad) 2009-10-18 14:58:35 Configure logger.conf to dump debug messages to a file. By: Matt King, M.A. Oxon. (kebl0155) 2009-11-04 19:36:15.000-0600 I don't know if this is any help, but I'm getting the same error message on Asterisk 1.6.0.3 when I load test it to approx. 100 simultaneous SIP calls. I have attached a full SIP debug log.  Asterisk has to be killed after this error, or will eventually segfault. We're just using standard ParkedCall (no multi-tenant patch), but I do think it's related to the call parking system, as if I switch to Bridge instead, the problem goes away. By: Leif Madsen (lmadsen) 2009-12-21 09:48:53.000-0600 Is anybody able to reproduce this on the latest Asterisk versions? If so, any idea as to what leads to this happening so it can be reproduced? By: Michael Cramer (micc) 2009-12-21 13:47:18.000-0600 I've seen a few of these messages in the latest builds 1.6.1.10 and 1.6.1.12, but never filling up the log again. By: Leif Madsen (lmadsen) 2009-12-21 16:52:10.000-0600 I'm going to close this for now as it appears it's just a logging message, and isn't as bad as it used to be. If an issue arises again, please file a new issue against the latest available Asterisk version. Thanks! Leif. By: Michael Cramer (micc) 2010-05-07 13:05:31 I just had this problem happen again and I'm running 1.6.1.18. I think the channel was on hold because the last thing it said after it stopped was stopping music on hold. By: Joe Cracchiolo (jjcinaz) 2010-05-18 23:00:19 This is definitely an issue.  This condition will consume all cycles on a core and if it happens on too many cores at once, Asterisk stops responding.  The condition is mitagated because the ast_log() call delays the thread somewhat.  Take that log message out and this quickly kills a server. By: Leif Madsen (lmadsen) 2010-05-19 10:27:27 As the 1.6.0 and 1.6.1 branches are only maintained for security fixes now, is this an issue that can be reproduced on the 1.6.2 branch? -- Per the Asterisk maintenance timeline page at http://www.asterisk.org/asterisk-versions maintenance (bug) support for the 1.6.0 and 1.6.1 branches has ended. For continued maintenance support please move to the 1.6.2 branch. More information on this change can be found in the release announcement: http://www.asterisk.org/node/49924 By: damian draus (darakdams) 2011-02-16 01:37:33.000-0600 we have the same thing happening in version 1.6.2.13 WARNING[28537] channel.c: Exception flag set on 'SIP/XXXXXXXXX', but no exception handler By: Ken Leland (kenlee) 2011-03-02 22:03:32.000-0600 We had to comment that line out.  It was being written a whopping 90k times per second on my system before the system buckled under the load. By: Russell Bryant (russell) 2011-07-27 09:18:29.752-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 If this is still an issue, please open a new issue so it can be re-triaged appropriately. Thanks!