From token@spacebus.mayn.de Thu Mar 11 21:44:48 1999
Return-Path: <token@spacebus.mayn.de>
Received: from spacebus.mayn.de (spacebus.mayn.de [194.95.209.18])
	by hub.freebsd.org (Postfix) with ESMTP id 93B1C14F8C
	for <FreeBSD-gnats-submit@freebsd.org>; Thu, 11 Mar 1999 21:44:31 -0800 (PST)
	(envelope-from token@spacebus.mayn.de)
Received: (from root@localhost)
	by spacebus.mayn.de (8.9.2/8.8.8) id GAA12496;
	Fri, 12 Mar 1999 06:44:13 +0100 (CET)
	(envelope-from token)
Message-Id: <199903120544.GAA12496@spacebus.mayn.de>
Date: Fri, 12 Mar 1999 06:44:13 +0100 (CET)
From: token@mayn.de
Sender: token@spacebus.mayn.de
Reply-To: token@mayn.de
To: FreeBSD-gnats-submit@freebsd.org
Subject: syslogd suddenly stopped logging
X-Send-Pr-Version: 3.2

>Number:         10553
>Category:       bin
>Synopsis:       syslogd suddenly stopped logging
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Mar 11 21:50:01 PST 1999
>Closed-Date:    Fri Jul 20 08:24:15 PDT 2001
>Last-Modified:  Fri Jul 20 08:28:25 PDT 2001
>Originator:     m. k. buelow
>Release:        FreeBSD 3.1-RELEASE i386
>Organization:
GeFoekoM e.V.
>Environment:

The machine is used for central logging and receives syslog
connections from several other machines (including high traffic
web servers which log a lot; however disk space and cpu time are
lots available).  The machine is also hosting nfs and running
named.  It was upgraded from 2.2.7 about 3 weeks ago.

>Description:

I do not know why but syslogd had stopped logging to any files
after about 10 days of system uptime.
logger(1) messages did not show up anymore in the logs, neither
did anything else.  Syslogd was still running and tracing it
and then sending it something with logger(1) showed the following:

    99 syslogd  PSIG  SIGALRM caught handler=0x804afc0 mask=0x1 code=0x0
    99 syslogd  RET   poll -1 errno 4 Interrupted system call
    99 syslogd  CALL  gettimeofday(0xefbfc854,0)
    99 syslogd  RET   gettimeofday 0
    99 syslogd  CALL  setitimer(0,0xefbfc84c,0xefbfc83c)
    99 syslogd  RET   setitimer 0
    99 syslogd  CALL  sigreturn(0xefbfc888)
    99 syslogd  RET   sigreturn JUSTRETURN

That is all.
kill -HUP didn't change anything, killing it and starting it again
made logging come back to normal operation.

>How-To-Repeat:

Dunno.

>Fix:
	
None known to me.


>Release-Note:
>Audit-Trail:

From: Dennis Boone <drb@msu.edu>
To: freebsd-gnats-submit@freebsd.org
Cc:  
Subject: Re: bin/10553: syslogd suddenly stopped logging
Date: Mon, 13 Dec 1999 09:48:40 -0500

 I have one machine running 3.2-RELEASE which does this same thing.
 It has happened on several occasions.  The machine in question
 only logs for itself.  I notice that "logfile turned over" messages
 continue to appear when syslog is in this state.
 
 Dennis Boone
 Metro Net Library Consortium
 

From: Rainer Duffner <duffner@fh-konstanz.de>
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
 ========================================
 
State-Changed-From-To: open->feedback 
State-Changed-By: mike 
State-Changed-When: Thu Jul 19 17:54:43 PDT 2001 
State-Changed-Why:  

Does this problem still occur in newer versions of FreeBSD, 
such as 4.3-RELEASE? 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=10553 
State-Changed-From-To: feedback->closed 
State-Changed-By: mike 
State-Changed-When: Fri Jul 20 08:24:15 PDT 2001 
State-Changed-Why:  

Originator confirmed, in a private e-mail to me, that this problem is 
no longer occurring on a newer version of FreeBSD.  The originator's 
environment has changed, but I'm almost certain that this bug has 
indeed been fixed. 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=10553 
>Unformatted:
