Summary:	ASTERISK-08466: queue causes a crash
Reporter:	gdhgdh (gdhgdh)	Labels:
Date Opened:	2007-01-03 03:58:53.000-0600	Date Closed:	2007-02-21 14:59:54.000-0600
Priority:	Critical	Regression?	No
Status:	Closed/Complete	Components:	Applications/app_queue
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:	( 0) backtrace4.txt
Description:	I created /etc/asterisk/meetme.conf thusly: [rooms] conf => 9000 Did a 'reload', and dialled into 311072 => MeetMe 9000|cs. I heard ' You are the only person in this...' and Asterisk crashed. Full bt + thread trace attached. Asterisk was already compiled with DONT_OPTIMIZE from previous crashes! ;/ This is desperate :/
Comments:	By: Serge Vecher (serge-v) 2007-01-03 09:00:32.000-0600 Do you have a snippet of the console log just prior to the crash? By: gdhgdh (gdhgdh) 2007-01-03 09:23:36.000-0600 Nope, sorry - it's scrolled out of the buffer many hours ago :/ I checked /var/log/asterisk/messages for 'MeetMe' but nothing matched, yet logger.conf says: messages => notice,warning,error,verbose I would have hoped that would be enough :/ By: Clod Patry (junky) 2007-01-04 06:02:41.000-0600 which kernel module do you have linked with zaptel? "lsmod|grep zaptel" By: gdhgdh (gdhgdh) 2007-01-04 06:21:34.000-0600 zaptel                217704  310 wanpipe,zttranscode wanpipe for a Sangoma A104D, using their newest stable release. By: Tilghman Lesher (tilghman) 2007-01-07 15:27:43.000-0600 This coredump was caused by app_queue, not app_meetme.  Please upload your queues.conf. By: gdhgdh (gdhgdh) 2007-01-10 04:26:26.000-0600 We were using realtime queues, with a small static one. I don't have copies now because we reverted to Asterisk 1.2, as 1.4 was just too unstable :( By: Clod Patry (junky) 2007-01-25 23:55:46.000-0600 Is someone else having these issues? By: warlock52 (warlock52) 2007-01-27 18:12:25.000-0600 Yes We are and have reverted back to 1.2 as well. At the moment we are testing the branch version but it seems to have the same issues and unfortunately adds variouys other problems so we have not been able to go back into production. By: Serge Vecher (serge-v) 2007-02-01 08:34:46.000-0600 gdhgdh, warlock: can you handle setting up a test server with 1.4 branch and reproducing the problem on it, so we can get this issue nailed down with your debug info? By: Serge Vecher (serge-v) 2007-02-21 14:59:53.000-0600 ok, well there have been several changes in 1.4 branch for affected areas. If you update your production systems and they exhibit the same problem again, please reopen the bug with required debugging info.