Hi,
we are really excited using amanda-3.5 because of the multithread patch.
Testing it there seems to be an issue:
If I run
for i in `amadmin mirror hosts`; do echo $i ;amcheck -c mirror $i;done
in amanda-3.3.9
* Two Clients have/'Connection timed out' (bla2,esx-237)
/
* /One Client has //'No route to host' (dl380-138)
/
The expected result would be that these three hosts are mentioned by
amcheck in 3.5, but no additional hosts.
Here is what amcheck in 3.5 says:
amanda@dl380-54:~$ amcheck -c mirror
'/usr/local/etc/amanda/mirror/amanda.conf', line 110: warning:
Keyword usetimestamps is deprecated.
Amanda Backup Client Hosts Check
--------------------------------
ERROR: gotdb7: selfcheck request failed: error sending REQ: write
error to: Broken pipe
ERROR: gotdb8: selfcheck request failed: error sending REQ: write
error to: Broken pipe
ERROR: gotdb9: selfcheck request failed: error sending REQ: write
error to: Broken pipe
ERROR: inets1: selfcheck request failed: error sending REQ: write
error to: Broken pipe
ERROR: inets2: selfcheck request failed: error sending REQ: write
error to: Broken pipe
ERROR: gotdb6: selfcheck request failed: EOF on read from gotdb6
ERROR: bla: selfcheck request failed: EOF on read from bla
ERROR: esx-180: selfcheck request failed: error sending REQ: write
error to: Broken pipe
ERROR: esx-162: selfcheck request failed: error sending REQ: write
error to: Broken pipe
ERROR: sf4200-88: selfcheck request failed: Can't bind a socket to
connect to sf4200-88
ERROR: dl380-138: selfcheck request failed: No route to host
ERROR: bla2: selfcheck request failed: Connection timed out
ERROR: esx-237: selfcheck request failed: Connection timed out
Client check: 244 hosts checked in 568.725 seconds. 13 problems found.
(brought to you by Amanda 3.5)
Do you have an idea why they fail? Do you need additional logs?
Regards,
Dennis
