From owner-freebsd-bugs Mon Apr 24 9: 0: 5 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id A307337B505 for ; Mon, 24 Apr 2000 09:00:03 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id JAA58035; Mon, 24 Apr 2000 09:00:03 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Mon, 24 Apr 2000 09:00:03 -0700 (PDT) Message-Id: <200004241600.JAA58035@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Rainer Duffner Subject: Re: bin/10553: syslogd suddenly stopped logging Reply-To: Rainer Duffner Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/10553; it has been noted by GNATS. From: Rainer Duffner To: freebsd-gnats-submit@FreeBSD.org, token@mayn.de Cc: Subject: Re: bin/10553: syslogd suddenly stopped logging Date: Mon, 24 Apr 2000 17:54:50 +0200 Hi, I have this on a a 3.4-stable machine, too. It logs, and suddenly stopps logging after some time. truss -o out-log logger Hallo tells me, at the end: syscall sendto(0x1,0xbfbfcf78,0x1f,0x0,0x0,0x0) errno 55 'No buffer space available' syscall close(1) returns 0 (0x0) syscall socket(0x1,0x2,0x0) returns 1 (0x1) syscall fcntl(0x1,0x2,0x1) returns 0 (0x0) syscall connect(0x1,0xbfbfcab4,0x6a) returns 0 (0x0) syscall sendto(0x1,0xbfbfcf78,0x1f,0x0,0x0,0x0) errno 55 'No buffer space available' syscall sigprocmask(0x1,0xfffef8cf) When I kill it and restart it, it works again, for some days. The machine is accepting logs from remote machines (if it is logging at all, that is). cheers, Rainer -- ======================================== Rainer Duffner , Konstanz, Germany eMail: duffner@fh-konstanz.de rainer.duffner@surf24.de www: http://www-stud.fh-konstanz.de M.I.C.R.O.S.O.F.T. Most Intelligent Customers Realize: Our Software Only Fools Teenagers ======================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message