[asterisk-bugs] [Asterisk 0010598]: "logger rotate" leads to logging getting deadlocked and asterisk won't stop

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10598 
====================================================================== 
Reported By:                stevedavies
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   10598
Category:                   Core-General
Reproducibility:            always
Severity:                   block
Priority:                   normal
Status:                     new
Asterisk Version:            SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 81356 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             08-29-2007 16:57 CDT
Last Modified:              08-30-2007 02:47 CDT
====================================================================== 
Summary:                    "logger rotate" leads to logging getting deadlocked
and asterisk won't stop
Description: 

Doing a "logger rotate" results in logging getting "stuck".  No new full /
messages file is created and Asterisk won't stop.

Observe:

...
voipconnect_2*CLI> logger rotate
[Aug 29 23:59:05] Asterisk Event Logger restarted
[Aug 29 23:59:05] Asterisk Queue Logger restarted
voipconnect_2*CLI> 
voipconnect_2*CLI> exit
voipconnect_2 customers # ls /var/log/asterisk/fu*
/var/log/asterisk/full.0  /var/log/asterisk/full.1.gz 
/var/log/asterisk/full.2.gz  /var/log/asterisk/full.4.gz
/var/log/asterisk/full.1  /var/log/asterisk/full.2    
/var/log/asterisk/full.3.gz  /var/log/asterisk/full.5.gz

You see that there is no new "full" file created.  Logging isn't going to
the old but renamed file either - its going nowhere.

Telling asterisk to stop now doesn't work (or didn't work the couple of
times I tried it.  I needed to kill asterisk process)


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

---------------------------------------------------------------------- 
 jamesgolovich - 08-30-07 02:47  
---------------------------------------------------------------------- 
This bug was introduced when the code to not reload unchanged config files
was added.  If the config file hasn't been changed then make_logchannel is
never executed that will reopen the file.  This is a simple fix to the
problem, and mimics the behavior of the other 2 logs that have a hardcoded
fopen.

If we want to go this route we probably could not call init_logger_chain
on a rotate, the way it is now a rotate implies a reload. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
08-30-07 02:47  jamesgolovich  Note Added: 0069686                          
======================================================================