tdx-util/expire question and overchan question

William Kronert wkronert at sunstroke.sdsu.edu
Mon Jan 19 01:49:26 UTC 2009


Hi Julien,

At 06:17 AM 1/17/2009, Julien ÉLIE wrote:
>>>tdx-util: tradindexed: low water mark 
>>>incorrect for tw.bbs.music.japan: 277375 != 277374
>>>tdx-util: tradindexed: count incorrect for tw.bbs.music.japan: 19 != 20
>>
>>When such a thing occurs, what is the ouput of:
>>
>>    grep "tw.bbs.music.japan" /var/lib/news/active
>>    tdx-util -i -n tw.bbs.music.japan
>>
>>The above gave me:
>>tw.bbs.music.japan 0000277397 0000277392 y
>
>You should try the same commands just after you receive such
>an error from tdx-util.
>As for tw.bbs.music.japan, it has been fixed since it occured.
>(The low water mark is now 277392 -- and not 277374.)

I finally got another one of these from tdx-util:

tdx-util: tradindexed: low water mark incorrect 
for de.comm.software.browser.misc: 1914 != 1913
tdx-util: tradindexed: count incorrect for 
de.comm.software.browser.misc: 2 != 3

-sh-3.00$ grep "de.comm.software.browser.misc" /var/lib/news/active
de.comm.software.browser.misc 0000001915 0000001913 y

Telnet to server and issued:
GROUP de.comm.software.browser.misc
211 3 1913 1915 de.comm.software.browser.misc
HDR Xref 1913
423 No articles in 1913
HDR Xref 1914
225 Header or metadata information for Xref follows (from overview)
1914 newshub.sdsu.edu de.comm.software.browser.misc:1914

After doing ctlinnd renumber de.comm.software.browser.misc:
GROUP de.comm.software.browser.misc
211 3 1913 1915 de.comm.software.browser.misc
HDR Xref 1913
423 No articles in 1913
HDR Xref 1914
225 Header or metadata information for Xref follows (from overview)
1914 newshub.sdsu.edu de.comm.software.browser.misc:1914

Then after doing tdx-util -F:
GROUP de.comm.software.browser.misc
211 2 1914 1915 de.comm.software.browser.misc
HDR Xref 1913
423 No articles in 1913
HDR Xref 1914
225 Header or metadata information for Xref follows (from overview)
1914 newshub.sdsu.edu de.comm.software.browser.misc:1914

After all that I then recheck the grep information on the newsgroup:
grep "de.comm.software.browser.misc" /var/lib/news/active
de.comm.software.browser.misc 0000001915 0000001913 y

>>That overview is just removed during news.daily 
>>if the article is removed from the spool and is 
>>done in a quiet mode.  That is my best understanding of it.
>
>OK.  That explains why expireover is done after expire when
>groupbaseexpiry is set to false.  (Otherwise, expireover
>is done before expire.)
>
>>Yep, that is my understanding, it is in quit 
>>mode if groupbaseexpiry is false.  I don't know 
>>why and think this would be better if it did 
>>not suppress the drop overview index.
>
>In fact, it is not a problem of quietness.  ("Article lines processed"
>is set to 0 during expireover with groupbaseexpiry set to false.)
>However, you *do* have the information:
>
>Your report:
>
>    expire begin Sat Jan 17 03:00:58 PST 2009: (-v1 -N)
>         Article lines processed  1046456
>         Articles retained         961432
>         Entries expired            85024
>         Articles dropped           82999
>    expire end Sat Jan 17 03:01:06 PST 2009
>    expireover start Sat Jan 17 03:01:06 PST 2009
>    expireover end Sat Jan 17 03:02:02 PST 2009
>The information about "Overview index dropped" is probably
>related to you "Articles dropped".

That might be true but in a indirect way since 
expireover runs after expire so the numbers 
reported for "Articles dropped" can only give you 
an idea of about what should be drop from 
overview - if I understand it correctly.

I just think it is odd that information about 
Overview dropped has been left out and wonder 
what the reason is for doing that.

Anyway, time to give it a break.  I have been 
struggling with that docheckgroups and the 
suggestions you made an e-mail...I haven't gotten anything to work yet.

Bill




More information about the inn-workers mailing list