From owner-freebsd-hackers Sat Mar 25 20: 3: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from phoenix.welearn.com.au (phoenix.welearn.com.au [139.130.44.81]) by hub.freebsd.org (Postfix) with ESMTP id 64E5F37B652; Sat, 25 Mar 2000 20:02:56 -0800 (PST) (envelope-from sue@phoenix.welearn.com.au) Received: (from sue@localhost) by phoenix.welearn.com.au (8.9.3/8.9.3) id OAA55956; Sun, 26 Mar 2000 14:02:46 +1000 (EST) (envelope-from sue) Date: Sun, 26 Mar 2000 14:02:43 +1000 From: Sue Blake To: freebsd-questions@freebsd.org Subject: syslogd stops logging - caught in the act Message-ID: <20000326140241.C43926@welearn.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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