From owner-freebsd-questions Mon Apr 8 20:52:50 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mba1.mba-consulting.com (mba1.mba-consulting.com [207.154.57.74]) by hub.freebsd.org (Postfix) with ESMTP id 840B537B423 for ; Mon, 8 Apr 2002 20:52:30 -0700 (PDT) Received: (from hjagnew@localhost) by mba1.mba-consulting.com (8.11.6/8.11.1) id g393mFc89892 for questions@freebsd.org; Mon, 8 Apr 2002 23:48:15 -0400 (EDT) (envelope-from hjagnew) Date: Mon, 8 Apr 2002 23:48:15 -0400 (EDT) From: "H. Jared Agnew" Message-Id: <200204090348.g393mFc89892@mba1.mba-consulting.com> To: questions@freebsd.org Subject: syslogd stopped logging Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG My syslogd stopped logging Sunday morning. It is Monday afternoon as of this writing. sighup to syslogd did not correct the situation. I've read a few posts on freebsd-bugs, and news groups that seem to point to this being an issue. Once I killed syslogd and started it again logging resumed just as it should. I do know that my hosts (three of them) were sending syslog messages to the box in question during the time that syslogd stopped logging. This is only the first occurence and I'm wondering if someone might tell me how to run syslogd in a way that might be helpful for any developer. I will run syslogd in debug mode, however there seemed to be traces from the other people reporting this problem, I don't know how to do this. I'm running 4.4-RELEASE, please let me know if anyone needs more info. Jared To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message