Syslogd dying often on different hardware - hackers?
Sten Daniel Sørsdal
sten.daniel.sorsdal at wan.no
Fri Aug 29 05:38:34 PDT 2003
Many of my servers tend to have their syslogd die on them.
In dmesg i could see the signal number on one of them; 11
But kill -l doesnt reveal which that is:
pid 17263 (syslogd), uid 0: exited on signal 11
pid 87264 (syslogd), uid 0: exited on signal 11
/var/log has lots of space, newsyslog does it's job regularly.
The versions vary from 4.7 to 4.9-prerelease. Lots of memory available.
Hardware ranges from 1ghz celerons, 400mhz p3's, 1.6ghz p4's.
The command lines are either; -nccvvs -ccvvs (but mostly) -vvs
They log to remote host that is currently unavailable.
(router emites destination host unreachable).
The reason i mention this is that many types of software misbehave
when they receive this message.
When i ran syslogd -dvvs in 'screen' it started logging to remote 'loghost'.
For a -long- time it kept repeating "Host is down" and tried to log to 'loghost'
'loghost' is a local alias.
I'm finding it hard to reproduce.
More information about the freebsd-questions