[BusyBox] bug#1235: marked as done (busybox (0.61pre) syslogd sometimes dies writing to remote logger)

BusyBox.net bug Tracking System owner at busybox.net
Sat Apr 13 08:16:04 UTC 2002


Your message dated Sat, 13 Apr 2002 08:12:22 -0600
with message-id <20020413141221.GI3091 at codepoet.org>
and subject line [BusyBox] bug#1235: Acknowledgement (busybox (0.61pre) syslogd sometimes dies writing to remote logger)
has caused the attached bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Erik Andersen
(administrator, BusyBox.net bugs database)

--------------------------------------
Received: (at submit) by bugs.busybox.net; 2 Apr 2002 01:53:09 +0000
>From ken_yap at users.sourceforge.net  Mon Apr  1 18:53:09 2002
Received: from mta03bw.bigpond.com (mta03bw.bigpond.com [139.134.6.86])
	by winder.codepoet.org (Postfix) with ESMTP id 144581575E6
	for <submit at bugs.busybox.net>; Mon,  1 Apr 2002 18:53:07 -0700 (MST)
Received: from ken.ken.com.au ([144.135.24.81]) by
          mta03bw.bigpond.com (Netscape Messaging Server 4.15) with SMTP
          id GTX3WD00.66H for <submit at bugs.busybox.net>; Tue, 2 Apr 2002
          11:53:01 +1000 
Received: from CPE-144-136-68-6.nsw.bigpond.net.au ([144.136.68.6]) by bwmam05.mailsvc.email.bigpond.com(MailRouter V3.0i 38/96316); 02 Apr 2002 11:53:00
Received: by ken.ken.com.au (Postfix on SuSE Linux 7.2 (i386), from userid 500)
	id 780567719; Tue,  2 Apr 2002 11:52:54 +1000
Received: from ken.com.au (localhost [127.0.0.1])
	by ken.ken.com.au (Postfix on SuSE Linux 7.2 (i386)) with ESMTP id 2ADC67718
	for <submit at bugs.busybox.net>; Tue,  2 Apr 2002 11:52:54 +1000
To: submit at bugs.busybox.net
Subject: busybox (0.61pre) syslogd sometimes dies writing to remote logger
From: ken_yap at users.sourceforge.net
Content-type: text/plain; charset="iso-8859-1"
X-Message-Flag: Linux : The choice of a GNU generation
X-Face: bak'McMAD{%JrA$mQ(j_Ex_o?a/F8/Nt<W\sbPkh?,)PF7TK1{Lh"HJLuQfhE}(Dj!g:c(U
 =wh/r[<MJUF}hXzR*URO0e/Lh'mn_YUpU+;ycf6:0>ng*t2KX(NcfGalVs^Ke^C61:F
Date: Tue, 02 Apr 2002 11:52:48 +1000
Message-Id: <20020402015254.780567719 at ken.ken.com.au>

Package: busybox
Version: 0.61pre
Severity: normal

Syslogd sometimes dies when trying to write a message to a remote
logger, after having run for a day or so. The remote logger IS running,
and when syslogd is restarted, everything works again.

syslogd: syslogd: cannot write to remote file handle on 192.168.26.1:514

No idea why. Perhaps syslogd should not exit with an error but try to
reopen the network socket?
---------------------------------------
Received: (at 1235-done) by bugs.busybox.net; 13 Apr 2002 14:12:23 +0000
>From andersen at codepoet.org  Sat Apr 13 08:12:23 2002
Received: by winder.codepoet.org (Postfix, from userid 1000)
	id 8331E157CFD; Sat, 13 Apr 2002 08:12:22 -0600 (MDT)
Date: Sat, 13 Apr 2002 08:12:22 -0600
From: Erik Andersen <andersen at codepoet.org>
To: ken_yap at users.sourceforge.net, 1235-done at bugs.busybox.net
Subject: Re: [BusyBox] bug#1235: Acknowledgement (busybox (0.61pre) syslogd sometimes dies writing to remote logger)
Message-ID: <20020413141221.GI3091 at codepoet.org>
Reply-To: andersen at codepoet.org
References: <handler.1235.B.101771238925084.ack at bugs.busybox.net> <20020402032324.B744E7797 at ken.ken.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20020402032324.B744E7797 at ken.ken.com.au>
User-Agent: Mutt/1.3.28i
X-Operating-System: Linux 2.4.18-rmk1, Rebel-NetWinder(Intel StrongARM 110 rev 3), 185.95 BogoMips
X-No-Junk-Mail: I do not want to get *any* junk mail.

On Tue Apr 02, 2002 at 01:23:19PM +1000, ken_yap at users.sourceforge.net wrote:
> BTW, looking through the code, I noticed that the MARK message is
> written from inside a signal handler. I think, but can't be sure, the
> crash happened at the time a MARK was expected. I've restarted syslogd
> without MARK writing to see what happens.
> 
> Is the code kosher? I was taught way back in the early days of Unix that
> one should not do anything more in a signal handler than setting a flag.

Nah, that isn't the problem here.  We were being overly strict
with errno checking.  I just applied a patch from Larry Doolittle
that should fix this problem for real,

 -Erik

--
Erik B. Andersen             http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--



More information about the busybox mailing list