Your message dated Sun, 29 May 2011 23:50:35 +0200
with message-id <[email protected]>
and subject line /dev/log sometimes disappears upon "rsyslog reload"
has caused the Debian Bug report #550391,
regarding /dev/log sometimes disappears upon "rsyslog reload"
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.)
--
550391: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=550391
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: rsyslog
Version: 3.18.6-4
Severity: important
Sometimes we see /dev/log disappear for a while when "rsyslog reload" is
invoked, typically by logrotate.
I've narrowed down steps to reproduce this bug:
1. Start with a standard lenny install with default syslog settings
2. Modify /etc/rsyslog.conf and uncomment out the following lines to enable TCP
logging:
#$ModLoad imtcp
#$InputTCPServerRun 514
3. Restart or reload rsyslog so the TCP setting is in effect.
4. Put some logging load on rsyslog. This works nicely:
while [ 1 ] ; do logger "Test" ; done
5. Call "/etc/init.d/rsyslog reload" in a loop with a short sleep in between.
Watch
for /dev/log not appearing very shortly after the reload.
In my testing, I reloaded 1000 times with a 0.1s sleep in between, and 10 of the
reloads resulted in /dev/log going away. /dev/log came back after exactly one
minute in every one of those 10 times (I was no longer calling reload while
waiting for /dev/log to reappear), but during that one minute nothing can write
log messages because /dev/log is gone.
Rsyslog appeared to still be listening on port 514, though since this test does
not used TCP logging, I could not verify if logging to port 514 actually worked.
I did not have any issues if TCP logging was disabled or if there was nothing
being
actively logged.
-- System Information:
Debian Release: 5.0.3
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.26-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages rsyslog depends on:
ii libc6 2.7-18 GNU C Library: Shared libraries
ii lsb-base 3.2-20 Linux Standard Base 3.2 init scrip
ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime
Versions of packages rsyslog recommends:
ii logrotate 3.7.1-5 Log rotation utility
Versions of packages rsyslog suggests:
ii rsyslog-doc 3.18.6-4 documentation for rsyslog
pn rsyslog-mysql | rsyslog-pgsql <none> (no description available)
-- no debconf information
--- End Message ---
--- Begin Message ---
This should no longer be a problem as rsyslog no longer does a full restart on
HUP as it pre v4.
http://www.rsyslog.com/doc/v4compatibility.html
http://www.rsyslog.com/doc/v5compatibility.html
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
