From owner-freebsd-security Wed Feb 14 22:59:56 2001 Delivered-To: freebsd-security@freebsd.org Received: from mailhost01.reflexnet.net (mailhost01.reflexnet.net [64.6.192.82]) by hub.freebsd.org (Postfix) with ESMTP id 227DE37B4EC for ; Wed, 14 Feb 2001 22:59:54 -0800 (PST) Received: from rfx-216-196-73-168.users.reflexcom.com ([216.196.73.168]) by mailhost01.reflexnet.net with Microsoft SMTPSVC(5.5.1877.197.19); Wed, 14 Feb 2001 22:58:00 -0800 Received: (from cjc@localhost) by rfx-216-196-73-168.users.reflexcom.com (8.11.1/8.11.1) id f1F6xjO66353; Wed, 14 Feb 2001 22:59:45 -0800 (PST) (envelope-from cjc) Date: Wed, 14 Feb 2001 22:59:45 -0800 From: "Crist J. Clark" To: Mark Hartley Cc: freebsd-security@FreeBSD.ORG Subject: Re: Syslogd stops working Message-ID: <20010214225944.R62368@rfx-216-196-73-168.users.reflex> Reply-To: cjclark@alum.mit.edu References: <20010214154342.A48740@router.drapple.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010214154342.A48740@router.drapple.com>; from freebsd@drapple.com on Wed, Feb 14, 2001 at 03:43:43PM -0800 Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Feb 14, 2001 at 03:43:43PM -0800, Mark Hartley wrote: > I have several different FreeBSD servers which I've upgraded recently > through cvsup and rebuilding world due to the bind, ipfw, and ssh holes. > > However, I have one machine which I cvsupped and rebuilt on Jan 29th > which has stopped logging to syslog. I've checked my syslog.conf file > and everything seems fine. I had just been noticing a lack of people > "banging" on my firewall. I got to looking, and syslog has not been > functioning since that point. This is a very serious issue for me > as I've potentially missed several important syslog notices. I checked, > and syslogd is in fact running. > > Any ideas why this is happening and what I can do to remedy it? Run it in debug mode, -d, and if you can't figure it out from there, post the output to the list (this actually may be more of a -questions issue if it turns out to be a configuration problem). Preferably, use logger(1) to send some messages to get logged if none pop up on their own while it is running. -- Crist J. Clark cjclark@alum.mit.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message