From owner-freebsd-current Fri Jan 3 21:58:01 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id VAA01033 for current-outgoing; Fri, 3 Jan 1997 21:58:01 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id VAA01010 for ; Fri, 3 Jan 1997 21:57:57 -0800 (PST) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by who.cdrom.com (8.7.5/8.6.11) with ESMTP id VAA04666 for ; Fri, 3 Jan 1997 21:32:06 -0800 (PST) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.8.4/8.8.4) with ESMTP id GAA01507 for ; Sat, 4 Jan 1997 06:31:00 +0100 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.6.12/8.6.12) with UUCP id GAA30501 for current@freebsd.org; Sat, 4 Jan 1997 06:31:04 +0100 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.4/keltia-uucp-2.9) id BAA13843; Sat, 4 Jan 1997 01:53:33 +0100 (CET) Message-ID: Date: Sat, 4 Jan 1997 01:53:33 +0100 From: roberto@keltia.freenix.fr (Ollivier Robert) To: current@FreeBSD.ORG Subject: Re: syslogd failure References: <32CD9C38.41C67EA6@nconnect.net> X-Mailer: Mutt 0.55.15 Mime-Version: 1.0 X-Operating-System: FreeBSD 3.0-CURRENT ctm#2837 In-Reply-To: <32CD9C38.41C67EA6@nconnect.net>; from Randy DuCharme on Jan 3, 1997 17:54:32 -0600 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to Randy DuCharme: > Syslog -d says "cannot create /var/run/log: Address already in use > logmsg: pri 53, flags 4, from arabian, msg syslogd: cannot create > /var/run/log: Address already in use > Logging to CONSOLE /dev/console > cannot create /var/run/log (0) > > I'm confused. Permissions look right. Any help would be GREATLY > appreciated. Look with ps or lsof. You'll see that your syslogd is probably in the "Exiting" state, thus "locking" the "/var/run/log" socket. It is a "known without a fix" bug I think of syslogd. Try to "kill -9" and launch another. If it is still unable to run, reboot... I see this also an an 2.1.5 box where it suddenly stops logging. -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #33: Sat Dec 21 12:57:17 CET 1996