From: Freeballer on
I just installed arch a bit ago on a spare computer, it all works great.
But I can't get leafnode working. I am using a howto from ubuntu since
arch site has no information. Installation and config seem to work, and
the daemon starts fine. Logs show it connects to my newsserver but
telnet'ing from localhost -- or slrn will not connect. Says "connection
refused"

I can "show my work" but I wanted to shorten the post. If you want/need
that info I'd be more than happy to post.

here's the guide I followed: http://ubuntuforums.org/showthread.php?t=676837

I installed using yaourt
I do not have my firewall running
hosts.allow/deny have been disabled in case.

leafnode has been configured with user/pass, server address and port.

if I type "leafnode" I get this:

//
200 Leafnode NNTP Daemon, version 1.11.7 running at [dns] (my fqdn: [dns])
//

I found a News.log file in /var/log/ and it says connected to newsgroup
server with user/pass, no posts sent. If I do a fetchnews I get new
articles in /var/spool/news/ So I do NOT think its the server config but
if I do a telnet it says:


//
[root(a)Desktop log]# telnet localhost 119
Trying 127.0.0.1...
telnet: Unable to connect to remote host: Connection refused
//

Anybody have any ideas? I'd appreciate any help, I'll try any ideas and
if you need some more info or output let me know. And maybee I'm
overlooking something simple. :/

Thanks
Geo

--
"'Bill Gates can't guarantee Windows, so how in the HELL can you
guarantee our safety!' --John Crichton (Farscape)"
From: andrew on
On 2009-11-30, Freeballer <freeballer(a)nospam.invalid> wrote:

> here's the guide I followed:
> http://ubuntuforums.org/showthread.php?t=676837

A fine guide that one, although I will have to say that it is a guide I
wrote myself :).

> I installed using yaourt
> I do not have my firewall running
> hosts.allow/deny have been disabled in case.

I am not familiar with Arch, and most certainly not with yaourt, but
unless things are radically different you will need to place Leafnode in
both of these files as described in the guide to allow access to INET
services.

> if I type "leafnode" I get this:
>
> //
> 200 Leafnode NNTP Daemon, version 1.11.7 running at [dns] (my fqdn: [dns])
> //

Hmmm.... the guide is actually aimed at Leafnode _2_ rather than
Leafnode 1...

> [root(a)Desktop log]# telnet localhost 119
> Trying 127.0.0.1...
> telnet: Unable to connect to remote host: Connection refused
> //

This is the heart of the problem and I suspect relates to an inetd
issue, possibly simply the hosts.deny and hosts.allow issue mentioned
previously. Are you running the openbsd inetd? If you are running xinetd
the setup will be a little different.

Andrew

--
Do you think that's air you're breathing?
From: Freeballer on
andrew wrote:
> On 2009-11-30, Freeballer <freeballer(a)nospam.invalid> wrote:
>
>> here's the guide I followed:
>> http://ubuntuforums.org/showthread.php?t=676837
>
> A fine guide that one, although I will have to say that it is a guide I
> wrote myself :).
>

haha nice! it was the best one I could find to be honest, glad I got in
touch with someone who definitely knows his sh-t

>> I installed using yaourt
>> I do not have my firewall running
>> hosts.allow/deny have been disabled in case.
>
> I am not familiar with Arch, and most certainly not with yaourt, but
> unless things are radically different you will need to place Leafnode in
> both of these files as described in the guide to allow access to INET
> services.
>

Yaourt is like an addon to deb/apt, it gives you the ability to compile
a package for arch and install regularly using sources.

>> if I type "leafnode" I get this:
>>
>> //
>> 200 Leafnode NNTP Daemon, version 1.11.7 running at [dns] (my fqdn: [dns])
>> //
>
> Hmmm.... the guide is actually aimed at Leafnode _2_ rather than
> Leafnode 1...

Is leafnode 2 not in development? I mean that doesn't necessarily mean
its bad but its not available in the normal arch repos

>
>> [root(a)Desktop log]# telnet localhost 119
>> Trying 127.0.0.1...
>> telnet: Unable to connect to remote host: Connection refused
>> //
>
> This is the heart of the problem and I suspect relates to an inetd
> issue, possibly simply the hosts.deny and hosts.allow issue mentioned
> previously. Are you running the openbsd inetd? If you are running xinetd
> the setup will be a little different.
>

Well. It IS "xinetd v2.3.14-5" so I'm guessing the setup is the problem
then. I was fairly sure allow/deny was ok, I used exactly what was shown
and other services work.

> Andrew
>


