Xref: utzoo news.software.nntp:1165 news.software.nn:1690 Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!helios!bcm!dimacs.rutgers.edu!rutgers!uwm.edu!caen!uakari.primate.wisc.edu!samsung!uunet!munnari.oz.au!uhccux!cfht.hawaii.edu!jwright From: jwright@cfht.hawaii.edu (Jim Wright) Newsgroups: news.software.nntp,news.software.nn Subject: Re: Having nntp 1.5.11 troubles... Message-ID: Date: 5 Mar 91 22:05:17 GMT References: <1991Mar4.212651.12120@cica.indiana.edu> Sender: news@uhccux.uhcc.Hawaii.Edu Followup-To: news.software.nntp Lines: 41 mr@ogre.cica.indiana.edu (Michael Regoli) writes: >... >N: Mar 4 15:06 (M): Lost connection to server cica.cica.indiana.edu: > No such file or directory >C: Mar 4 15:06 (M): Collect: 250 art, 99 gr, 279 s >N: Mar 4 15:20 (M): Lost connection to server cica.cica.indiana.edu: > No such file or directory >C: Mar 4 15:20 (M): Collect: 268 art, 110 gr, 228 s >N: Mar 4 15:33 (M): Lost connection to server cica.cica.indiana.edu: > No such file or directory >C: Mar 4 15:33 (M): Collect: 261 art, 88 gr, 148 s >... I was having the same trouble after changing from 6.4.11 to 6.4.12. Not only did it generate these messages, it failed to collect many groups at all. And many other groups it would only collect about 5% of the posted articles. I was on the verge of junking nn! I just changed from 6.4.12 to 6.4.13. In the process, I (intentionally) deleted GROUPS, MASTER, ACTIVE and DATA/*. Then I did an nnmaster -D. When it got to the group alt.desert-storm, it sucked over all the headers and then said that there were 0 articles! From then on every group reported 0 articles. By the speed at which it went through the articles, it was obvious that the entire header was not being sent. I ^C'd out and editted the GROUPS file to kill alt.desert-storm, removed alt.[d-z]* files from the DATA/ directory, and restarted the nnmaster. The same procedure was required for the group junk. Our nntp feed is running an old version of nntp. I asked them about upgrading, and they said "someday..." All seems to be working now, but I'm going to keep a close eye on this. It seems to me that nn is not reacting correctly to some sort of error message or bogus nntp message. The error message produced by nn is less than helpful. -- Jim Wright jwright@cfht.hawaii.edu Canada-France-Hawaii Telescope Corp.