[prev in list] [next in list] [prev in thread] [next in thread] 

List:       amd-dev
Subject:    Re: amq: localhost: RPC: Authentication error
From:       Ion Badulescu <ionut () badula ! org>
Date:       2003-11-07 14:15:50
[Download RAW message or body]

On Fri, 7 Nov 2003, Ivan Teliatnikov wrote:

> Ion,
> 
> Thank you very much for quick reply. You are right, when I comment out
> ALL: ALL in /etc/hosts.deny, things are working again. Below is copy of my
> hosts.allow. I would appreciate if you could have a look, I think it
> contains everything amd needs to work properly. I must be wrong.
> 
> Machine is configured with dhcp and has an ip address from the range 
> below. DNS is configured correctly. Machine is listed in /etc/hosts. NFS 
> server and clients are working.
> 
> rquotad: 129.78.124.0/255.255.254.0 129.78.236.0/255.255.255.0
> mountd:  129.78.124.0/255.255.254.0 129.78.236.0/255.255.255.0
> statd:   129.78.124.0/255.255.254.0 129.78.236.0/255.255.255.0
> nfsd:    129.78.124.0/255.255.254.0 129.78.236.0/255.255.255.0
> lockd:   129.78.124.0/255.255.254.0 129.78.236.0/255.255.255.0
> portmap: 129.78.124.0/255.255.254.0 129.78.236.0/255.255.255.0 

Amd recently became tcpwrappers-aware, so it will shield its own amq 
service according to restrictions in hosts.{allow,deny}. Its service name 
is "amd", and you need to open it to localhost at the very least, if you 
want to use amq.

This is documented (probably not prominently enough) in the manual, under 
the "use_tcpwrappers" amd.conf parameter.

Ion

-- 
  It is better to keep your mouth shut and be thought a fool,
            than to open it and remove all doubt.

_______________________________________________
amd-dev mailing list: amd-dev@cs.columbia.edu
Am-utils: http://www.am-utils.org
[prev in list] [next in list] [prev in thread] [next in thread]