Amanda has been happily backing up a half dozen Linux machines for a week now and I can even restore files using amrecover on the server. That part was easy.
Using the instructions I found on zmanda wiki -- with appropriate adjustments for my environment -- I tried to get amrecover over ssh working on the clients with no success. I created a key pair on the client. I added the public key of the above pair to /var/amanda/.ssh/authorized_keys on the server As a test, I can log onto the server from the client as amandabackup: $ ssh -i /var/amanda/.ssh/amrecover_key scadev02.lereta.com and as root: $ sudo ssh -i /var/amanda/.ssh/amrecover_key amandabac...@scadev02.lereta.com but running amrecover as root I get a "Host key verification failed": $ sudo amrecover Host key verification failed. AMRECOVER Version 2.6.1p2. Contacting server on scadev02.lereta.com ... [request failed: EOF on read from scadev02.lereta.net] Just to be certain this is not just an incompatibility between 2.6.1 (on client) and 3.3.6 (on the server), I tried the same steps on a machine running client version 3.3.6 with the same results. $ sudo amrecover Host key verification failed. AMRECOVER Version 3.3.6. Contacting server on scadev02.lereta.com ... [request failed: EOF on read from scadev02.lereta.net] Server version: 3.3.6 Client version: 2.6.1p2 /etc/amanda/amanda-client.conf conf "lereta" index_server "scadev02.lereta.com" tape_server "scadev02.lereta.com" tapedev "" auth "ssh" ssh_keys "/var/amanda/.ssh/amrecover_key" client_username "amandabackup" (I also noticed that the underscore was replaced by a dash between 2.6.1 and 3.3.6) /var/log/amanda/client/amrecover.20150116145809.debug contains: 1421449089.660567: amrecover: pid 7195 ruid 0 euid 0 version 2.6.1p2: start at Fri Jan 16 14:58:09 2015 1421449089.661031: amrecover: pid 7195 ruid 0 euid 0 version 2.6.1p2: rename at Fri Jan 16 14:58:09 2015 1421449089.661075: amrecover: security_getdriver(name=ssh) returns 0x7ff5c720f2e0 1421449089.661094: amrecover: security_handleinit(handle=0x7ff5c9929a30, driver=0x7ff5c720f2e0 (SSH)) 1421449089.661685: amrecover: security_streaminit(stream=0x7ff5c99315a0, driver=0x7ff5c720f2e0 (SSH)) 1421449089.719622: amrecover: security_stream_seterr(0x7ff5c99315a0, SOCKET_EOF) 1421449089.719657: amrecover: security_seterror(handle=0x7ff5c9929a30, driver=0x7ff5c720f2e0 (SSH) error=EOF on read from scadev02.lereta.net) 1421449089.719671: amrecover: security_close(handle=0x7ff5c9929a30, driver=0x7ff5c720f2e0 (SSH)) 1421449089.719677: amrecover: security_stream_close(0x7ff5c99315a0) I do not see what I am overlooking. It make no sense that I can connect as amandabackup but, assuming that amrecover connects as the user in client-username, amrecover cannot. Any suggestions as to where to go from here? +---------------------------------------------------------------------- |This was sent by a0180...@opayq.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +----------------------------------------------------------------------
