Problems with inn on Fedora Core 4

Russ Allbery rra at
Sun Jan 29 01:43:14 UTC 2006

Paul Tomblin <ptomblin at> writes:
> Quoting Russ Allbery (rra at

>> Huh.  That would imply that it's all done and is shutting down.  Does
>> that match what you see in the new history file?  Could it have
>> possibly finished?

> Well, there is the little problem that the new history file is empty.
> And that strace I send you shows it opening just a few of the 8250
> timecaf files.  I'm guessing it found some previous error, and then
> exited, and while it was exiting it tried to free something that had
> already been freed.

Well, the storage API does run SMshutdown as an atexit handler, but it
should have printed out some sort of error before that point if it exited
due to some sort of problem.  Even if it's segfaulting, the error
reporting happens before any of the atexit error handlers run.

>> Bleh.  That isn't too helpful either.  That conditional jump may be a
>> hint, or it may be noise.

> I'm more worried about the huge mallocs.  Why is it mallocing 2Gb of
> memory?

It could be that valgrind is just confusing it somehow, although maybe
that's a hidden error message under the segfault as well.  I'm really not

> Hmmm.  Is there a way to see what the config options are in an rpm?

If the src RPM is available, you can tell from the spec file in it.

Russ Allbery (rra at             <>

More information about the inn-bugs mailing list