Description of Problem:
After periods of heavy use, sysklogd-1.3.31-12 hangs, leaving processes
trying to write
log entries blocking, making logging in impossible. The culprit was
determined by leaving a shell open.
Not easily repeatable, but the machine in question was running processes
which were slamming the syslog quite hard. (Machine in question is a
Being a model of a live environment, the techs have decided not to upgrade
sysklogd to -17 from the RH6.2 updates site until they are certain it is a
bug in the version of sysklogd they are using at the moment. glibc
upgraded to glibc-2.1.3-21.
Are you using remote logging with a nameserver on the same machine?
It's receiving logs from a remote machine, but the machine does not run a
Remote nameservers are reachable from it, but none of the machines have
hostnames which resolve from the IP addresses. (We tend not to bother with
local DNS in this lab)
Just clearing out old bugs here. This one would definitely appear
to be fixed with syslogd-1.4.1-22.