--
"'Bill Gates can't guarantee Windows, so how in the HELL can you
guarantee our safety!' --John Crichton (Farscape)"
From: Freeballer on
Freeballer wrote:
> andrew wrote:
>> On 2009-11-30, Freeballer <freeballer(a)nospam.invalid> wrote:
>>
>>> here's the guide I followed:
>>> http://ubuntuforums.org/showthread.php?t=676837
>>
>> A fine guide that one, although I will have to say that it is a guide I
>> wrote myself :).
>>
>
> haha nice! it was the best one I could find to be honest, glad I got in
> touch with someone who definitely knows his sh-t
>
>>> I installed using yaourt
>>> I do not have my firewall running
>>> hosts.allow/deny have been disabled in case.
>>
>> I am not familiar with Arch, and most certainly not with yaourt, but
>> unless things are radically different you will need to place Leafnode in
>> both of these files as described in the guide to allow access to INET
>> services.
>>
>
> Yaourt is like an addon to deb/apt, it gives you the ability to compile
> a package for arch and install regularly using sources.
>
>>> if I type "leafnode" I get this:
>>>
>>> //
>>> 200 Leafnode NNTP Daemon, version 1.11.7 running at [dns] (my fqdn:
>>> [dns])
>>> //
>>
>> Hmmm.... the guide is actually aimed at Leafnode _2_ rather than
>> Leafnode 1...
>
> Is leafnode 2 not in development? I mean that doesn't necessarily mean
> its bad but its not available in the normal arch repos
>
>>
>>> [root(a)Desktop log]# telnet localhost 119
>>> Trying 127.0.0.1...
>>> telnet: Unable to connect to remote host: Connection refused
>>> //
>>
>> This is the heart of the problem and I suspect relates to an inetd
>> issue, possibly simply the hosts.deny and hosts.allow issue mentioned
>> previously. Are you running the openbsd inetd? If you are running xinetd
>> the setup will be a little different.
>>
>
> Well. It IS "xinetd v2.3.14-5" so I'm guessing the setup is the problem
> then. I was fairly sure allow/deny was ok, I used exactly what was shown
> and other services work.
>
>> Andrew
>>
>
>



Hi, sorry to be impatient. But its close to bedtime here (3am). I went
to their site, and read the install. I have put

//
b. After you have figured which of the two files to edit (or
create), add
this to the xinetd configuration file:

service nntp
{
flags = NAMEINARGS NOLIBWRAP
socket_type = stream
protocol = tcp
wait = no
user = news
server = /usr/sbin/tcpd
server_args = /usr/local/sbin/leafnode
instances = 7
per_source = 3
}

//

as per guide. I stopped xinetd and started again. I get the same msg
about the daemon running but when I telnet into it I get

//

[freeballer(a)Desktop ~]$ telnet localhost 119
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
Connection closed by foreign host.
[freeballer(a)Desktop ~]$

//

I'm going to go back tomorrow and remove everything from
hosts.deny/allow and see if that helps but any output on method so far
or information that may be useful is always welcome

thanks for replying btw :)
freeballer

--
"'Bill Gates can't guarantee Windows, so how in the HELL can you
guarantee our safety!' --John Crichton (Farscape)"
From: andrew on
On 2009-11-30, Freeballer <freeballer(a)nospam.invalid> wrote:

> Is leafnode 2 not in development? I mean that doesn't necessarily mean
> its bad but its not available in the normal arch repos

Leafnode 2 has been 'in development' for many years but in my experience
the final release of 2008 has been quite stable.

> Well. It IS "xinetd v2.3.14-5" so I'm guessing the setup is the problem
> then. I was fairly sure allow/deny was ok, I used exactly what was shown
> and other services work.

I have not used xinetd but the documentation in the Leafnode 2 tarball
has a few words:

#v+
+ Alternative #2: If your system has xinetd instead. Add this to
your xinetd.conf (this example assumes xinetd 2.3.3 or newer):

service nntp
{
flags = NAMEINARGS NOLIBWRAP
socket_type = stream
protocol = tcp
wait = no
user = news
server = /usr/sbin/tcpd
server_args = /usr/local/sbin/leafnode
instances = 7
per_source = 3
}

Then send xinetd an USR2 signal to make it reread its
configuration. See the xinetd.conf(5) manual page for details.
Note: some systems install tcpd to a different path, but it's
uncommon. Change the first path accordingly if your tcpd
resides in /usr/etc or /usr/lbin.
#v-

But I have no experience with xinetd unfortunately :(. Mind you if this
does not get your server running the best place to direct queries about
Leafnode is actually news.software.readers.

All the best,

Andrew

--
Do you think that's air you're breathing?
 |  Next  |  Last
Pages: 1 2 3
Prev: Nvidia help pls ...
Next: FC12 and kde