[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[leafnode-list] Undelivered Mail Returned to Sender

For further assistance, please send mail to <postmaster>If you do so, please include this problem report. You can
delete your own text from the message returned below.

			The Postfix program<mike@xxxxxxxxxxxxxxx>: deferred transport

Content-Description: Delivery error report
Content-Type: message/delivery-statusReporting-MTA: dns; osiris.terra.de
Arrival-Date: Fri,  8 Mar 2002 18:58:05 +0100 (CET)

Final-Recipient: rfc822; mike@xxxxxxxxxxxxxxx
Action: failed
Status: 4.0.0
Diagnostic-Code: X-Postfix; deferred transport--4C037413FD.1016044839/osiris.terra.de
Content-Description: Undelivered Message
Content-Type: message/rfc822

Received: by osiris.terra.de (Postfix)
	id 4C037413FD; Fri,  8 Mar 2002 18:58:05 +0100 (CET)
Delivered-To: mike@xxxxxxxxxxxxxxxxxx
Received: from localhost (localhost [])
	by osiris.terra.de (Postfix) with ESMTP id D282B413FB
	for <mike@localhost>; Fri,  8 Mar 2002 18:58:04 +0100 (CET)
Received: from fwdallmx.t-online.com []
	by localhost with POP3 (fetchmail-5.9.6)
	for mike@localhost (single-drop); Fri, 08 Mar 2002 18:58:04 +0100 (CET)
Received: from wpxx02.toxi.uni-wuerzburg.de ([]) by mailin03.sul.t-online.de
	with esmtp id 16jGxU-1Dczy4a; Fri, 8 Mar 2002 10:46:40 +0100
Received: from wpxx02.toxi.uni-wuerzburg.de ([])
	by wpxx02.toxi.uni-wuerzburg.de with smtp (Exim 3.22 #1)
	id 16jGkh-0005Jc-00; Fri, 08 Mar 2002 10:33:27 +0100
From: Matthias Andree <ma@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Reply-To: leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Errors-To: leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
To: leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Message-ID: <3C888567.BeroList-2.5.9@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
X-Received: from krusty.e-technik.uni-dortmund.de ([] ident=postfix)
X-Received: from merlin.emma.line.org (localhost [])
X-Received: by merlin.emma.line.org (Postfix, from userid 500)
X-Draft-From: ("nnml+private:ln" 3466)
In-Reply-To: <3C87A5CC.BeroList-2.5.9@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> ("Michael
 O'Quinn"'s message of "Thu, 7 Mar 2002 09:39:18 -0800 (PST)")
Date: Fri, 08 Mar 2002 10:33:21 +0100
Original-Message-Id: <m3bsdze74u.fsf@xxxxxxxxxxxxxxxxxxxx>
Lines: 35
User-Agent: Gnus/5.090006 (Oort Gnus v0.06) Emacs/21.1 (i686-pc-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Precedence: bulk
Subject: 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
> groups.

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"? :-)-- 
Matthias Andree

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


leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx -- mailing list for leafnode
To unsubscribe, send mail with "unsubscribe" in the subject to the list