[asterisk-bugs] [Asterisk 0014562]: safe_asterisk can get multiple instances if killproc escalates to SIGKILL in service asterisk restart

[Asterisk Bug Tracker]

The following issue has been set as RELATED TO issue 0015846. 
====================================================================== 
https://issues.asterisk.org/view.php?id=14562 
====================================================================== 
Reported By:                davidw
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   14562
Category:                   General
Reproducibility:            have not tried
Severity:                   minor
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           SVN 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-02-26 12:37 CST
Last Modified:              2009-10-21 11:05 CDT
====================================================================== 
Summary:                    safe_asterisk can get multiple instances if killproc
escalates to SIGKILL in service asterisk restart
Description: 
Weird behaviour was observed in which we got Remote UNIX connection and
disconnections continuously repeated.  It turned out that we had two copies
of safe_asterisk running.

Although I didn't do this myself, I believe this was the result of using
"service asterisk restart" on an asterisk that was in distress (deadlock,
at least).  I think what happened is that the killproc escalated to
SIGKILL, which was not recognized by the original safe_asterisk, so it
continued to run.  Meanwhile the new safe_asterisk was started, but both
checks for a running asterisk failed, either because it was too much in
distress, or because the console listener had shut down in response to
killproc's SIGTERM.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0015846 Asterisk is looking in the wrong locati...
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-10-21 11:05 lmadsen        Relationship added       related to 0015846  
======================================================================