[asterisk-bugs] [Asterisk 0009579]: Asterisk dies unexpectedly, cannot find out reason why. I suspect due to nagios monitoring on management interface.

[noreply at bugs.digium.com]

The following issue has been CLOSED 
====================================================================== 
http://bugs.digium.com/view.php?id=9579 
====================================================================== 
Reported By:                amegyeri
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   9579
Category:                   Core/General
Reproducibility:            random
Severity:                   crash
Priority:                   normal
Status:                     closed
Asterisk Version:            1.2.17  
SVN Branch (only for SVN checkouts, not tarball releases):  1.2  
SVN Revision (number only!):  
Disclaimer on File?:        No 
Request Review:              
Resolution:                 open
Fixed in Version:           
====================================================================== 
Date Submitted:             04-23-2007 14:26 CDT
Last Modified:              08-02-2007 15:44 CDT
====================================================================== 
Summary:                    Asterisk dies unexpectedly, cannot find out reason
why. I suspect due to nagios monitoring on management interface.
Description: 
Asterisk died over 10-20 times today, in unexpected and non-periodical
intervals. It is running on a XEN virtual machine, and the only recent
change is that I have introduced a nagios monitoring. Nagios checks
asterisk every minute.
After a random time, asterisk simly drops out my remote unix connection
(asterisk -r). No entries even in the FULL log.
I suspect this is up to some issue in the management interface, however
I'm not sure.
The same nagios checks another asterisk server (though it is a remote one,
not localhost), and that one runs flawlessly.
The issue happens with version 1.2.17, the other asterisk is 1.2.14.
Any help would be highly welcome. 
How could I try to locate the problem? Even the highest level logs do not
show anything at all, and there is no common pattern in the logs before it
crashes...


====================================================================== 

---------------------------------------------------------------------- 
 murf - 08-02-07 15:44  
---------------------------------------------------------------------- 
I apologize for this, but I'm closing this bug because the time for 1.2
support is now expired. 

All hope is not lost, tho! Hopefully, there will come a time and chance
for you
to move your installation to 1.4; and if this problem persists in 1.4, you
are more than welcome to re-open this bug, or open a new one, and we'll see
if it can't be solved.

If the problem disappears in 1.4, all I can say is Yay!; but if not, we'll
dive back in and sort it out.

Sorry for this inconvenience! We hope you'll stick with it and try this on
1.4. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
08-02-07 15:44  murf           Note Added: 0068349                          
======================================================================