From andrew@beebite.ugh.net.au  Fri May  8 03:51:00 1998
Received: from int-mail.fl.net.au (root@int-mail.syd.fl.net.au [202.181.0.28])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA00234
          for <FreeBSD-gnats-submit@freebsd.org>; Fri, 8 May 1998 03:50:58 -0700 (PDT)
          (envelope-from andrew@beebite.ugh.net.au)
Received: from beebite.ugh.net.au (root@a5-p43.syd.fl.net.au [202.181.2.43]) by int-mail.fl.net.au (2.0/fl) with ESMTP id UAA19026 for <FreeBSD-gnats-submit@freebsd.org>; Fri, 8 May 1998 20:50:54 +1000 (EST)
Received: (from andrew@localhost)
	by beebite.ugh.net.au (8.8.8/8.8.8) id TAA04330;
	Fri, 8 May 1998 19:11:01 +1000 (EST)
	(envelope-from andrew)
Message-Id: <199805080911.TAA04330@beebite.ugh.net.au>
Date: Fri, 8 May 1998 19:11:01 +1000 (EST)
From: andrew@ugh.net.au
Reply-To: andrew@ugh.net.au
To: FreeBSD-gnats-submit@freebsd.org
Subject: syslog stops working
X-Send-Pr-Version: 3.2

>Number:         6552
>Category:       bin
>Synopsis:       syslog stops working
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri May  8 03:50:02 PDT 1998
>Closed-Date:    Mon Nov 9 17:20:54 PST 1998
>Last-Modified:  Mon Nov  9 17:21:15 PST 1998
>Originator:     Andrew
>Release:        FreeBSD 2.2.6-STABLE i386
>Organization:
UgH!
>Environment:

stable as of yesterday (7/5)

>Description:

syslog slows right down. This is probably related to a pr I sent in earlier.
ATM there is abouta 15 min delay between me logging something and it appearing.

Perl scripts block for quite a while while logging (using Sys::Syslog).

netstat -a contains the line:

udp     2570      0  *.syslog               *.*

from ps:

USER       PID %CPU %MEM   VSZ  RSS  TT  STAT STARTED       TIME COMMAND
root        79  0.0  1.3   204  384  ??  Ss   11:52AM    0:01.06 syslogd

I have given this pr such a high priority as I beleive it is related to one I
posted earlier (but am off line atm so I don't know the pr) where syslog halted 
the entire box. If someone can find the earlier one feel free to connect the two.

>How-To-Repeat:

	

>Fix:
	
	

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: phk 
State-Changed-When: Fri May 8 13:06:51 PDT 1998 
State-Changed-Why:  
Do you have any complaints about mbufs in your dmesg/syslog output ? 

From: Poul-Henning Kamp <phk@critter.freebsd.dk>
To: freebsd-gnats-submit@freebsd.org
Cc:  Subject: Re: bin/6552 
Date: Wed, 20 May 1998 08:30:20 +0200

 In message <Pine.BSF.3.96.980509160207.1048d-100000@beebite.ugh.net.au>, andrew
 @ugh.net.au writes:
 >
 >
 >On Fri, 8 May 1998, Poul-Henning Kamp wrote:
 >
 >> Do you have any complaints about mbufs in your dmesg/syslog output ?
 >
 >Nope.
 >
 >Andrew
 >
 >
 
 --
 Poul-Henning Kamp             FreeBSD coreteam member
 phk@FreeBSD.ORG               "Real hackers run -current on their laptop."
 "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal

From: Guido van Rooij <guido@gvr.org>
To: freebsd-gnats-submit@freebsd.org, andrew@ugh.net.au
Cc:  Subject: Re: bin/6552: syslog stops working
Date: Thu, 25 Jun 1998 21:06:56 +0200 (MET DST)

 When this happens again, could you please ktrace syslogd and send the output
 to me? (You need options KTRACE in your kernel).
 
 -Guido

From: liz <liz@hmm.com>
To: freebsd-gnats-submit@freebsd.org
Cc:  Subject: Re: bin/6552: syslog stops working
Date: Mon, 09 Nov 1998 14:35:45 +1000

 Its probably safe to close this PR now. After putting KTRACE in the
 kernel the problem didn't reappear and the box has now been upgraded to
 fix a few security problems. I have no idea what caused it but unless
 someone else is still experiencing it I'd say the problem has been
 fixed...
 
 Thanks,
 
 Andrew
 
State-Changed-From-To: feedback->closed 
State-Changed-By: steve 
State-Changed-When: Mon Nov 9 17:20:54 PST 1998 
State-Changed-Why:  
Closed at originator's request. 
>Unformatted:
