[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[leafnode-list] fetchnews doesn't connect to one of two servers

To: leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Subject: [leafnode-list] fetchnews doesn't connect to one of two servers
From: davidg@xxxxxxxxx (David J. Greenberger)
Date: Fri, 11 Jul 2003 11:12:51 -0400
Original-message-id: <87el0xgkr0.fsf@greenberger.no-ip.com>
Reply-to: leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
User-agent: Gnus/5.1002 (Gnus v5.10.2) XEmacs/21.4 (Common Lisp, linux)

I just upgraded to Leafnode 1.9.41-1 on a Debian system, and fetchnews
is unable to retrieve articles from one of its servers.

Here is the output of fetchnews -fvvv:

========
leafnode 1.9.41.rel: verbosity level is 3
Trying to connect to news.cis.dfn.de:nntp ... connected.
Using STAT <message-ID> command on this server.
news.cis.dfn.de: 0 articles posted
Getting all newsgroups from news.cis.dfn.de
Reading server info from /var/spool/news/leaf.node/news.cis.dfn.de
rec.autos.driving: no new articles
rec.travel.usa-canada: considering articles 257217 - 257499
rec.travel.usa-canada: will fetch 257251 (/var/spool/news/message.id/847/<afjdkjjkkj-americanos-ljkjj@xxxxxxxxx>)
rec.travel.usa-canada: will fetch 257252 (/var/spool/news/message.id/367/<c2f8f5f0.0307080855.8e72f19@xxxxxxxxxxxxxxxxxx>)
rec.travel.usa-canada: will fetch 257253 (/var/spool/news/message.id/720/<ZPCOa.42237$JY1.28331@xxxxxxxxxxxxxxxxxxxx>)
[...many lines snipped...]
rec.travel.usa-canada: will fetch 257498 (/var/spool/news/message.id/591/<3f0d6970$1@xxxxxxxxxxxxxxx>)
rec.travel.usa-canada: will fetch 257499 (/var/spool/news/message.id/640/<3f0d69c5$1@xxxxxxxxxxxxxxx>)
rec.travel.usa-canada: receiving article 257251 (247 more up in the air)
Discarding article 257251 - no Date:  found
Discarding article 257251 - older than 20 days
Server disconnection or timeout before article could be retrieved
Disconnected from news.cis.dfn.de.
Trying to connect to news.opera.com:nntp ... connected.
Using STAT <message-ID> command on this server.
news.opera.com: 0 articles posted
Getting all newsgroups from news.opera.com
Reading server info from /var/spool/news/leaf.node/news.opera.com
rec.autos.driving: no such group
rec.travel.usa-canada: no such group
opera.linux: no new articles
linux.debian.user: no such group
opera.wishlist: no new articles
comp.emacs.xemacs: no such group
misc.consumers.frugal-living: no such group
comp.os.linux.misc: no such group
opera.beta: considering articles 38792 - 38794
opera.beta: will fetch 38792 (/var/spool/news/message.id/684/<bejnqb$a49$1@xxxxxxxxxxxxx>)
opera.beta: will fetch 38793 (/var/spool/news/message.id/057/<Xns93B45E870778Dlpsp53hotmailcom@xxxxxxxxxxxx>)
opera.beta: will fetch 38794 (/var/spool/news/message.id/630/<oprr3jjhhnrn2rkc@xxxxxxxxxxxxx>)
opera.beta: receiving article 38792 (2 more up in the air)
storing <bejnqb$a49$1@xxxxxxxxxxxxx>: opera.beta
.as article 512 in opera.beta
opera.beta: receiving article 38793 (1 more up in the air)
storing <Xns93B45E870778Dlpsp53hotmailcom@xxxxxxxxxxxx>: opera.beta
.as article 513 in opera.beta
opera.beta: receiving article 38794 (0 more up in the air)
storing <oprr3jjhhnrn2rkc@xxxxxxxxxxxxx>: opera.beta
.as article 514 in opera.beta
opera.beta: 3 articles fetched, 0 killed
misc.transport.road: no such group
comp.mail.pine: no such group
misc.transport.urban-transit: no such group
comp.graphics.apps.gimp: no such group
alt.culture.ny-upstate: no such group
misc.consumers: no such group
comp.os.linux.x: no such group
opera.os2: no new articles
gnu.emacs.gnus: no such group
comp.theory: no such group
alt.planning.urban: no such group
rec.photo.film+labs: no such group
comp.os.linux.answers: no such group
soc.culture.jewish.moderated: no such group
nyc.transit: no such group
Disconnected from news.opera.com.
wrote active file with 22437 lines
Started process to update overview data in the background.
Network activity has finished.
========

And here is my /etc/news/leafnode/config file:

========
## This is the NNTP server leafnode fetches its news from.
## You need read and post access to it. Mandatory.
server = news.cis.dfn.de

## Unread discussion threads will be deleted after this many days if
## you don't define special expire times. Mandatory.
expire = 20

##
## All the following parameters are optional
##

## I have free access to my news server. If you don't have, comment out
## the following two lines and change them accordingly.
username = [deleted]
password = [deleted]

## Standard news servers run on port 119. If your newsserver doesn't, comment
## out the following line and change it accordingly.
# port = 8000

## This is another news server which stores some groups that are not
## available on the first one. You can define username, password and port
## for each server separately.
server = news.opera.com
# username = xenu
# password = secret

## This is a news server which does not understand the 
## "LIST NEWSGROUP news.group" command. For this reason, we don't try to
## download newsgroups descriptions when getting new newsgroups. This is
## achieved by putting "nodesc = 1" somewhere behind the server
## line.
# server = broken.upstream.server
# nodesc = 1

## Here we have another news server which has a very slow connection. For
## that reason, we wait a full minute before we give up trying to connect.
## The default is 10 seconds.
# server = really.slow.snail
# timeout = 60

## Non-standard expire times (glob(7) wildcard constructs possible)
# groupexpire comp.os.linux.* = 5 # groups too big to hold articles 20 days
# groupexpire any.local.newsgroup = 100 # very interesting, hold articles longer

## Never fetch more than this many articles from one group in one run.
## Be careful with this; setting it much below 1000 is probably a bad
## idea.
maxfetch = 5000

## Fetch only a few articles when we subscribe a new newsgroup. The
## default is to fetch all articles.
# initialfetch = 100

## If you want to use leafnode like an offline newsreader (e.g. Forte
## Agent) you can download headers and bodies separately if you set
## delaybody to 1. In this case, fetch will only download the headers
## and only when you select an article, it will download the body.
## This can save a huge amount of bandwith if only few articles are really
## read from groups with lots of postings.
## This feature works not very well with Netscape, though (which is not
## a fault of Leafnode).
# delaybody = 0

## To avoid spam, you can select the maximum number of crosspostings
## that are allowed in incoming postings. Setting this below 5 is
## probably a bad idea. The default is unlimited crossposting.
# maxcrosspost = 5

## If you suffer from repeatedly receiving old postings (this happens
## sometimes when an upstream server goes into hiccup mode) you can
## refuse to receive them with the parameter "maxage" which tells the
## maximum allowed age of an article in days. The default maxage is 10
## days.
maxage = 20

## maxlines will make fetch reject postings that are longer than a certain
## amount of lines.
# maxlines = 100

## minlines will make fetch reject postings that are shorter than a certain
## amount of lines.
# minlines = 2

## maxbytes will make fetch reject postings that are larger
# maxbytes = 50000

## timeout_short determines how many days fetch gets a newsgroup which
## has been accidentally opened. The default is two days.
# timeout_short = 1

## timeout_long determines how many days fetch will wait before not getting
## an unread newsgroup any more. The default is seven days.
# timeout_long = 6

## timeout_active determines how many days fetch will wait before re-reading
## the whole active file. The default is 90 days.
# timeout_active = 365

## If you want to have your newsreader score/kill on Xref: lines, you might
## want to uncomment this.
# create_all_links = 1

## If you want to filter out certain regular expressions in the header,
## create a "filterfile" (how this is done is explained in the README)
## and set
# filterfile = /path/to/your/filterfile

## If your newsreader does not supply a Message-ID for your postings
## Leafnode will supply one, using the hostname of the machine it is
## running on.  If this hostname is not suitable, this parameter can be 
## used to override it.  Do not use a fantasy name, it may interfere with
## the propagation of your messages.  Most modern newsreaders do provide
## a Message-ID.
# hostname = 
========

Any ideas of how to get this to work again?  Thanks.
-- 
David J. Greenberger
New York, NY

-- 
leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx -- mailing list for leafnode
To unsubscribe, send mail with "unsubscribe" in the subject to the list

Follow-Ups:
- Re: [leafnode-list] fetchnews doesn't connect to one of two servers
  - From: Matthias Andree

Prev by Date: Re: [leafnode-list] Feature request
Next by Date: [leafnode-list] Memory corruption bug in leafnode-2.0.0.alpha20030710a?
Previous by thread: [leafnode-list] leafnode 2.0.0.alpha20030710a
Next by thread: Re: [leafnode-list] fetchnews doesn't connect to one of two servers
Index(es):
- Date
- Thread