Date: Sun, 26 Mar 2000 15:25:20 -0500 (EST) From: Thomas Stromberg <tstromberg@rtci.com> To: Sue Blake <sue@welearn.com.au> Cc: freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: syslogd stops logging - caught in the act Message-ID: <Pine.GSO.4.20.0003261520130.13429-100000@barracuda.aquarium.rtci.com> In-Reply-To: <20000326140241.C43926@welearn.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Me and my roommate saw a similar thing occuring when developing a Windows NT EventLog -> syslogd forwarder (http://www.schizo.com/software/sislog/) on an older 4.0-CURRENT machine and a 2.2.8-RELEASE machine.. We concluded that it appears to be if the host sending the syslog messages is unresolvable (in our case, the DNS server could not be contacted), it would stop logging for us. I'm not sure about any other situations. This drove me nuts for quite a while, but since we have no home connectivity I forgot about submitting a GNATS report later. Perhaps a good thing to check... ------------------------------------------------------------------------- > Thomas R. Stromberg Senior Systems Administrator : > smtp[tstromberg@rtci.com] Research Triangle Commerce, Inc. : > http[afterthought.org] pots[1.919.657.1317] : > irc[helixblue] FreeBSD Contributor, Perl Hacker : ------------------------------------------------------------------------- On Sun, 26 Mar 2000, Sue Blake wrote: > Let's solve this once and for all. > > I've run syslogd -d and sent output to a file and waited for the > inevitable cessation of logging although syslogd is still running. > (Refer PRs 2191 5548 6216 8847 8865 10553 and two or three threads > in -isp and/or -questions earlier this year that summarised the > problems and their scope but didn't reach the list archives) > > Now logging's stopped and I need to get it restarted again soon, but I'd > like to collect some useful information first. I need help to do that. > > This has been reported for almost all -release and -stable versions since > early 2.2, and it's been hard to pin down what circumstances cause it > or to repeat it on unaffected machines. > > The common facts are that syslogd is running, using CPU, but nothing > goes to the logs, not mark messages, logger messages, nothing. One > exception: the logs dutifully rotate and log that they have rotated. > Sending a sighup does not fix it, only completely killing and > restarting syslogd gets it going. Unless this is done, it will continue > with the same behaviour (running but not logging) until reboot. > All past speculation as to the cause has been met with counterexamples. > > There are five freebsd machines that exhibit this problem which I only > have access to for another couple of days, so if anyone is interested > in solving this long-standing failure of syslogd please take this > opportunity to work with me on it. > > These machines range from almost idle very vanilla 3.3R workstations > with only sendmail running, up to 3.4-STABLE of january running many > daemons and with reasonable load, for which reliable logging is > critical. > > Replies to my email address would be appreciated. > > -- > > Regards, > -*Sue*- > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.20.0003261520130.13429-100000>