I upgraded to 1.2.9.1 today. It was working fine until after lunch. After running since 8am it stopped around 1pm. People could still call in on our PRI via Zap. But, you couldn't use the dialplan (would just sit there)... the queue went to dead air.. and 'show agents' 'show queues' 'zap show channels' did nothing.. just returned back to the asterisk prompt with no information. Calls there were up (queue calls) continued to work. Any thoughts on what might have happened?
On Tuesday 20 June 2006 12:58, Matt wrote:> I upgraded to 1.2.9.1 today. It was working fine until after lunch. > After running since 8am it stopped around 1pm.Upgraded from what version?> People could still call in on our PRI via Zap. But, you couldn't use > the dialplan (would just sit there)... the queue went to dead air.. > and 'show agents' 'show queues' 'zap show channels' did nothing.. just > returned back to the asterisk prompt with no information.Could you connect in with gdb -p [main pid of asterisk] and give a 'bt full' command? -A.
Arg... ok it just crashed again. Lasted about 7 hours this time. On 6/20/06, Matt <mhoppes@gmail.com> wrote:> I use FOP... I believe that that uses manager fairly extensively. > > Also... about 2-4 hours prior to the crash I had been playing around > with getting new MOH working.. .and had reload res_musiconhold several > times (5 or 6) > > > Just curious, do you use the manager interface extensively? > > > > _______________________________________________ > > --Bandwidth and Colocation provided by Easynews.com -- > > > > Asterisk-Users mailing list > > To UNSUBSCRIBE or update options visit: > > http://lists.digium.com/mailman/listinfo/asterisk-users > > >
I guess that was a yes to both my scenarios, reloads and manager interface. It is still running just not responsive? Matt wrote:> Arg... ok it just crashed again. Lasted about 7 hours this time. > > On 6/20/06, Matt <mhoppes@gmail.com> wrote: >> I use FOP... I believe that that uses manager fairly extensively. >> >> Also... about 2-4 hours prior to the crash I had been playing around >> with getting new MOH working.. .and had reload res_musiconhold several >> times (5 or 6) >> >> > Just curious, do you use the manager interface extensively? >> > >> > _______________________________________________ >> > --Bandwidth and Colocation provided by Easynews.com -- >> > >> > Asterisk-Users mailing list >> > To UNSUBSCRIBE or update options visit: >> > http://lists.digium.com/mailman/listinfo/asterisk-users >> > >> > _______________________________________________ > --Bandwidth and Colocation provided by Easynews.com -- > > Asterisk-Users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users >
----- Steve Totaro <stotaro@asteriskhelpdesk.com> wrote:> My system never stops processing calls but it slows. On the CLI, it > may > take five minutes for a command to execute but it does finally execute > > (such as sip show peers or show channels) And calls to the agents sit > > in queue for a while before being delivered to an agent even thought > he > agent is available.There is a problem that has been identified that was caused by a recent change in Asterisk, that may be the reason you are seeing these symptoms. It would appear to only affect people using chan_agent, and then only if the agents are transferring calls they receive. I am still working on a proper solution for this issue, but hope to get it resolved in the next day or so. Stay tuned and watch for a new release :-) -- Kevin P. Fleming Senior Software Engineer Digium, Inc.
Kevin P. Fleming wrote:> ----- Steve Totaro <stotaro@asteriskhelpdesk.com> wrote: > >> My system never stops processing calls but it slows. On the CLI, it >> may >> take five minutes for a command to execute but it does finally execute >> >> (such as sip show peers or show channels) And calls to the agents sit >> >> in queue for a while before being delivered to an agent even thought >> he >> agent is available. >> > > There is a problem that has been identified that was caused by a recent change in Asterisk, that may be the reason you are seeing these symptoms. It would appear to only affect people using chan_agent, and then only if the agents are transferring calls they receive. > > I am still working on a proper solution for this issue, but hope to get it resolved in the next day or so. Stay tuned and watch for a new release :-) > >Kevin, Thanks for the update. We are a busy call center and asterisk just stopped running yesterday at a fairly peak hour. We dropped 95 calls. Asterisk just needed to be restarted. This morning I am changing to boot to safe_asterisk. Then we will have a core dump and asterisk should restart if it happens again. There is absolutely no reason in any of the system or asterisk logs explaining the crash. We do not do any transfers between agents but use queues and chan_agent extensively, we also use the manager interface to update agent penalties every fifteen minutes (as well as other functions). We use alot of .call files to originate calls as well. Hopefully this next release might help with our issue as well. Thanks, Steve