[asterisk-users] reload stopping EVERYTHING on CLI and causing havoc.

[Steve Totaro]

Three options.
1.  Open a bug report and hope someone fixes it.
2.  Use AMI AND write the new .conf entry at the same time!
3.  Reload queues when empty.

I don't really understand what the issue is with number two.  Although
I am not a programmer, I can see why reloading queues with callers in
the queues might be a problem.

Thanks,
Steve Totaro

On Thu, May 22, 2008 at 3:38 PM, Mark Hamilton <mark.h at cage151.com> wrote:
> That's true. But that's exactly why it's not used and conf is much easier.
>
> -----Original Message-----
> From: asterisk-users-bounces at lists.digium.com
> [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Steve Totaro
> Sent: May 22, 2008 3:34 PM
> To: Asterisk Users Mailing List - Non-Commercial Discussion
> Subject: Re: [asterisk-users] reload stopping EVERYTHING on CLI and causing
> havoc.
>
> You can create queues via AMI although it won't survive a restart.
>
> Thanks,
> Steve Totaro
>
> On Thu, May 22, 2008 at 3:25 PM, Mark Hamilton <mark.h at cage151.com> wrote:
>> Thanks Steve.
>> Using 1.4.18, and I don't think it's fixed.
>> The unresponsiveness is permanent - although I do try to not reload during
>> work hours, sometimes it's just necessary.. especially when someone asks
> for
>> a new queue.
>>
>> -----Original Message-----
>> From: asterisk-users-bounces at lists.digium.com
>> [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Steve Totaro
>> Sent: May 22, 2008 3:12 PM
>> To: Asterisk Users Mailing List - Non-Commercial Discussion
>> Subject: Re: [asterisk-users] reload stopping EVERYTHING on CLI and
> causing
>> havoc.
>>
>> On Thu, May 22, 2008 at 2:02 PM, Sherwood McGowan
>> <sherwood.mcgowan at gmail.com> wrote:
>>> Mark Hamilton wrote:
>>>>
>>>> Hi,
>>>>
>>>> Yesterday I made a change in queues.conf and so tried doing a reload
>>>> app_queue.so in the CLI. (Using 1.4.18). It didn't seem to do
>>>> anything, infact all action on CLI stopped.
>>>>
>>>> Then, I did a reload. Same thing.
>>>>
>>>> After that there was no other way.. because even stop now wouldn't
>>>> work, so I did a service asterisk restart
>>>>
>>>> And then asterisk kept giving the same thing on prompt "Died
>>>> successfully" and all that it usually says when you issue a stop now,
>>>> except it kept showing that on root prompt after doing a service
>>>> asterisk restart.
>>>>
>>>> Did a killall asterisk, and finally it stopped.
>>>>
>>>> Then started asterisk service. It was fine.
>>>>
>>>> Did a full restart at night, and it was fine.
>>>>
>>>> NOW, I wanted to do a reload again today mid-day when in full use, and
>>>> it still didn't work, and ALL of the above happened again.
>>>>
>>>> --
>>>>
>>>> How do I diagnose what's causing this?
>>>>
>>>> Thanks,
>>>>
>>>> Mark.
>>>>
>>>> ------------------------------------------------------------------------
>>>>
>>>> _______________________________________________
>>>> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>>>>
>>>> asterisk-users mailing list
>>>> To UNSUBSCRIBE or update options visit:
>>>>    http://lists.digium.com/mailman/listinfo/asterisk-users
>>> I've had this problem before, haven't debugged it. I definitely look
>>> forward to hearing what is said about this.
>>>
>>> Example from my recent experience, I wanted to restart the server and so
>>> did
>>>
>>> pbx0*CLI> restart now
>>>
>>> But nothing happened...system continued to allow calls to take place.
>>> I've found that sometimes exiting and reconnecting to the CLI helps, but
>>> there have been a couple occasions where NOTHING would allow the server
>>> to restart save for a reboot. Even killall asterisk didn't kill the
>>> process....
>>>
>>> Sherwood McGowan
>>>
>>
>> You are using Asterisk 1.2.x?  I have seen this many, many times.
>>
>> Sometimes the CLI becomes unresponsive, sometimes queues crap out or
>> stops delivering calls to agents, sometimes it just takes a bit and
>> then becomes responsive again.
>>
>> The rule of thumb is don't reload queues when there are people in
>> queue, at least that seems to eliminate the problems I have seen.
>> Makes sense too.
>>
>> Not sure if it is fixed in 1.4.
>>
>> Thanks,
>> Steve Totaro
>>
>> _______________________________________________
>> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>>
>> asterisk-users mailing list
>> To UNSUBSCRIBE or update options visit:
>>   http://lists.digium.com/mailman/listinfo/asterisk-users
>>
>>
>> _______________________________________________
>> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>>
>> asterisk-users mailing list
>> To UNSUBSCRIBE or update options visit:
>>   http://lists.digium.com/mailman/listinfo/asterisk-users
>>
>
> _______________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-users
>
>
> _______________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-users
>