From: Chris Gregors (Chris.Gregors@TELUS.COM)
Date: Thu Mar 13 2003 - 15:05:31 EST
I've seen syslogd stop writing the log files, if the filesystem that the
logfile is on hits 100% utilization (0 blocks free). We write our log
files to the /var filesystem and if someone blows up /var/tmp, it causes
syslogd to stop writing. The only solution is to restart syslogd.
I would also alarm the filesystems that syslogd writes to and make sure
the S.A.'s managing the system have restarting syslogd when the
filesystem has hit 100% utilization.
Chris Gregors
Telus Enterprise Solutions
-----Original Message-----
From: Jim Lane [mailto:JLane@torontohydro.com]
Sent: Thursday, March 13, 2003 10:09 AM
To: aix-l@Princeton.EDU
Subject: Re: syslogd daemon stops writing output.
my other Networker server has an identical /etc/syslog.conf and syslogd
works just fine. I can't see anything relevant in the errpt output. the
one difference I can think of between the 2 servers is that on the
failing one I recently migrated the filesystem where the syslog output
goes onto disks in an EMC Symmetrix array. the working system still has
the file on local SCSI disks. I can't see why this should make a
difference but then again it's hard to underestimate the reliability of
EMC.
Jim Lane
Sr. Technical Consultant
Network Services
Toronto Hydro
office: (416)-542-2820
cell: (416)-896-8576
>>> pobrien@DOIT.NV.GOV 12-Mar-03 11:52:02 AM >>>
Is your /etc/syslog.conf the same as on a system where syslog works all
of the time?
How about doing an 'errpt -a', looking for a hit when syslog stops
writing.
-----Original Message-----
From: Jim Lane [mailto:JLane@TORONTOHYDRO.COM]
Sent: Wednesday, March 12, 2003 5:22 AM
To: aix-l@Princeton.EDU
Subject: syslogd daemon stops writing output.
Hi, All
has anybody ever run into anything like this? I have one server on
which, for the past couple of months, the syslogd daemon just stops
writing output. the process still shows as being active via "lssrc -s
syslogd". I've verified it with /usr/bin/logger to try and force output
but still nothing. if I stop and start the daemon it resumes writing
output as expected. the server in question is AIX 4.3.3-10. it runs
Legato Networker (unfortunately) so the syslog output is kind of
important. I can't see what's different between this machine and several
others that don't have the problem. I'd appreciate any suggestion
anybody might have either as to a possible cause or a direction to
diagnose this. TIA
Jim Lane
Sr. Technical Consultant
Network Services
Toronto Hydro
office: (416)-542-2820
cell: (416)-896-8576
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 22:16:39 EDT