[Asterisk-Users] executing a reload under stress in Asterisk

[Franklin Webb]

Fellow list members,
 
I was wondering if anyone else out there has had issues with Asterisk
after doing a reload with a number of users on.
 
I fixed a minor bug in my dial plan and did a reload, and I seemed to
have a corrupt config file afterwards.  I am also considering there may
have been some kind of an issue with copying the files.  I keep a
seperate copy on a test server, and I copied over to Asterisk before
doing the reload.  I was getting errors that were basically indicating
parts of my dial plan were missing (error indicated I was sending
control to priorities that did not exist but they should have).  I
stopped Asterisk and rebooted the machine and the errors still occured.
I copied the files over from my test machine a second time, restarted
Asterisk, and everything worked beautifully (as it had on the test
machine during the whole process).
 
I have some concern the reload may have been related to this problem,
which is serious because it pretty much took down our ability to take
calls.  It seems like it could have been an error occuring in the
process of copying hte files also.  For the record I ftp the files
between machines to a seperate directory and then "cp" them into the
asterisk config directory.
 
Any feedback especially on doing reloads with high call volume and using
queues etc, would be appreciated.
 
Thanks in advance,

Frank Webb
Inter Media Marketing Solutions
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20051212/63448ce1/attachment.htm