Amanda Backup Permission denied (publickey,gssapi-with-mic,password). error
 

I can ssh from each server to the other. I have generated the keys and added them to the .ssh/authorized_keys file. I can log back and forth from the client to the server for Amanda Backup and vice versa. Every time I run the amcheck I get this:

amcheck mydb
Amanda Tape Server Host Check
-----------------------------
WARNING: holding disk /path/to/dumps/amanda: only 64876544 KB available (524288000 KB requested)
read label `daily_full_01-05', date `20100204200003'.
label "daily_full_01-05" doesn't match "^mydb_full-[0-9][0-9]*$".
(expecting a new tape)
WARNING: tapecycle (1) <= runspercycle (1).
Server check took 6.837 seconds
Permission denied (publickey,gssapi-with-mic,password).

Amanda Backup Client Hosts Check
--------------------------------
WARNING: mydb: selfcheck request failed: EOF on read from mydb
Client check: 1 host checked in 0.210 seconds. 1 problem found.

(brought to you by Amanda 2.6.1p1)

All I am trying to do is backup one server, one time. This is really frustrating. Any help is very appreciated.

You have several problems with your configuration that you'll need to work out. It's hard to tell where to start without more information, but http://wiki.zmanda.com/index.php/Quick_start is a good guide that you can walk through step by step and check your setup. You have at least 5 configuration errors to straighten out going off the error messages. Take them one at a time. From the quick start you can jump out to other pages in the wiki for more detail.

What version of Amanda on what OS? Did you install from a package or build from source? If you built from source, did you do the ./configure --with-auth=ssh? (the --help will tell you what that should be. I'm just going from memory.)

If you configured amanda with auth ssh (on both the server and the client), and you did an ssh from the server to the client to set known hosts, and you copied the pub key from the server to the client and put it in authorized keys, and you can ssh from server to client using that key, and you have your dump type from the disklist set up in amanda.conf with auth ssh and pointing at the key file, then that part should work. That's only one of the configuration issues though.

Another is that you labeled your tape or virtual tape with a different label than the label string in your amanda.conf. Your tape cycle needs to be greater than your runspercycle. And so on.

After you work through the quick start guid and straighten out as much as you can, let us know where you are and what the messages are at that point. If you get to a point where you have trouble figuring out what is happening, it often helps to look in /tmp/amanda for the debug logs. They give more detail on errors.

Here is the OS and Amanda version info:
Linux version 2.6.9-89.0.0.0.1.ELsmp (mockbuild@ca-build10.us.oracle.com) (gcc version 3.4.6 20060404 (Red Hat 3.4.6-11.0.1)) #1 SMP Tue May 19 05:31:20 EDT 2009
VERSION="Amanda-2.6.1p1"

I have several Amanda configurations successfully running right now. I have followed the Quick Start Guide and the 15 minute guide to get them set up. This is the first time I am trying to connect to a different server. The other configurations all use rsync to backup to the local drive and then run amanda on the same server.

I know I left the daily tape in the drive when I ran this. I am swapping it out for the full backup tape right now. The other thing that bugs me is when I go to the debug files, there is nothing for this configuration. I have debug files for my other configurations, but nothing for this one.

Here is the dump type I have defined:
define dumptype global {
comment "Global definitions"
# auth "bsdtcp"
auth "ssh"
client_username "amanda"
ssh_keys "/var/lib/amanda/.ssh/id_rsa_dump"
amandad_path "/usr/lib/amanda/"

}

What else can I show you?

Nikki

Here is the error message with the proper tape. I also am aware that I have less room that it is requesting. That is another issue we are working on. It is enough for the test I plan to run.

Amanda Tape Server Host Check
-----------------------------
WARNING: holding disk /path/to directory/dumps/amanda: only 37580800 KB available (524288000 KB requested)
read label `db_full-01', date `X'.
NOTE: skipping tape-writable test
Tape db_full-01 label ok
WARNING: tapecycle (1) <= runspercycle (1).
Server check took 0.068 seconds
Permission denied (publickey,gssapi-with-mic,password).

Amanda Backup Client Hosts Check
--------------------------------
WARNING: db: selfcheck request failed: EOF on read from db
Client check: 1 host checked in 0.196 seconds. 1 problem found.

Well, I have resolved my problem. I could not get ssh to work. Yum installs an old version of Amanda Backup on the client that does not have bsdtcp on it. I uninstalled the old version and reinstalled the latest version of Amanda Backup (2.6.1p2) Then I followed the 15 minute guide and had it up and working in a matter of minutes. I would still be interested in knowing what caused that error, but for now, I'm moving again.

Nikki

Glad to hear you got it worked out. It takes too long to get new versions into various distribution's package management schemes. On my Ubuntu systems, I don't use apt-get for critical packages - the Amanda version was older than what I had installed on my Solaris systems more than 2 years ago. I install them from source and make sure the source matches across my systems. Somewhere within the early 2.5 versions, there may have been an incompatibility compared to the 2.6 versions with respect to the authentication you were trying to do, but I'd have to refer to the Amanda developers to fact check that.

I had the same problem and could not find the solution in the forum, so I am posting to this old post. If you can ssh as amandabackup without a password to the client then ssh is setup correctly, but my problem was that I did not have my ssh_keys setting in amanda.conf pointing to the private key.