[Leaplist] SYSLOG problem ....

[Andrew]

On May 13, 2008, at 8:29 AM, Mark W. Alexander wrote:

> On Mon, May 12, 2008 at 09:00:33AM -0500, William A. Mahaffey III  
> wrote:
>>
>> .... I am having a teensy little problem w/ syslogging on my  
>> Athlon64X2
>> box running FC8 64-bit (this box, as it happens). I looked at my
>> /var/log directory this A.M. & noticed that my messages files had  
>> gotten
>> logrotated out yesterday, but the new messages files was empty,  
>> which is
>> unusual for ~24 hours of operation. rsyslog *is* running
>> (rsyslog.x86_64, 2.0.2-3.fc8, yum-installed May 3) & the 5 previous
>> logrotated messages files are there.
>
> You mention rsyslog. I don't know what distro you're on but I  
> suspect rsyslog
> is not the default syslog. Check the logrotate configuration to see  
> what
> command it performs in the postrotate section. Odds are its wrong.  
> If that's
> the case, logrotate is moving the file out from under rsyslog and  
> not properly
> telling rsyslog to open a new one.
>

Fedora switched to using rsyslog recently, so it's probably not a  
syslog/rsyslog food fight, but possibly a rsyslog bug.  Try  
restarting rsyslog and test with the 'logger' command to see if that  
will get logging working again.