#1085371 innduct: Excessive debug log when peer expiring for ages

Package:
innduct
Source:
innduct
Description:
nntp feeder transport for inn2
Submitter:
Ian Jackson
Date:
2024-10-18 16:45:03 UTC
Severity:
normal
Tags:
#1085371#5
Date:
2024-10-18 16:43:06 UTC
From:
To:
I have had trouble over the past few days with innduct generating
unreasonable amounts of debug log.  Mostly, the messages look like
this:

Oct 18 08:40:01 chiark innduct[3270]: nntp.[elided]| debug: filemon inotify: read event with unknown wd=5447913
Oct 18 08:40:01 chiark innduct[3270]: nntp.[elided]| debug: filemon inotify: startfile 0x55de6bf4e6b0 wd=5447914 pf=0x55de6c096840
Oct 18 08:40:01 chiark innduct[3270]: nntp.[elided]| debug: filemon inotify: stopfile 0x55de6bf4e6b0 wd=5447914 pf=0x55de6c096840
Oct 18 08:40:01 chiark innduct[3270]: nntp.[elided]| debug: filemon inotify: read event with unknown wd=5447914
Oct 18 08:40:01 chiark innduct[3270]: nntp.[elided]| debug: filemon inotify: startfile 0x55de6bf4e6b0 wd=5447915 pf=0x55de6bfbfd10
Oct 18 08:40:01 chiark innduct[3270]: nntp.[elided]| debug: filemon inotify: stopfile 0x55de6bf4e6b0 wd=5447915 pf=0x55de6bfbfd10
Oct 18 08:40:01 chiark innduct[3270]: nntp.[elided]| debug: filemon inotify: startfile 0x55de6bf4e6b0 wd=5447916 pf=0x55de6bff38d0

This seems to have been triggered by the peer being in "expiring"
state for several days and responding to every article with 431.

I think I have diagnosed the problem.  If my fix holds up, I will
upload it.