Still more newbie stuff

[TerryK]

I got the changer mechanism working. Now I get the following from amcheck daily1:

(brought to you by Amanda 2.5.1p3)
-bash-3.00$ strace -f -F -x -oam5.trc amcheck daily1
Amanda Tape Server Host Check
-----------------------------
Holding disk /image2/amandahold/daily1: 629838496 KB disk space available, using 628789920 KB
slot 5: read label `daily-005', date `X'
NOTE: skipping tape-writable test
Tape daily-005 label ok
Server check took 0.975 seconds

Amanda Backup Client Hosts Check
--------------------------------
WARNING: hubble.hq.aldon.com: selfcheck request failed: unable to bind to a reserved port (got port 32782)
Client check: 1 host checked in 11.780 seconds, 1 problem found

-bash-3.00$


I did a strace of the command and found many sequences like the following. The sin_port value increments by one for each repeat.


1269 5825 write(10, "amcheck-clients: time 0.001: bin"..., 75) = 75
1270 5825 bind(4, {sa_family=AF_INET, sin_port=htons(604), sin_addr=inet_addr("0.0.0.0")}, 16) = -1 EACCES (Permission denied)
1271 5825 write(10, "Permission denied\n", 18) = 18

[TerryK]

I was attempting to backup the Amanda Tape server.
In the disklist file, I selected a 'new' dumptype of comp-root-gnutar. Which was just a root-gnutar with compression turned on.

In the /etc/xinetd.d/amanda and amanda-client I had selected socket_type = stream and protocol = tcp

I noticed in the strace output that amcheck was attempting to use udp datagrams rather than tcp.

After adding
auth "bsdtcp"
to the amanda.conf dumptype, I was able to get a successful amcheck and backup.

I must admit that I 'stumbled' across this resolution. However, it appears to me that the dumptype in the amanda config file must agree with the socket-type and protocol entries in xinetd.d.

All of this may seem obvious to everyone else, but I couldn't find anything in the documentation that pointed me in that direction. In fact, in the example amanda.conf file, bsdtcp isn't identified as a valid value for the auth option. When I made the change it was one of those 'last straw', 'lets see if this works' kind of deals.

Bottom line... I am thrilled to have the initial backup test working. Now I just need to get the entire strategy implemented...