On Fri, 2005-05-13 at 13:04, Jeff Sheltren wrote: > Ever since updating on the morning of May 10th to the latest > development packages, my x86_64 machine has not been logging anything > to syslog. syslogd and klogd are both running, there is plenty of > free space in /var, and I have not touched syslog.conf for a month. > I first noticed this problem under kernel 1287 smp, but it persists > under 1290 smp. > > Is anyone else experiencing this? On two other FC4 boxes (both > i386), syslog is running fine. > > Another possibly related problem is that an 'ls -l' in /var/log was > showing lastlog as being 1.2 TB. df reported only ~700MB used in / > var (which seems more correct, especially since /var is only 4GB > large, making it impossible to have a 1.2TB file on it). I removed > the lastlog file and touched a new one. It is now showing up as 5.5 > MB... > > # uname -a > Linux hell 2.6.11-1.1290_FC4smp #1 SMP Mon May 9 19:28:09 EDT 2005 > x86_64 x86_64 x86_64 GNU/Linux > > Any ideas? > > -Jeff Please raise a sysklogd bugzilla on this - there have been no reports of this kind before. syslogd has nothing to do with /var/log/lastlog - that's a utmp/wtmp like login log . Please raise a bug against shadow-utils for the incorrect size - I'm getting incorrect sizes for this file on i386 too: $ ls -l lastlog -r-------- 1 root root 19136220 May 13 11:15 lastlog $ du -ks lastlog 33 lastlog Please gather an strace when you can reproduce the syslogd problem: # strace -p `pgrep syslogd` >/tmp/syslogd.strace.log 2>&1 # logger hello # pkill strace And append the /tmp/syslogd.strace.log to the bug report. Does the problem persist after clearing out /var/log/messages ? ie. back up /var/log/messages if you want to save it, and do: # echo '' > /var/log/messages # service syslog restart Thank You, Jason Vas Dias.