> /Glenn, you may want to try using strace(1) on the syslogd process./
Agree. See where it's hung.
strace -p $PID_OF_STRACED
Also, I'd check the I/O of wherever it's saving logs to. If it's
saving to a local disk, it may be getting ready to die. If it's saving
to NFS or a remote log server, the LAN may be having issues (bad switch,
cable, firewall, etc.)
--Derek
On 10/14/2010 11:42 AM, Mark Foster wrote:
On 10/14/2010 11:25 AM, Jesse Keating wrote:
On 10/14/2010 11:06 AM, Glenn Stone wrote:
You guys ever seen RHEL4's syslogd just hang inexplicably? RHEL4.8, mysql
server, the only oddball thing is we've got a third-party app using syslog's
standard "local6" facility to log to a file on an OCFS filesystem. A
bog-standard "service syslogd restart" restores functionality quickly and
without complaint or trace in the logs, just "restart successful"...
Clues? Google-fu was less than useful...
-- Glenn
No clue, other than to disable the third-party app for a period of time
sufficient to place blame upon it if the freezing does not re-occur.
Not really helpful, I know.
Glenn, you may want to try using strace(1) on the syslogd process.
That often yields some valuable clue.
