[EMAIL PROTECTED] wrote:
Hello,
I am experiencing a problem very similar to Kerry's. Attempts to 'tellnews update' result in only a few articles getting pulled down rather than the 300 or so that are often available. Per Chris' instructions, here is the log with debugging turned on. Can someone help? Maybe my upstream server has a crazy article numbering scheme.
It does appear to be unhappy with the 'next' command, set in dnews.conf
suck_stream true
if that doesn't fix it send me your dnews.conf and the log again.
ChrisP.
Thanks, Gordon
08 11:06:21 0:info: nntp: Setting TCP_NODELAY for socket [0]
08 11:06:21 0:info: max_mb = 0, max_con=0, max_users=0 areamb=0
08 11:06:21 0:info: chan: Currently 1 users (1,0) from a_* machine1.mshome.net
08 11:06:21 0:warn: nntp: connection [0:200] From machine1.mshome.net 192.168.0.198
08 11:06:21 0:info: skip 0 all 155889
08 11:06:21 0:info: nntp: Setting TCP_NODELAY for socket [0]
08 11:06:21 0:info: key: Loaded ok flags (0) NonFree NoSpoolLimit
08 11:06:21 0:info: Manager Command (fcmd PASSWORD getold comp.unix.admin 100 )
08 11:06:21 0:info: key: Loaded ok flags (0) NonFree NoSpoolLimit
08 11:06:21 0:info: cmd: Do cmdx[0:machine1.mshome.net] {quit} {quit}
08 11:06:21 :info: Close later called and now closing chan [0]
08 11:06:21 :info: chan: Currently 0 users from a_*
08 11:06:27 :info: db_pile_status
08 11:06:27 :info: db_pile_status_done
08 11:06:27 :info: dnews_status 1
08 11:06:27 :info: dnews_status 2
08 11:06:27 :info: dnews_status 3
08 11:06:27 :info: Timezone Offset 25200 dst 3600
08 11:06:29 :debug: suck: flush 60
08 11:06:29 :debug: suck: flush 60 part 2
08 11:06:29 :debug: suck: Chan purge done
08 11:06:39 0:info: nntp: Setting TCP_NODELAY for socket [0]
08 11:06:39 0:info: max_mb = 0, max_con=0, max_users=0 areamb=0
08 11:06:39 0:info: chan: Currently 1 users (1,0) from a_* machine1.mshome.net
08 11:06:39 0:warn: nntp: connection [0:264] From machine1.mshome.net 192.168.0.198
08 11:06:39 0:info: skip 0 all 155892
08 11:06:39 0:info: nntp: Setting TCP_NODELAY for socket [0]
08 11:06:39 0:info: key: Loaded ok flags (0) NonFree NoSpoolLimit
08 11:06:39 0:info: Manager Command (fcmd PASSWORD updateone comp.unix.admin )
08 11:06:39 0:info: key: Loaded ok flags (0) NonFree NoSpoolLimit
08 11:06:39 0:info: cmd: Do cmdx[0:machine1.mshome.net] {quit} {quit}
08 11:06:39 :info: Close later called and now closing chan [0]
08 11:06:39 :info: chan: Currently 0 users from a_*
08 11:06:40 :debug: suck: Pop group {comp.unix.admin}
08 11:06:40 :debug: suck: idle {comp.unix.admin}
08 11:06:40 :info: suck: group comp.unix.admin from news.west.cox.net ( ****)
08 11:06:40 :info: chan: chan_open {news.west.cox.net}
08 11:06:40 :info: nntp: Setting TCP_NODELAY for socket [0]
08 11:06:40 :info: suck: Open channel 0 to {news.west.cox.net}
08 11:06:40 0:debug: suck: check -- 200 Cox Internet Service (fed1read06) (Tornado v1.0.6)
08 11:06:40 0:debug: suck: check set cstate to [0] 3
08 11:06:40 0:debug: suck: check set fstate {F_OPEN_DOMODE}
08 11:06:40 :info: suck: news.west.cox.net Connected: 200 Cox Internet Service (fed1read06) (Tornado v1.0.6)
08 11:06:40 :debug: suck: --> mode reader
08 11:06:40 0:debug: suck: check -- 200 Cox Internet Service (fed1read06) (Tornado v1.0.6.363)
08 11:06:40 0:debug: suck: check set cstate to [0] 5
08 11:06:40 0:debug: suck: check set fstate {F_FORGROUP}
08 11:06:40 :debug: suck: forgroup {comp.unix.admin}
08 11:06:40 :debug: suck: --> group comp.unix.admin
08 11:06:40 0:debug: suck: check -- 211 64918 17468394 17628718 comp.unix.admin
08 11:06:40 0:debug: suck: check set cstate to [0] 5
08 11:06:40 0:debug: suck: check set fstate {F_GET}
08 11:06:40 :debug: suck: suck group 17468394 17628718, fend 17628618
08 11:06:40 :warn: suck: Fetching group comp.unix.admin 100 new from 17628619 to 17628718
08 11:06:40 :debug: suck: --> stat 17628619
08 11:06:40 0:debug: suck: next -- 423 No Such Article In Group
08 11:06:40 0:debug: suck: status!=220, but ok here stat 17628620
08 11:06:40 0:debug: suck: --> stat 17628620
08 11:06:40 0:debug: suck: next -- 423 No Such Article In Group
08 11:06:40 0:debug: suck: status!=220, but ok here stat 17628621
08 11:06:40 0:debug: suck: --> stat 17628621
08 11:06:40 0:debug: suck: next -- 423 No Such Article In Group
08 11:06:40 0:debug: suck: status!=220, but ok here stat 17628622
08 11:06:40 0:debug: suck: --> stat 17628622
08 11:06:40 0:debug: suck: next -- 423 No Such Article In Group
08 11:06:40 0:debug: suck: status!=220, but ok here stat 17628623
08 11:06:40 0:debug: suck: --> stat 17628623
08 11:06:40 0:debug: suck: next -- 423 No Such Article In Group
08 11:06:40 0:debug: suck: status!=220, but ok here stat 17628624
08 11:06:40 0:debug: suck: --> stat 17628624
08 11:06:40 0:debug: suck: next -- 423 No Such Article In Group
08 11:06:40 0:debug: suck: status!=220, but ok here stat 17628625
08 11:06:40 0:debug: suck: --> stat 17628625
08 11:06:40 0:debug: suck: next -- 423 No Such Article In Group
08 11:06:40 0:debug: suck: status!=220, but ok here stat 17628626
08 11:06:40 0:debug: suck: --> stat 17628626
08 11:06:40 0:debug: suck: next -- 423 No Such Article In Group
08 11:06:40 0:debug: suck: status!=220, but ok here stat 17628627
08 11:06:40 0:debug: suck: --> stat 17628627
08 11:06:40 0:debug: suck: next -- 423 No Such Article In Group
08 11:06:40 0:debug: suck: status!=220, but ok here stat 17628628
08 11:06:40 0:debug: suck: --> stat 17628628
08 11:06:40 0:debug: suck: next -- 223 17628628 <[EMAIL PROTECTED]>
08 11:06:40 0:debug: suck: --> next
08 11:06:40 0:debug: suck: next -- 223 17628684 <[EMAIL PROTECTED]>
08 11:06:40 0:debug: suck: --> next
08 11:06:40 0:debug: suck: next -- 223 17628718 <[EMAIL PROTECTED]>
08 11:06:40 0:debug: suck: --> next
08 11:06:40 0:debug: suck: next -- 421 No Next Article
08 11:06:40 0:debug: suck: status!=223, doing next group 421 No Next Article
08 11:06:40 :info: Close later called and now closing chan [0]
08 11:07:18 :info: db_piles_trim called
08 11:07:28 :info: db_pile_status
08 11:07:28 :info: db_pile_status_done
"Chris Pugmire" <[EMAIL PROTECTED]> wrote:
I have been experiencing difficulties with some newsgroups. Articles which
are
on the machine I am sucking from do not appear. If I look in dnews.log I
see
dnews.log:16 12:10:50.920 :warn: group: Catching up group microsoft.public.mone
y fend 58932
What does the fend mean and how do I fix it?
It doesn't mean much, it implies dnews decided to skip to
the end of the available items, usually dnews does this if
a large gap is found or something 'odd' happens, it does this
in an attempt to start getting 'real' items again instead of being
left 'stuck' on faulty ones.
Try and find the relevant section in suck.log, or test it again like this:
tellnews debug suck:
tellnews loglvl debug
tellnews getold microsoft.public.money 100
tellnews updateone microsoft.public.money N
(where n is the suck number, defaults to nntp_feeder)
Send us the resulting log section.
ChrisP.
