[prev in list] [next in list] [prev in thread] [next in thread] 

List:       syslog-ng
Subject:    [syslog-ng] [Bug 6] New: syslog-ng dies after cron.daily
From:       bugzilla () www ! balabit ! com
Date:       2007-12-25 14:17:24
Message-ID: bug-6-3 () https ! bugzilla ! balabit ! com/
[Download RAW message or body]

https://bugzilla.balabit.com/show_bug.cgi?id=6

           Summary: syslog-ng dies after cron.daily
           Product: syslog-ng
           Version: 2.0.x
          Platform: PC
               URL: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=427791
        OS/Version: Linux
            Status: NEW
          Severity: critical
          Priority: unspecified
         Component: syslog-ng
        AssignedTo: bazsi@balabit.hu
        ReportedBy: sasa@debian.org
Type of the Report: bug
   Estimated Hours: 0.0


From bugs.debian.org:

Syslog-ng is dying repeatedly after logrotate runs.
I believe that in most cases it continues to log to the original file, 
despite it having been rotated, though I am not 100% sure of this.
Where it does continue running, it dies when the 2nd rotate occurs, 
where the logfile is gzipped.

When trying to reproduce it manually, sending kill -HUP causes syslog-ng 
to die shortly after it gets a new PID.
I am able to consistently reproduce this.
No data is written to the new logfile until I manually restart syslog-ng

For now, as a workaround, I have altered the post-rotate command to 
restart syslog-ng rather than reload.


-- 
Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
_______________________________________________
syslog-ng maillist  -  syslog-ng@lists.balabit.hu
https://lists.balabit.hu/mailman/listinfo/syslog-ng
Frequently asked questions at http://www.campin.net/syslog-ng/faq.html

[prev in list] [next in list] [prev in thread] [next in thread]