nnrpd core

Russ Allbery rra at stanford.edu
Thu Oct 16 05:30:12 UTC 2003


Dmitry Davidov <D.Davidov at webplus.ru> writes:

>> Date: Tue, 23 Sep 2003 11:23:45 -0700
>> From: Russ Allbery <rra at stanford.edu>
>> To: inn-workers at isc.org
>> Subject: Re: nnrpd core

>> Dmitry Davidov <D.Davidov at webplus.ru> writes:

>>> Sometime one of ~300 nrrpd process increases in memory up to a segment
>>> limit and :

>>> Core was generated by `nnrpd'.
>>> Program terminated with signal 11, Segmentation fault.
>>> Reading symbols from /usr/local/lib/libdb41.so.1...done.
>>> Reading symbols from /usr/lib/libc.so.4...done.
>>> Reading symbols from /usr/libexec/ld-elf.so.1...done.
>>> #0  0x281c0208 in isatty () from /usr/lib/libc.so.4

>> Hm, are you sure that this is a memory limit problem and not something
>> else?

> I think it happens when nnrpd close self on timeout but ovdb_server
> already clear connection on this nnrpd, because nnrpd write to log
> (2000-~500000 lines)
> nnrpd[pid]: OVDB: cant write: broken pipe

I finally had a chance to take a closer look at this, and I'm not sure
that this is what's causing this problem, or at least I can't see how it
would be causing this.  In INN 2.4, nnrpd should exit after logging that
message, so I don't see how you could be getting tons of them in the logs
or how that could cause nnrpd to grow and segfault.  Although in INN 2.4,
that message is actually "OVDB: rc: cant write".  That error message does
not occur in INN 2.3; readserver support was added in INN 2.4.

I also don't understand how ovdb_server closing its connection could cause
this problem.  That would cause nnrpd to receive a broken pipe error when
it tries to write, which should cause it to log that message and then
immediately exit.  On a read, it should read an EOF and exit.

So I'm not sure that what you're describing explains the problem, and I
have no idea what would cause the problems that you're describing.  :/

-- 
Russ Allbery (rra at stanford.edu)             <http://www.eyrie.org/~eagle/>

    Please send questions to the list rather than mailing me directly.
     <http://www.eyrie.org/~eagle/faqs/questions.html> explains why.


More information about the inn-workers mailing list