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

[leafnode-list] leafnode stopped working



Hello.

I have been running leafnode wthout problems in my home
computer (Gentoo Linux) until recently. But lately it has
stopped working. Maybe someone can help me find what is
going on and correct it.  I have leafnode-1.9.51.rel
installed. I have attached some of my configuration files.

# fetchnews -vvv -f
leafnode 1.9.51.rel: verbosity level is 3, debugmode is 1
try_lock(timeout=5), fqdn="gentoo.malaquias.no-ip.org"
Forced active fetch requested from command-line (option -f).
Trying to connect to news-read2.maxwell.syr.edu:nntp ... connected.
Using STAT <message-ID> command on this server.
Not posting to news-read2.maxwell.syr.edu: non-permission
Getting all newsgroups from news-read2.maxwell.syr.edu
Warning: skipping group "alt.", invalid name (NULL component).
Newsgroup name conflict: alt.2600.aol vs. alt.2600.AOL
Newsgroup name conflict, chose alt.2600.aol
[...]
Newsgroup name conflict: microsoft.public.word.OLEinterop vs. microsoft.public.word.oleinterop
Newsgroup name conflict, chose microsoft.public.word.oleinterop
Reading server info from /var/spool/news/leaf.node/news-read2.maxwell.syr.edu
Disconnected from news-read2.maxwell.syr.edu.
WARNING: found no server with posting permission!
wrote active file with 25858 lines
Started process to update overview data in the background.
Network activity has finished.

# /etc/init.d/xinetd status
 * status:  started

# fetchnews -vvv
leafnode 1.9.51.rel: verbosity level is 3, debugmode is 1
try_lock(timeout=5), fqdn="gentoo.malaquias.no-ip.org"
Trying to connect to news-read2.maxwell.syr.edu:nntp ... connected.
Using STAT <message-ID> command on this server.
Not posting to news-read2.maxwell.syr.edu: non-permission
Getting new newsgroups from news-read2.maxwell.syr.edu
Reading server info from /var/spool/news/leaf.node/news-read2.maxwell.syr.edu
Disconnected from news-read2.maxwell.syr.edu.
WARNING: found no server with posting permission!
wrote active file with 25858 lines
Started process to update overview data in the background.
Network activity has finished.

$ NNTPSERVER=localhost slrn -f ~/.jnewsrc --create
slrn 0.9.8.0 [2003-08-25]
 
Reading startup file /home/romildo/.slrnrc.
Using newsrc file /home/romildo/.jnewsrc for server localhost.
Connecting to host localhost ...
Failed to initialize server
Reason:
slrn fatal error:
Failed to initialize server.

Any help?

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

### A server list can be found at http://www.newzbot.com/

#server = nntp.sourceforge.net		#
#port = 563
#username = romildo
#password = 1995ana

#server = news.freshmeat.net
#username = romildo
#password = 1995ana

# Server				Rating	Allows	Speed	Average	Groups
#						Posting	kb/sec	Article
#								Retent.

#server = news.vmware.com
#server = news.uol.com.br
#server = news.terra.com.br
#server = news.abusar.org
#
#server = sunsite.dk			# Bett	?	15.40	  361	  483
server = news-read2.maxwell.syr.edu	# Good	No	13.67	  631	25876
#server = msnews.microsoft.com		# Good	Yes	39.28	  908	 2287
#server = sea.gmane.org			# So-so	?	15.33	 2509	 4289
#server = fb1.euro.net			# Good	No	10.75 	  760	  447

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

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

## Important and recommended setting:
## Fetch only a few articles when we subscribe a new newsgroup. The
## default is to fetch all articles.
## As leafnode forgets the article numbers of its upstream server when
## a group is marked as uninteresting, and later marked interesting
## again, you may end up downloading ALL articles from the upstream 
## in that group. So uncomment and adjust this line:
# initialfetch = 100

## Debugging setting:
## the higher, the more output will be logged.
## Make sure you've also read the TROUBLESHOOTING section in README.
## Leave at 0 for regular use, 1, 2 or 3 are good for debugging.
# debugmode = 3
debugmode = 1

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

## By default, leafnode only serves connections from addresses in the
## local networks and drops those from outside. An IPv4 address is
## considered local if it is within the networks (IP/netmask) of the local
## interfaces. An IPv6 address is considered local if it is site-local,
## link-local or the loopback address (::1).
##
## You can enable remote access by doing:
## 1. enabling access for single static IPs (or subnetworks) through
##    your super server (xinetd, tcpserver) or, if the service is wrapped by
##    tcpd, hosts.allow/hosts.deny configuration,
## 2. disabling access for all other hosts (default to deny),
## 3. testing that "deny" works, to avoid abuse of your server,
## 4. uncommenting this option, capitalizing the "strangers" subword and
##    setting the value to 42.
##
## WARNING: ENABLING THIS OPTION IS DANGEROUS. YOU AGREE TO BE LIABLE
## FOR ALL ABUSE OF YOUR SERVER WHEN THIS OPTION IS ENABLED.
## IF ANYTHING ABOUT ITEMS 1. TO 3. ABOVE IS UNCLEAR, DO NOT ENABLE THIS!
## IF YOU ARE NOT FAMILIAR WITH ACCESS CONTROL, OR YOUR CLIENTS ARE ON
## DYNAMIC IPS, YOU MUST NOT ENABLE THIS. (You can use other, authenticated,
## methods of access instead, for instance SSH tunnels.)
##
# allowstrangers = 0

