nnrpd given the same PID as innfeed
Julien ÉLIE
julien at trigofacile.com
Mon Jun 15 19:26:37 UTC 2015
Hi all,
Has someone ever seen "exit 1" lines for innfeed in your news.notice files?
Jun 15 17:37:14 news innd: innfeed! exit 1 elapsed 48133 pid 4474
I have recently seen it a few times. The problem is that during a fork,
nnrpd is given the PID of innfeed if I trust the logs:
Jun 15 17:37:14 news nnrpd[4474]: cpe-67-242-187-207.rochester.res.rr.com (67.242.187.207) connect - port 119
Jun 15 17:37:14 news nnrpd[4474]: cpe-67-242-187-207.rochester.res.rr.com rejected by rule (Closed service.)
Jun 15 17:37:14 news nnrpd[4474]: cpe-67-242-187-207.rochester.res.rr.com times user 0.032 system 0.016 idle 0.000 elapsed 0.036
Jun 15 17:37:14 news nnrpd[4474]: cpe-67-242-187-207.rochester.res.rr.com time 36 nntpwrite 0(1)
Jun 15 17:37:14 news innd: innfeed! exit 1 elapsed 48133 pid 4474
I don't know why it happens. But the fact is it happens...
That issue always appears (at least on my system) when a user tries to connect very very often.
I blacklist such users in my readers.conf file, whence the "rejected by rule (Closed service.)".
% grep cpe-67-242-187-207.rochester.res.rr.com news.notice | grep connect | wc -l
14768
Now blacklisted directly in my iptables!
Maybe it is a bug in my old Debian Etch (2007) distrib...
If someone sees similar "exit 1" lines, please tell!
--
Julien ÉLIE
« N'as-tu jamais fait ces rêves, Neo, qui ont l'air plus vrais que la
réalité ? Si tu étais incapable de sortir de l'un de ces rêves,
comment ferais-tu la différence entre le monde du rêve et le monde
réel ? » (Morpheus, _Matrix_)
More information about the inn-workers
mailing list