ctlinnd reload all reason kills innd

Jeffrey M. Vinocur jeff at litech.org
Sat Mar 2 00:49:01 UTC 2002



On Fri, 1 Mar 2002, William F. Maton wrote:

> 	Executing ctlinnd reload all reason kills innd....whoops!

Ooh, not again.  I can't reproduce this -- can you try issuing the
different sorts of reload one by one (they're listed in the ctlinnd
manpage) and track down which one it is?

We were seeing something like this in the early days of the IPv6 patch,
and it turned out that some part of the original patch that Marco hadn't
finished was returning a static string, and reloading was causing us to
attempt to free() static data.  But we fixed that...


> Mar  1 13:44:12 mcast innd: SERVER can't close history
> /var/news/db/history: No such file or directory

This may actually be unrelated.  I was seeing two "can't close history"
errors for a while, that and one other...let me see if I'm still seeing
them.  Yeah, I get this when attempting to shutdown INN:

    Mar  1 19:31:02 marduk innd: SERVER can't close history
    /usr/local/news/db/history: Interrupted system call

But here's the weird thing.  As far as I can tell the only place that
generates that sort of message is history/hisv6/hisv6.c:hisv6_closefiles()
and as of late it has an "errno != EINTER" wrapped around it.  So I have
no idea how I'm getting this error.

I lost track of the thread where we were debugging this.

-- 
Jeffrey M. Vinocur
jeff at litech.org



More information about the inn-bugs mailing list