Bug#623302: leafnode: excessive logging of old articles causing overload
Arthur Marsh
Version: 1.11.8-1
Severity: normal
With default logging (debugmode = 0), I ended up with over 100 MiB
of log file containing lines like:
Apr 19 00:03:09 victoria fetchnews[3335]: gmane.linux.kernel: killed 79950 (<200
212181942.g...@devserv.devel.redhat.com>), too old (3043 > 15) days
I had subscribed to gmane.linux.kernel some time ago but leafnode decided
to attempt re-fetching the group on its own, sending this old machine
into overload.
How can leafnode be configured to accept such a group without such a huge
amount of logging of articles older than what I want?
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.38.2 (SMP w/1 CPU core)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages leafnode depends on:
ii debconf [debconf-2.0] 1.5.38 Debian configuration management sy
ii libc6 2.11.2-11 Embedded GNU C Library: Shared lib
ii libpcre3 8.12-3 Perl 5 Compatible Regular Expressi
ii logrotate 3.7.8-6 Log rotation utility
ii netbase 4.45 Basic TCP/IP networking system
ii openbsd-inetd [inet-superse 0.20080125-6 The OpenBSD Internet Superserver
ii tcpd 7.6.q-19 Wietse Venema's TCP wrapper utilit
leafnode recommends no packages.
Versions of packages leafnode suggests:
ii lynx-cur [news-reader] 2.8.8dev.8-1 Text-mode WWW Browser with NLS sup
ii perl 5.10.1-19 Larry Wall's Practical Extraction
-- Configuration Files:
/etc/cron.d/leafnode changed:
3,8,13,18,23,28,33,38,43,48,53,58 * * * * news if [ -x /etc/news/leafnode/do-fetch-news ]; then nice ionice -c3 /etc/news/leafnode/do-fetch-news; fi
/etc/logcheck/ignore.d.paranoid/leafnode [Errno 13] Permission denied: u'/etc/logcheck/ignore.d.paranoid/leafnode'
/etc/logcheck/ignore.d.server/leafnode [Errno 13] Permission denied: u'/etc/logcheck/ignore.d.server/leafnode'
/etc/logcheck/ignore.d.workstation/leafnode [Errno 13] Permission denied: u'/etc/logcheck/ignore.d.workstation/leafnode'
/etc/logcheck/violations.ignore.d/leafnode [Errno 13] Permission denied: u'/etc/logcheck/violations.ignore.d/leafnode'
/etc/news/leafnode/do-fetch-news changed:
. /etc/news/leafnode/debian-config
cd /
if [ "$NETWORK" = "permanent" -a -x /usr/sbin/fetchnews -a ! -z "`ps -e|grep icedove`" ]; then
trickle -s -d 8 /usr/sbin/fetchnews
fi
/etc/news/leafnode/filters changed:
^Newsgroups:.*[, ]gmane.spam.detected$
^Newsgroups:.*[, ]gmane.spam.detected,
-- debconf-show failed
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Robert Grimm
> With default logging (debugmode = 0), I ended up with over 100 MiB
> of log file containing lines like:
>
> Apr 19 00:03:09 victoria fetchnews[3335]: gmane.linux.kernel: killed 79950 (<200
> 212181942.g...@devserv.devel.redhat.com>), too old (3043 > 15) days
>
> I had subscribed to gmane.linux.kernel some time ago but leafnode decided
> to attempt re-fetching the group on its own, sending this old machine
> into overload.
I can't say what happened exactly from your description. Maybe it was a
hiccup on news.gmane.org or a problem with the active file for this
server.
> How can leafnode be configured to accept such a group without such a huge
> amount of logging of articles older than what I want?
Please be sure, that maxage is lower or equal to [group]expire,
or clamp_maxage is unset.
The logging of leafnode, resp. fetchnews is (with the exception of debug
logging) not adjustable. You may redirect news.info with your syslog
daemon.
Regards,
Robert Grimm
Arthur Marsh
Robert Grimm wrote, on 19/06/11 16:31:
Yes thanks... I wanted to give it a while to check that it worked.
Feel free to close the bug.
Regards,
Arthur.