[leafnode-list] Re: Fetchnews messages
Enrico Wiki
enrico.c.ml.address at gmail.com
Sat May 23 10:17:30 CEST 2009
On Tue, May 19, 2009 at 4:29 PM, Matthias Andree wrote:
> Am 19.05.2009, 15:31 Uhr, schrieb Enrico Wiki:
>
> On Sat, May 16, 2009 at 6:41 PM, Matthias Andree wrote:
>>
>> Am 16.05.2009, 12:28 Uhr, schrieb Enrico Wiki :
>>
>>>
>>> On Wed, May 13, 2009 at 10:45 PM, Matthias Andree wrote:
>>>
>>>>
>>>>
[...]
> Well, no, it wasn't aborted.
>>>
>>>> I tried again (starting from scratch) and had the same results.
>>>>
>>>
>>> Have some of the articles been crossposted to several groups? Then
>>> leafnode will have fetched it for one of the groups, and when it's listed in
>>> another, it will not download another copy, because it already has it.
>>>
>>
>>
>> Nope, no crossposted articles, in that case. Just
>>
>> *"store: duplicate article "
>>
>> and in the same number as the "killed" articles.
>>
>
> Euh. I think - again, without looking at code - that something with
> fetchnews OR with your spool is wrong.
>
> For some reason, fetchnews decides inconsistently if it already has certain
> articles in the spool. Does this happen with XHDR or with XOVER or with
> both?
>
Both.
>
> At any rate, PLEASE DO SAVE your current configuration and command lines
> and take notes of what might trigger these store: duplicate article. I think
> there's a bug in fetchnews/store/... somewhere. In the simplest case, it's
> just XHDR responses not being used properly, but that doesn't go without
> closer inspection (which I don't have time for in the next few days).
>
> Could you do me a favour and save your current configuration,
Ok. Do you need the config file or other files too?
> and if you can afford the space, also a tarball/pax archive,
I can do that, but do you want me to send it? It's pretty big.
> or rsync copy of the spool with hard links intact, and also command lines
> that you used
That's easy:
fetchnews
fetchnews -N [group]
> (try "history" if you've been hacking away in your shell). I may need some
> of this information later for debugging.
>
> Thanks in advance.
I would be happy to help. Also see my reply to Clemens.
--
Enrico
More information about the leafnode-list
mailing list