[leafnode-list] Re: delaybody -- no response

[Matthias Andree <matthias.andree@xxxxxx>]

Am 09.08.2013 00:47, schrieb thufir:
> I have been using delaybody, but seem to have run into a problem where 
> leafnode keeps trying to get the body for a few messages but can't (for 
> whatever reason).
> 
> thufir@dur:~$ 
> thufir@dur:~$ 
> thufir@dur:~$ tail /var/log/news/news.err
> Aug  8 15:20:36 dur fetchnews[3304]: Cannot obtain lock file, aborting.
> Aug  8 15:20:51 dur fetchnews[3305]: Cannot obtain lock file, aborting.
> Aug  8 15:42:18 dur fetchnews[3559]: mozilla.support.firefox: Retrieving 
> body <k92lv85m5trafg4qkf1bda1uihr27erqia@xxxxxxx> failed. No response
> Aug  8 15:42:19 dur fetchnews[3559]: mozilla.support.firefox: Retrieving 
> body <Yz7Q3QchIV$RFwXG@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> failed. No 
> response
> Aug  8 15:42:20 dur fetchnews[3559]: mozilla.support.firefox: Retrieving 
> body <ktlh0h$e82$1@xxxxxxxxxxxxxxxxx> failed. No response
> Aug  8 15:42:21 dur fetchnews[3559]: mozilla.support.firefox: Retrieving 
> body <5oudnc9XKYuOEGPMnZ2dnUVZ_qednZ2d@xxxxxxxxxxx> failed. No response
> Aug  8 15:42:22 dur fetchnews[3559]: mozilla.support.firefox: Retrieving 
> body <g9adnYuNe8LEB2PMnZ2dnUVZ_oudnZ2d@xxxxxxxxxxx> failed. No response
> Aug  8 15:42:23 dur fetchnews[3559]: mozilla.support.firefox: Retrieving 
> body <GL-dndInntPLUJ_PnZ2dnUVZ_qudnZ2d@xxxxxxxxxxx> failed. No response
> Aug  8 15:42:24 dur fetchnews[3559]: mozilla.support.firefox: Retrieving 
> body <m9ydnYbc1_l6TZ_PnZ2dnUVZ_hKdnZ2d@xxxxxxxxxxx> failed. No response
> Aug  8 15:42:25 dur fetchnews[3559]: mozilla.support.firefox: Retrieving 
> body <R7-dnR5snptJTJ_PnZ2dnUVZ_rOdnZ2d@xxxxxxxxxxx> failed. No response
> thufir@dur:~$ 
> thufir@dur:~$ ll /var/spool/news/interesting.groups/
> mozilla.support.firefox 
> -rw-rw-r-- 1 news news 32 Aug  8 15:42 /var/spool/news/interesting.groups/
> mozilla.support.firefox
> thufir@dur:~$ 
> thufir@dur:~$ 
> 
> 
> 
> is it safe to just go into the firefox file in interesting.groups and 
> just delete out the lines?  This is where leafnode keeps track of which 
> articles need bodies?

Thufir,

Can you obtain debug information (NNTP command and response trace in
particular)?  Leafnode-1 is rather picky when it sends the BODY
<5oudnc9XKYuOEGPMnZ2dnUVZ_qednZ2d@xxxxxxxxxxx> command, and expects
nothing else than 222 back.  We may need to handle the case where an
article got removed upstream (spam cancel, or whatever), and I'd need to
know if the result code is 430, or something else.

Best regards
Matthias

-- 
_______________________________________________
leafnode-list mailing list
leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
https://www.dt.e-technik.uni-dortmund.de/mailman/listinfo/leafnode-list
http://leafnode.sourceforge.net/