On 05/25/2012 02:02 PM, Brian Cuttler wrote:
On Fri, May 25, 2012 at 01:06:45PM -0400, Brian Cuttler wrote:
Charles,
Jean-Louis,
I did include the amgetconf reserved-tcp-port info in my email,
I get the same results you do.
I am logged in as root when running amcheck.
I was afraid that was an IPv6 error, was running it out of the
box and didn't expect it to be turned on.
How do I turn off IPv6?
Out of the box xinetd's config is
~
# default: off
# description: Amanda backup client
#
service amanda
{
socket_type = dgram
protocol = udp
wait = no
user = amanda
group = amanda
server = /usr/lib/amanda/amandad
disable = no
server_args = -auth=bsdudp amdump
}
This is a config for bsdudp auth.
Either fix xinetd for bsdtcp or use bsdudp.
Fri May 25 13:57:44 2012: amcheck-clients: connect_portrange: Connect from
0.0.0.0:585 failed: Connection refused
Fri May 25 13:57:44 2012: amcheck-clients: connect_portrange: connect to
172.16.1.34:10080 failed: Connection refused
Fri May 25 13:57:44 2012: amcheck-clients: stream_client: Could not bind to
port in range 512-1023.
Fri May 25 13:57:44 2012: amcheck-clients:
security_seterror(handle=0x7f30710cd4e0, driver=0x7f30709f7860 (BSDTCP)
error=Connection refused)
Fri May 25 13:57:44 2012: amcheck-clients:
security_close(handle=0x7f30710cd4e0, driver=0x7f30709f7860 (BSDTCP))
Fri May 25 13:57:44 2012: amcheck-clients: security_stream_close(0x7f30710b69d0)
But you are using bsdtcp
Either fix xinetd for bsdtcp or use bsdudp.
bsdtcp is the preferred choice.
Jean-Louis
