You can specify the amandad-path in the disklist, or better, in the
authorized_keys on the client.
Provide the client debug files.
Jean-Louis
On 08/07/2014 04:51 PM, Chris Hoogendyk wrote:
I've been having a bit of trouble adding a client today and just
wanted to get a reality check before I bang my head too much.
My new server with Amanda 3.3.6 is temporarily on a private address
inside our department NAT. I was just trying today to add a 2.5.3
client that is in another department on a public address. I can ssh to
it, and I am using auth=ssh. I've got the keys set up. One thing I
noticed is that the key was specifying /usr/local/libexec/amandad, but
the newer Amanda was calling for /usr/local/libexec/amanda/amandad. I
tried working around that by creating the directory on the client and
symlinking all the executables into the directory. After that, I at
least was getting debug files on the client (before it had been nothing).
Am I going to be able to get this working? Or is it an insurmountable
problem to be on a private address behind the NAT?
It seems from http://wiki.zmanda.com/man/amanda-compatibility.7.html
that the versions ought not to be an issue, but I don't know what
other things besides the amanda directory in libexec might be getting
tangled up between the older Amanda and the newest Amanda.
At the moment, I'm still getting "selfcheck request failed: EOF on read".
