Your message dated Wed, 23 Jul 2008 11:25:17 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Could not reproduce the bug
has caused the Debian Bug report #427791,
regarding syslog-ng dies after cron.daily
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
427791: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=427791
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: syslog-ng
Version: 2.0.0-1
Severity: grave
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.
Chris
--- End Message ---
--- Begin Message ---
Hi!
Upstream could not reproduce the bug Neither I am.
And no information.
smime.p7s
Description: S/MIME cryptographic signature
--- End Message ---
