Hi Ian,
Version: 2.6.4-2
I've recently had a 2nd incident where inn2 got weirdly stuck and
caused the system to run out out of processes.
[...]
This strace does IMO show pathological behaviour. innd calls accept
and fork, but you will observe that it doesn't reap!
I don't know what causes the incidents you report.
Looking at what has been fixed since the 2.6.4 version, maybe you
reached the maximum number of file descriptors your system can handle?
I noted in the change log of INN 2.7.2 that "innd no longer malfunctions
nor throttles when the maximum number of file descriptors supported by
the system is reached. If needing to use more file descriptors than the
default system limit, a new LARGE_FD_SETSIZE option can be set at build
time. See the documentation for rlimitnofile in inn.conf for more
information."
You can find the mentioned documentation here:
https://www.eyrie.org/~eagle/software/inn/docs/inn.conf.html
It could be unrelated to your issue, though.
Just telling you in case it could hint at something.
--
Julien ÉLIE
« Quousque tandem ? » (Cicéron)
