[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [leafnode-list] leafnode very slow on first XOVER
"Michael O'Quinn" <michael@xxxxxxxxxxx> writes:
> I've seen similar behavior. In my case what is happening is that
> fetchnews dies with the message to the console "Broken pipe" and never
> spawns the process that updates the .overview files. As a result the
Can anyone of you figure from his logs when or why fetchnews gets the
"broken pipe"? It may be necessary to run fetchnews after placing
debugmode=1 in /etc/leafnode/config to get useful logs.
> first attempt to access new articles in a group causes leafnode to update
> the .overview file. This requires opening and reading the headers of each
> and every new message, and that can take quite a long time on very active
I can have leafnode 1.9.20's fetchnews catch the SIGPIPE and still run
the XOVER updater, to work around this problem, but I'd rather go figure
why that happens, and maybe fix the bug that triggers it. I might also
do other changes like adding a switch to fetchnews, but I'm reluctant to
do that before 1.9.20.
> I've often wished for either a daemon or a program that could be invoked
> from cron whose only purpose is to scan the entire news tree on a regular
> basis and make sure the .overview files are up to date.
You can run texpire for now, it does more than just fixing overviews though.
> This issue may not be technically considered a "Bug", but it does
How do you know triggering EPIPE/SIGPIPE is not a "bug"? :-)
GPG encrypted mail welcome, unless it's unsolicited commercial email.
leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx -- mailing list for leafnode
To unsubscribe, send mail with "unsubscribe" in the subject to the list