For the mailing list archives, it turns out there was a routing problem preventing our name servers from reaching our ISP's authoritative name servers. This stopped us from getting reverse DNS for our internet address space which caused our syslog server (which was functioning as a syslog collector) to block. Mon would then wait on the block.
Thanks for all the help guys. Without it, it would have been a long time before I found the problem. Out. -----Original Message----- From: Eric Sorenson [mailto:[EMAIL PROTECTED] Sent: Monday, January 12, 2004 12:45 PM To: Gary Richardson Cc: [EMAIL PROTECTED] Subject: RE: Mon Server Goes Foobar, help! On Mon, 12 Jan 2004, Gary Richardson wrote: > I'm doing some more research into this. A ran -d:Profile for perl and found > that 96% of the time is spent in Sys::Syslog::_syslog_send_socket. Is this > normal? Maybe the output logfile is set to fsync-on-write. This is the (unfortunate) default for some syslogs. Try prepending the filename with a '-' to turn it off, like: local1.* -/var/log/mon.log NB not all syslogs support this, check your local man pages for details. -- Eric Sorenson - Systems / Network Administrator, MIS - Transmeta Corporation _______________________________________________ mon mailing list [EMAIL PROTECTED] http://linux.kernel.org/mailman/listinfo/mon
