> On Dec 14, 2016, at 6:04 PM, Gene Heskett <ghesk...@shentel.net> wrote: > > On Wednesday 14 December 2016 18:25:23 Debra S Baddorf wrote: > >>> On Dec 14, 2016, at 4:51 PM, Gene Heskett <ghesk...@shentel.net> >>> wrote: >>> >>> Greetings all; >>> >>> I added another machine machine to my disklist about a month back, >>> and now I need to do a full recovery just to see if I've blown a pin >>> on its gpio. >>> >>> The machine is a raspberrypi 3b. >>> >>> But even though I have added it to the only_from line in >>> the /etc/xinetd.d/amanda file, and restarted xinetd, and verified >>> that all the server_args=bsdtcp, this machine is still rejecting the >>> connection from amrecover on the pi: >>> >>> pi@raspberrypi:/ $ sudo amrecover -s coyote.coyote.den -t >>> coyote.coyote.den -d /amandatapes -C Daily >>> AMRECOVER Version 3.3.6. Contacting server on coyote.coyote.den ... >>> [request failed: EOF on read from coyote.coyote.den] >>> >>> What does this tell me I need to do next? >>> >>> Thank you all. >>> >>> Cheers, Gene Heskett >>> -- >>> "There are four boxes to be used in defense of liberty: >>> soap, ballot, jury, and ammo. Please use in that order." >>> -Ed Howdershelt (Author) >>> Genes Web page <http://geneslinuxbox.net:6309/gene> >> >> For an easy starter question: does your server (coyote, I take it?) >> include the PI node’s name in the .amandahosts file? (And >> .k5amandahosts, but I doubt if you use kerberos). >> >> Sample client line: >> .amandahosts:PI.my.domain root amindexd amidxtaped > > Now I am between 2 other rocks > pi@raspberrypi:~ $ sudo amrecover -s coyote.coyote.den -t > coyote.coyote.den -C Daily > AMRECOVER Version 3.3.6. Contacting server on coyote.coyote.den ... > NAK: user root from raspberrypi.coyote.den is not allowed to execute the > service amindexd: Please add the line "raspberrypi.coyote.den root > amindexd amidxtaped" to /home/amanda/.amandahosts on the server > pi@raspberrypi:~
Well, this one is what we just did. However, the file is rather picky about its permissions: (operator is my backup account). Oh, and make sure the line reads exactly as requested, above. -rw------- 1 operator root 2875 Aug 29 14:09 .amandahosts > $ amrecover -s coyote.coyote.den -t coyote.coyote.den -C > Daily > amrecover: critical (fatal): create debug > directory "/var/log/amanda/client/": Permission denied > amrecover: create debug directory "/var/log/amanda/client/": Permission > denied > > but the directory exists, with these permissions: > pi@raspberrypi:/var/log $ sudo ls -l amanda > total 8 > drwx------ 2 backup backup 4096 Dec 14 03:03 amandad > drwx------ 3 backup backup 4096 Dec 14 18:50 client > Those perms don't look kosher, but thats what installing amanda-common > and amanda-client left me with. > I gather these are where your logs are supposed to go? (the default value is /tmp/amanda, I think) My permissions are, where OPERATOR is my backup account. drwxr-xr-x. 7 operator root 4096 Dec 14 07:00 amanda What’s the permission on your “/var/log” itself ? If you don’t want *IT* to be owned by “backup” you may need to specify a directory under it. /var/log/amanda perhaps. Though, if your backups are currently working, it’s probably okay. It’s just the recover that isn’t going, right now. directories under that are created at need, i think, and come up with drwx------ 2 operator root 4096 Dec 14 17:30 amandad drwx------ 5 operator root 4096 Dec 14 17:30 client drwx------ 2 operator root 4096 Dec 14 04:47 log.error drwx------ 5 operator root 4096 Dec 14 17:30 server (you won’t get all until needed) Those match yours. So, maybe I haven’t added anything new? Or did this prompt a change, above? Deb > Next? > > Thanks Deb. > > Cheers, Gene Heskett > -- > "There are four boxes to be used in defense of liberty: > soap, ballot, jury, and ammo. Please use in that order." > -Ed Howdershelt (Author) > Genes Web page <http://geneslinuxbox.net:6309/gene> >