Brian Groose wrote: > 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.
Hi Rainer, could you take a look at that. Shouldn't a simple reload keep /dev/log available? Or is rsyslog doing a full restart on "reload" due to listening on tcp port 514? Cheers, Michael -- 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
