nnrpd given the same PID as innfeed

Richard Kettlewell rjk at greenend.org.uk
Fri Jun 19 17:26:35 UTC 2015


On 18/06/15 18:19, Julien ÉLIE wrote:
> I unfortunately have bad news about the fix of the issue.  I still see
> errors in my logs:

Oh dear.  In my defense it's hard to fix bugs without having managed to
reproduce them l-)

> Jun 18 06:33:55 news innd: nocem! exit 1 elapsed 57507 pid 22274
> Jun 18 06:33:55 news innd: inpaths! exit 1 elapsed 57507 pid 22272
> Jun 18 06:33:55 news innd: source-archive! exit 1 elapsed 57507 pid 22273
> Jun 18 06:47:02 news innd: innfeed! exit 1 elapsed 9120 pid 24910
> Jun 18 06:47:02 news innd: inpaths! exit 1 elapsed 9120 pid 24911
> Jun 18 09:23:07 news innd: innfeed! exit 1 elapsed 18485 pid 24910
> Jun 18 09:23:07 news innd: inpaths! exit 1 elapsed 18485 pid 24911
> Jun 18 12:06:49 news innd: innfeed! exit 1 elapsed 28306 pid 24910
> Jun 18 12:06:49 news innd: inpaths! exit 1 elapsed 28306 pid 24911
> Jun 18 14:42:35 news innd: inpaths! exit 1 elapsed 37653 pid 24911
> Jun 18 14:42:35 news innd: innfeed! exit 1 elapsed 37653 pid 24910
> Jun 18 17:21:00 news innd: inpaths! exit 1 elapsed 47157 pid 24911
> Jun 18 17:21:00 news innd: innfeed! exit 1 elapsed 47157 pid 24910

The repeated PIDs and consistently growing elasped time is the clue that
got me there.  Evidently it is revisiting the same PROCtable entries.

Patch attached.

ttfn/rjk
-------------- next part --------------
A non-text attachment was scrubbed...
Name: procreap.patch
Type: text/x-patch
Size: 582 bytes
Desc: not available
URL: <https://lists.isc.org/pipermail/inn-workers/attachments/20150619/94babf8f/attachment.bin>


More information about the inn-workers mailing list