## Standard news servers run on port 119, reserved for NNTP, so that's
## the default port fetchnews wants to connect to. If your ISP's news
## server (or other "upstream") does not listen on this standard port,
## you can set the "port" option. Note that it is only relevant for
## fetchnews, for leafnode, set the port in your inetd.conf, xinetd.conf
## file or tcpsvd/tcpserver command line, whatever is relevant for your
## system. Leafnode does not currently support SSL.
## Give "port" a numeric value, example:
# port = 9119

## If you want to guarantee that the stdout/stderr are line buffered
## (GNU libc sets them to full buffering if they are redirected to
## files), then set this:
# linebuffer = 1

## 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 = sex.and.warez.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

## Disable the updating of the active file unless specifically requested
## in order to minimise network usage as much as possible.  The active
## file can be updated manually with the "-f" option to fetchnews.
# server = even.slower
# noactive = 1

## And this is a news server you only want to pull news from, but never
## post to. You can also use this as a workaround if you do not have posting
## permission on the server while it still greets you with a 200 code.
## The default is: nopost = 0
# server = lurk-only.example.com
# nopost = 1

## And this is a news server you only want to post to, but never
## fetch messages from. If set, noactive = 1 is also assumed.
## The default is: noread = 0
# server = post-only.example.com
# noread = 1

## And this is a news server with broken XOVER. Forbid XOVER,
## leafnode will use XHDR. XHDR may be slower or faster than XOVER,
## depending how many of the maxlines/minlines, maxbytes, maxage
## and similar options.
## The default is: noxover = 0
# server = post-only.example.com
# noxover = 1

## The post_anygroup parameter affects posting and makes leafnode skip
## the check if the newsgroup is carried by the respective server.
## Use this on servers that allow only posting, but no "GROUP" commands.
## Note: do not enable unless you know you may post to that server, your
## postings might end up in the failed.postings directory otherwise.
# server = post-only.example.com
# post_anygroup = 1

## This shows how a server is configured that only has specific news
## groups. Note that this parameter is a PCRE, not a wildmat! See
## pcre(3) or pcre(7), depending on your PCRE version.
# server = cnews.corel.com
# only_groups_pcre = corel\.

## Non-standard expire times (glob(7) wildcard constructs possible)
#
# groups too big to hold articles 20 days:
# groupexpire comp.os.linux.* = 5
#
# very interesting, hold articles longer:
# groupexpire any.local.newsgroup = 100
# 
# archive this group (fetchnews uses the global expire to figure the
# maxage, but texpire will skip it):
# groupexpire my.archived.group = -1

groupexpire comp.lang.functional = 360
groupexpire comp.lang.ml = 360
groupexpire comp.lang.scheme = 360
groupexpire comp.mail.* = 360
groupexpire comp.os.linux.hardware = 360
groupexpire comp.os.linux.help.hardware = 360
groupexpire comp.os.linux.x = 180
groupexpire comp.text.tex = 80
groupexpire gnu.emacs.gnus = 180
groupexpire alt.comp.periphs.mainboard.soyo = 180
groupexpire alt.test = 7
groupexpire fm.articles = 360

## 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 = 2000

## 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

## If you have configured delaybody mode and your newsreader doesn't
## cope with articles changing their numbers but not their Message-ID
## such as Knode, then try setting this switch to 1, which
## will make fetchnews keep the article number.
## You'll have to switch the article body cache off though in your
## newsreader.
# delaybody_in_situ = 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. A value of 0 indicates that
## no checking should be performed. The default maxage is 10 days.
## WARNING: maxage can be overridden by expire! See the clamp_maxage
## parameter below.
#maxage = 10
maxage = 270

## By default, maxage is limited to groupexpire (if applicable) or
## expire (otherwise). On some rare occasions, this limit may be
## undesirable. To avoid this maxage manipulation, uncomment this line:
# clamp_maxage = 0

## 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_long = 28

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

## timeout_client determines how many seconds of inactivity to allow before
## a client is forcibly disconnected. The default is 15 mins (900s). Optional.
# timeout_client = 900

## 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 = /etc/leafnode/filters

## Note that filtering usually means HEAD and BODY are downloaded
## separately, so fetchnews has to wait for the packets TWICE to travel
## to the server and back. If you have a fast link with high latencies
## (for example a DSL line with interleaving or a satellite link), it
## may be faster to request header and body in a single command and
## discard the body. Note that the filter applies to the header only in
## either case because PCRE matching is expensive.
##
## If you have one of the high-latency high-throughput links and have
## enough free traffic left or a flat rate (no per-MByte billing), uncomment
## this:
# article_despite_filter = 1

## 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 = myhost.example.org
#hostname = uber.com.br

## You can also override the From: header address shown in placeholder
## articles. It should be the news administrator's mail address.
# newsadmin = postmaster@xxxxxxxxxxxxxxxxxxx

## If in your local Usenet hierarchy, posting unencoded 8-bit data in
## headers is condoned, uncomment this option to allow this. 8-bit data
## in headers is officially illegal, although the header character set
## may change to UTF-8 soon.
# allow_8bit_headers = 1
# Sample configuration file for xinetd

defaults
{
	only_from      = 127.0.0.1 localhost gentoo.malaquias.no-ip.org
	instances      = 60
	log_type       = SYSLOG authpriv info
	log_on_success = HOST PID
	log_on_failure = HOST
	cps            = 25 30
}

includedir /etc/xinetd.d
# default: off
# description: Leafnode - accepts connections on port 119 (NNTP)

service nntp
{
	socket_type = stream
	protocol    = tcp
	wait        = no
	user        = news
	server      = /usr/sbin/leafnode
	disable     = no
}
-- 
_______________________________________________
leafnode-list mailing list
leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
http://www.dt.e-technik.uni-dortmund.de/mailman/listinfo/leafnode-list
http://leafnode.sourceforge.net/