On Thu, Apr 05, 2012 at 23:01:57 -0400, gene heskett wrote:
> What would be the nmap invocation that would show if ports amanda needs are
> closed?
> Thu Apr 5 22:48:11 2012: thd-0x86ede00: amcheck-clients: connect_port: Try
> port 516: available - Success
> Thu Apr 5 22:48:11 2012: thd-0x86ede00: amcheck-clients: connected to
> 192.168.71.3:10080
> Thu Apr 5 22:48:11 2012: thd-0x86ede00: amcheck-clients: our side is
> 0.0.0.0:516
> Thu Apr 5 22:48:11 2012: thd-0x86ede00: amcheck-clients: connect_port: Try
> port 516: available - Success
> Thu Apr 5 22:48:11 2012: thd-0x86ede00: amcheck-clients: connect_portrange:
> Connect from 0.0.0.0:516 failed: Connection refused
> Thu Apr 5 22:48:11 2012: thd-0x86ede00: amcheck-clients: connect_portrange:
> connect to 192.168.71.4:10080 failed: Connection refused
> Thu Apr 5 22:48:11 2012: thd-0x86ede00: amcheck-clients: stream_client:
> Could not bind to port in range 512-1023.
> Thu Apr 5 22:48:11 2012: thd-0x86ede00: amcheck-clients: connect_port: Try
> port 516: available - Success
> Thu Apr 5 22:48:11 2012: thd-0x86ede00: amcheck-clients: connect_portrange:
> Connect from 0.0.0.0:516 failed: Connection refused
> Thu Apr 5 22:48:11 2012: thd-0x86ede00: amcheck-clients: connect_portrange:
> connect to 192.168.71.5:10080 failed: Connection refused
> Thu Apr 5 22:48:16 2012: thd-0x86ede00: amcheck-clients: connect_port: Try
> port 516: available - Success
> Thu Apr 5 22:48:16 2012: thd-0x86ede00: amcheck-clients: connect_portrange:
> Connect from 0.0.0.0:516 failed: Connection refused
> Thu Apr 5 22:48:16 2012: thd-0x86ede00: amcheck-clients: connect_portrange:
> connect to 192.168.71.4:10080 failed: Connection refused
> Thu Apr 5 22:48:16 2012: thd-0x86ede00: amcheck-clients: stream_client:
> Could not bind to port in range 512-1023.
> Thu Apr 5 22:48:16 2012: thd-0x86ede00: amcheck-clients: connect_port: Try
> port 516: available - Success
> Thu Apr 5 22:48:16 2012: thd-0x86ede00: amcheck-clients: connect_portrange:
> Connect from 0.0.0.0:516 failed: Connection refused
> Thu Apr 5 22:48:16 2012: thd-0x86ede00: amcheck-clients: connect_portrange:
> connect to 192.168.71.5:10080 failed: Connection refused
> Thu Apr 5 22:48:16 2012: thd-0x86ede00: amcheck-clients: stream_client:
> Could not bind to port in range 512-1023.
> Thu Apr 5 22:48:21 2012: thd-0x86ede00: amcheck-clients: connect_port: Try
> port 516: available - Success
> Thu Apr 5 22:48:21 2012: thd-0x86ede00: amcheck-clients: connect_portrange:
> Connect from 0.0.0.0:516 failed: Connection refused
> Thu Apr 5 22:48:21 2012: thd-0x86ede00: amcheck-clients: connect_portrange:
> connect to 192.168.71.4:10080 failed: Connection refused
> Thu Apr 5 22:48:21 2012: thd-0x86ede00: amcheck-clients: stream_client:
> Could not bind to port in range 512-1023.
> Thu Apr 5 22:48:21 2012: thd-0x86ede00: amcheck-clients: connect_port: Try
> port 516: available - Success
> Thu Apr 5 22:48:21 2012: thd-0x86ede00: amcheck-clients: connect_portrange:
> Connect from 0.0.0.0:516 failed: Connection refused
> Thu Apr 5 22:48:21 2012: thd-0x86ede00: amcheck-clients: connect_portrange:
> connect to 192.168.71.5:10080 failed: Connection refused
> Thu Apr 5 22:48:21 2012: thd-0x86ede00: amcheck-clients: stream_client:
> Could not bind to port in range 512-1023.
Assuming you don't have any firewalling going on between these machines,
you can most likely tell which ports Amanda has open on the clients by
just running
$ netstat -a | grep amanda
on those machines...
Does the output from that command on 192.168.71.3 look any different
from that on your other clients?
(As described in /etc/services, port 10080 is the "amanda" port for both
UDP and TCP.)
Nathan
----------------------------------------------------------------------------
Nathan Stratton Treadway - [email protected] - Mid-Atlantic region
Ray Ontko & Co. - Software consulting services - http://www.ontko.com/
GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt ID: 1023D/ECFB6239
Key fingerprint = 6AD8 485E 20B9 5C71 231C 0C32 15F3 ADCD ECFB 6239
