Summary: | ASTERISK-07942: Asterisk crashes on app_queue.c | ||
Reporter: | sk2133 (sk2133) | Labels: | |
Date Opened: | 2006-10-17 04:56:13 | Date Closed: | 2011-06-07 14:00:20 |
Priority: | Critical | Regression? | No |
Status: | Closed/Complete | Components: | Applications/app_queue |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ( 0) btfull_061106.txt ( 1) btfull_071106.txt ( 2) btfull_11_Oct_2006.txt ( 3) core-02Nov2006.txt | |
Description: | asterisk version: Asterisk 1.2.12.1 built by root @ haso on a i686 running Linux on 2006-09-26 23:08:06 UTC Linux distro: Gentoo 2.6.12.5 #1 SMP This issue is not readily reproducable but it does cause asterisk to crash. The crash happened while removing queues and reloading while a caller hangs up (on ISDN PRI call). On the hangup, asterisk crashes. We are reying to replcate this so that it is reproducable. I have attached the full backtrace of the core file. The configuration settings are also attached. | ||
Comments: | By: Joshua C. Colp (jcolp) 2006-10-19 15:17:27 The attached file doesn't look like a bt full... can you attach a different one/real one? By: jmls (jmls) 2006-11-01 13:14:33.000-0600 sk2133, please attach a bt full as requested. Thanks. By: sk2133 (sk2133) 2006-11-02 08:05:13.000-0600 That is the result of a BT full. I cannot get anything more on this. This has happened once again today and the output is attached. By: sk2133 (sk2133) 2006-11-02 08:21:41.000-0600 This is a user that is using asterisk in a call centre environment. They have 45 extensions registered. They have 19 queues. They are using a combination of agentcallbacklogin as well as members in queues There are several hundred changes to the queues.conf on a daily basis. This is because they have had issues with agentcallbacklogin they are adding and removing members as required during the course of the day. They have 3 x ISDN PRI lines coming into a TE410P card. All inbound traffic comes in on the ISDN lines and goes to queues. By: BJ Weschke (bweschke) 2006-11-02 08:25:31.000-0600 hard to say for sure, but it looks like your channel list memory space is getting pretty messed up from a quick review of the bt. Are you calling "show channels verbose" from within the manager? By: sk2133 (sk2133) 2006-11-02 09:28:37.000-0600 This is on an asterisk with a fromt end GUI. This gui has a monitoring page that when displayed does a show channels verbose every 10 seconds on asterisk. By: sk2133 (sk2133) 2006-11-02 10:30:45.000-0600 Do you know what is causing the channel list memory space to get messed up? By: jmls (jmls) 2006-11-02 13:28:16.000-0600 could this be related to ASTERISK-7811 ? By: sk2133 (sk2133) 2006-11-03 10:04:50.000-0600 The user also received the following today: Agent 5002 was logged into phone 6053 and was taking calls fine. Then Agent 5002 stopped receiving calls. I looked on the Asterisk CLI and typed in show agents it showed that Agent 5002 was still on a call despite them not actually being on a call. I asked that agent to then log out when they did I got the following messages: Nov 3 11:14:48 ERROR[25031]: ../include/asterisk/lock.h:338 __ast_pthread_mutex_unlock: chan_agent.c line 843 (agent_hangup): mutex '&p->app_lock' freed more times than we've locked! Nov 3 11:14:48 ERROR[25031]: ../include/asterisk/lock.h:351 __ast_pthread_mutex_unlock: chan_agent.c line 843 (agent_hangup): Error releasing mutex: Operation not permitted -- agent_call, call to agent '5002' call on 'SIP/6053-085a2000' Nov 3 11:14:50 WARNING[18993]: file.c:587 ast_readaudio_callback: Failed to write frame Nov 3 11:14:50 WARNING[16665]: channel.c:787 channel_find_locked: Avoided initial deadlock for '0x41418038', 10 retries! Does this shed any light on this? By: sk2133 (sk2133) 2006-11-07 04:00:08.000-0600 I have attached another 2 backtraces. We have upgraded the asterisk version to 1.2.13 as of Saturday 4th Nov. Any feedback on these back traces would be greatly appreciated. By: sk2133 (sk2133) 2006-11-08 06:29:24.000-0600 The backtrace called btfull_071106.txt looks like it was due to agent login issues already in bug 7890 & 8064. In the backtrace called btfull_061106.txt, agent login was not being used. They have 16 queues all using members. Any ideas from this backtrace? By: Serge Vecher (serge-v) 2007-02-28 13:45:13.000-0600 ok, what's the status with the latest 1.2 checked out from svn? By: Joshua C. Colp (jcolp) 2007-06-07 19:09:24 It has been quite some time now. If this is still an issue with the latest version of things please reopen with new backtrace. Thanks. |