Date: Thu, 12 Nov 1998 12:18:21 +1030 From: Greg Lehey <grog@lemis.com> To: Alexander Litvin <archer@lucky.net> Cc: current@FreeBSD.ORG Subject: Re: The infamous dying daemons bug Message-ID: <19981112121821.G463@freebie.lemis.com> In-Reply-To: <19981111112620.20264@carrier.kiev.ua>; from Alexander Litvin on Wed, Nov 11, 1998 at 11:26:20AM %2B0200 References: <199811101456.QAA28210@grape.carrier.kiev.ua> <199811110038.CAA01861@grape.carrier.kiev.ua> <19981111133212.B20374@freebie.lemis.com> <19981111112620.20264@carrier.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday, 11 November 1998 at 11:26:20 +0200, Alexander Litvin wrote:
> On Wed, Nov 11, 1998 at 01:32:12PM +1030, Greg Lehey wrote:
>
>>> Brought up old kernel without kludge.
>>>
>>> It appears that memory corruption leading to 'daemons dying' may take
>>> different forms. E.g., once it appears that sendmail continues to
>>> fork for queue runs successfully, but when I do 'telnet localhost 25',
>>> it just accepts connection, forks, changes proctitle ('startup with ...'),
>>> and goes into some strange state -- no EHLO, just accepts all I type
>>> in telnet and that's all. In that state kill -1 restarts sendmail ok.
>>> Other time I exhaust memory, sendmail segfaults every child forked
>>> for queue run, again restarts ok on SIGHUP. Once I even got in responce
>>> to 'telnet localhost 25':
>>>
>>> Trying 127.0.0.1...
>>> Connected to localhost.carrier.kiev.ua.
>>> Escape character is '^]'.
>>> archer... Recipient names must be specified
>>>
>>> As if I started sendmail without arguments on command prompt!
>>>
>>> I think it is ehough evidence that 'daemons dying' is caused by
>>> memory corruption.
>>
>> Well, no, I had an alternative explanation: for me, this problem
>> started with sendmail 8.9. I think I even went back and tried
>> sendmail 8.8.<mumble> and it didn't cause any problems. It could be a
>> bug in sendmail, possibly related to the config I'm using (it often
>> refuses connections because it thinks some test on the domain name
>> succeeds, when in fact it should have failed).
>
> Oh, come on!
Where?
> Just installed 8.8.8 -- same stuff, dies on queue runs and when
> accepting connection. And AFAIR the whole story had started before
> 8.9 was released and merged to CURRENT.
Well, this could mean that I'm wrong. Or it could mean that we have
two different SIGSEGV problems with sendmail, one which possibly
doesn't relate to the "dying daemons" problem. As I said above, I
suspect my config file.
> Why people still try to pretend that this definitely kernel-related
> problem may be explained by user-level bugs? Yes, inetd is buggy
> (it was for ages), sendmail is buggy, etc. But on 2.x.x it seems
> nobody ever saw anything similar.
Why are you trying to insist that this is all just one bug? Yes, I'm
sure we have a kernel bug somewhere. I'm not sure that my dying
sendmail is caused by this bug.
> And why Dima's kludge make it go away all at once?
It hasn't made my dying sendmail go away, because I didn't install it.
BTW, we've had a massive phone cable failure here (4½ of 5 lines), and
I'm off the Net for a few days until they repair it.
Greg
--
See complete headers for address, home page and phone numbers
finger grog@lemis.com for PGP public key
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19981112121821.G463>