I’m at v3.3.3 on my server and have a couple of clients at 2.5.0p2. They work fine, with auth=bsd. I haven’t tried auth=ssh. Deb Baddorf
On Aug 7, 2014, at 3:51 PM, Chris Hoogendyk <[email protected]> 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". > > -- > --------------- > > Chris Hoogendyk > > - > O__ ---- Systems Administrator > c/ /'_ --- Biology & Geology Departments > (*) \(*) -- 347 Morrill Science Center > ~~~~~~~~~~ - University of Massachusetts, Amherst > > <[email protected]> > > --------------- > > Erdös 4 >
smime.p7s
Description: S/MIME cryptographic signature
