[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [leafnode-list] groups listed twice in groupinfo, and other
On Friday 08 November 2002 19:16, ma wrote:
> > Other than that, is it normal for a group to show up twice in teh
> > groupinfo file?
>
> No, that Should Not Happen[tm]. Can you feed the output of your grep
> through a hexdump utility and make sure that there are no control
> characters that escape the display? Try hexdump, od, xxd (comes with
> vim) if you don't know where to start?
Ok, xxd produced the most usable output imo:
Example group alt.sci.seti
Commandline: grep alt.sci.seti groupinfo|xxd
0000000: 616c 742e 7363 692e 7365 7469 2037 3637 alt.sci.seti 767
0000010: 3430 2032 2031 3033 3630 3730 3433 3620 40 2 1036070436
0000020: 5365 6172 6368 2066 6f72 2045 7874 7261 Search for Extra
0000030: 2054 6572 7265 7374 7269 616c 2049 6e74 Terrestrial Int
0000040: 656c 6c69 6765 6e63 650a 616c 742e 7363 elligence.alt.sc
0000050: 692e 7365 7469 2037 3635 3837 2032 2031 i.seti 76587 2 1
0000060: 3033 3630 3730 3433 3620 5365 6172 6368 036070436 Search
0000070: 2066 6f72 2045 7874 7261 2054 6572 7265 for Extra Terre
0000080: 7374 7269 616c 2049 6e74 656c 6c69 6765 strial Intellige
0000090: 6e63 650a nce.
> Has that "double" newsgroup arrived recently? Could you show the
> lines that grep offered?
I don't know when it arrived, it could have been there for up to a
year... But! I've not noticed any problems before this week, and had no
reason to go look in the newspool before.
Now, I noticed not all groups seem affected... So, I gathered a bit of
stats:
cat groupinfo|wc -l
101444
cat groupinfo | sort | uniq | wc -l
83774
cat groupinfo | sort | uniq -d |wc -l
17670
My reaction to this right now would be.... "Oi..."
Hmm... Found a backup tarball of the newspool from Sunday.. (I was
testing a CDRW disc that looked scratched...), let me try see what
groupinfo looks like on there... Unfortunately I can't remember when I
upgraded to .29 (it was no sooner than the week before the backup,
possible after), and I can't tell if there were any problems like the
one with the groupinfo file with the previous versions of leafnode!
Urgh, what a mess I have here...
Hmm... wait a minute.... Now I remember why I upgraded to .29 in the
first place, the old version (maybe .23 or .25??) kept downloading list
of ALL newsgroups from ALL servers over and over again!! Could this be
related?... I seem to recall I did do something with the newspool to
stop fetchnews from doign this... (fetchnews -f didn't do anything,
subsequent runs still fetched *all* newsgroups)..
Ah, but finally while I have been throwing potentialyl useless garbage
at you, my comptuer has extracted groupinfo file from the backup (It
takes long to scan a tar.bz2 archive....)
Let me try run those same tests again
Total lines in groupinfo: 83725
Unique lines in groupinfo: 83725
Duplicates: 0
This from Sunday's backup of the newsspool, so ok, the duplication of
groupinfo lines is very recent, either when I upgraded to leafnode
..29, or the patch v1/v2 (nah not possible?)...
*reaches for cron and stops teh fetchnews job*
I seem to recall that I did touch /var/spool/news/active.read and chown
news.news /var/spool/news/active.read to stop fetchenws from
re-acquiring the kust if newsgroups over and over again (this was
eating lots of bandwidth)... Could this have triggered or caused the
duplicate groupinfo lines I'm seeing now? (active.read file was
nonexistant before i touch'd it, /var/spool/news has ownership
news.news and drwxrwsr-x)
The active.read file is not in my backup (I think it is safe to assume
that backup was taken before upgrading to .29, while fetchnews was
still fetching all groups all the time)
Sorry for throwing this mass of raving lunacy of a bugreport at you, I
have had little sleep ;-)
Regards, JK
--
leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx -- mailing list for leafnode
To unsubscribe, send mail with "unsubscribe" in the subject to the list