Very strange syslogd behavior

From: Ross Vandegrift (ross@willow.seitz.com)
Date: Mon Jan 26 2004 - 22:00:18 CET

Hello everyone,

        I've started seeing some very weird syslogd behavior recently.
We use a central syslog server to host the log messages for all of our
machines. There are probably a dozen or so Debian 3.0 servers logging
to the loghost (which is also running Debian), and maybe half a dozen
printers.

        We recently installed a new VPN server. Everything was fine
with logging, until messages suddenly stopped showing up in the logs.
No configurations were changed, no firewalls installed, nothing. The
last message from the VPN server is dated Jan 25, 23:40:02 and is a
routine cron message. Both servers are working well and I've tried
restarting syslogd.

        Then, this afternoon, messages stopped showing up from sendmail
on our primary outgoing mail relay. Only sendmail messages are missing
- ospfd, snmpd, crond, are all logging away happily. Again, no
configurations were changed, all daemons restarted.

Any ideas? 

-- 
Ross Vandegrift
ross@willow.seitz.com
A Pope has a Water Cannon.                               It is a Water Cannon.
He fires Holy-Water from it.                        It is a Holy-Water Cannon.
He Blesses it.                                 It is a Holy Holy-Water Cannon.
He Blesses the Hell out of it.          It is a Wholly Holy Holy-Water Cannon.
He has it pierced.                It is a Holey Wholly Holy Holy-Water Cannon.
He makes it official.       It is a Canon Holey Wholly Holy Holy-Water Cannon.
Batman and Robin arrive.                                       He shoots them.

This archive was generated by hypermail 2.1.7 : Mon Jan 26 2004 - 22:25:25 CET