Re: [leafnode-list] I can't get leafnod to run. Please help me!

[Nicolas <oxstone@xxxxxxx>]

Thanks a lot for your attention and your answer.

Le Jeudi 7 Novembre 2002 12:09, vous avez écrit :
> Nicolas <oxstone@xxxxxxx> writes:
> > I use leafnode 1.9.18 on Redhat (kernel 2.4.18-3)
>
> 1.9.18 is outdated, so after you've solved this particular problem, you
> should update.

Well, I'm not a programmer, and when I tried to compile the latest version of 
leafnode, I get an error which I did not understand. Unless the latest 
version solves bad problems which were present in old version, I think I'll 
continue to use this outdated version, which I installed using an RPM. I 
don't remember the error, sorry...

> 
> > I created a new /etc/xinetd.d/leafnode file. Here's what's inside:
> > service nntp
> > {
> >         disable = no
> >         flags           = REUSE
> >         socket_type     = stream
> >         wait            = no
> >         user            = news
> >         server          = /usr/sbin/leafnode
> >         log_on_failure  += USERID
> > }
>
> Please see http://www.leafnode.org/faq.html#3. Note inetd -d is not
> going to get any results, so skip that step, but you can run xinetd -d
> instead -- or try lsof -i:119 (on the server).

I'm using a recent version of Linux (Redhat 7.3 on the server) which uses 
xinetd instead of inetd. I added this /etc/xinetd.d/leafnode file following 
exactly what is indicated on some leafnode tutorials I found on the internet. 
I think this should be ok.

>
> > The firewalls settings seems ok (the gateway can serve nntp to my
> > client, and my client can be served nntp from the server)
>
> When reading the above URL, you will verify that. Don't use "telnet
> localhost 119", but "telnet 192.168.0.2 119" instead. Please run tcpdump
> on the server while doing that.

Unfortunately, telnet is completly disabled on the server. I can't use it. The 
only way I can use to connect to it is to use ssh...

>
> > When I try to get the newsgroups from my clients (I use KNode 0.7.1), the
> > following ERROR message appears:
> > "Impossible de se connecter: Opération maintenant en cours"
> > It's in French. It means:
> > "Impossible to connect: a process is running"
>
> The canonical translation is "connection refused: operation in
> progress." -- it corresponds to EINPROGRESS. Whatever KNode is trying to
> do there, it may be asynchronous I/O.

Mmmm... I think that's the thing we should investigate...

>
> > I noticed the following packet drop on my client (nothing on special on
> > the server):
> > Nov  7 02:53:08 Tower kernel: ABORTED IN=eth0 OUT= MAC=(blablabla)
> > SRC=192.168.0.1 DST=192.168.0.2 LEN=40 TOS=0x00 PREC=0x00 TTL=255
> > ID=0 DF PROTO=TCP SPT=8080 DPT=2396 SEQ=3476029895 ACK=0 WINDOW=0
> > RES=0x00 RST> URGP=0
>
> This is unrelated; neither SPT nor DPT are port 119.

You're right. I'm sorry about this bad copy/paste. Here's a right packet drop 
I get in /var/log/messages on the CLIENT:

Nov  7 13:09:46 Tower kernel: ABORTED IN=eth0 OUT= 
MAC=00:50:ba:33:a0:c0:00:40:f4:2d:66:e2:08:00 SRC=192.168.0.1 DST=192.168.0.2 
LEN=40 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=TCP SPT=119 DPT=1066 SEQ=0 
ACK=399830744 WINDOW=0 RES=0x00 ACK RST URGP=0

>
> > PS: sorry for my poor English. How's your French? =)
>
> Moins bon que votre anglais, certainnement. :-)
>
> Je ne parle pas le français très bien non plus (si vous auriez posé
> cette question il y a dix ans...), mais je peux le lire. Si vous avez
> besoin d'expliquer des choses en français, n'utilisez pas de la langage
> courante...
>
> Euhm, est-ce qu'on se tutoie sur des listes de diffusion ou dans le
> Usenet? Je ne suis pas sûr...
>
> Je conseille d'écrire en anglais tout de même.

Well, I think your French is much better than my English... That's quite 
impressive. Let's continue in English, even if we could use French, for 
sure!! =)

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