From owner-freebsd-questions Wed Jan 22 12:44:54 2003 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 078F037B4A0 for ; Wed, 22 Jan 2003 12:44:52 -0800 (PST) Received: from bast.unixathome.org (bast.unixathome.org [66.11.174.150]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5F72443E4A for ; Wed, 22 Jan 2003 12:44:51 -0800 (PST) (envelope-from dan@langille.org) Received: from wocker (wocker.unixathome.org [192.168.0.99]) by bast.unixathome.org (Postfix) with ESMTP id AF9073D27 for ; Wed, 22 Jan 2003 15:44:44 -0500 (EST) From: "Dan Langille" To: freebsd-questions@freebsd.org Date: Wed, 22 Jan 2003 15:44:44 -0500 MIME-Version: 1.0 Subject: syslogd stops logging Message-ID: <3E2EBC6C.8564.5427A283@localhost> X-mailer: Pegasus Mail for Windows (v4.02a) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body 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 I have observed this behaviour today and yesterday. For some reason, syslogd stops logging. Here's what I'm seeing: [dan@undef:~/tmp] $ tail /var/log/messages Jan 22 00:00:00 undef newsyslog[50185]: logfile turned over [dan@undef:~/tmp] $ logger hi [dan@undef:~/tmp] $ tail /var/log/messages Jan 22 00:00:00 undef newsyslog[50185]: logfile turned over [dan@undef:~/tmp] $ ps auwx | grep syslogd root 4837 0.0 0.0 940 0 ?? IWs - 0:00.00 /usr/sbin/syslogd -s Yesteryday, killing and restarting syslogd solved the issue. But I'd rather investigate this before I do that today. Ideas? thanks -- Dan Langille : http://www.langille.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message