Re: found initial debian setup instructs
Christoph Scheeder <[email protected]> Mon, 11 Aug 2025 16:32:08 +0200
| Newsgroups | gmane.comp.archivers.amanda.user |
|---|---|
| Message-ID | <[email protected]> |
Hi Gene, first please apologize im not an native amarican speaker, so my english may be odd at some points. i use amanda at two sites with vtape-setups, so lets see if we can fix your problems. 1.) what i found when amcheck complained about files/dirs not existing was i had typos in the config-file or the directorynames on the filesystem, so tripple-check the paths in amanda.conf and on disk match. (i never get that right at the first step.) same for permisions. just set it to the expected values, even if they seem to be correct. 2.) as for /var/backups/.ssh/id_rsa_amanda : two possible solutions: a) simplest solution: switch off the usage of ssh in amanda. as long as you trust your network you don't need that extra-security. on the amanda-server and every client edit /etc/xinetd.d/amanda und replace the line containing "server_args" with server_args = -auth=bsdtcp amdump amindexd amidxtaped senddiscover then create the file /var/backups/.amandahosts with lines like amanda.coyote.den backup amdump amindexd amidxtaped this allows the server to connet to the clients. b) (caveat: i never did it thisway, so my description my be falty) create ssh-identitys on every involved host and distribute the public-key of the server to all the clients: this is complex and described in detail at "https://wiki.zmanda.com/index.php/How_To:Set_up_transport_encryption_with_SSH" 3.) as user backup "mkdir /buildbot/amanda/AMdb/DailySet1/curinfo" that should fix most of your problems, give it a try and come back with whats remaining. ;-) hope it helps Christoph Am 11.08.2025 um 01:04 schrieb gene heskett: > On 8/10/25 14:47, gene heskett wrote: > su backup, ram >>> backup@amanda:/etc/amanda/DailySet1$ amcheck DailySet1 >>> Amanda Tape Server Host Check > ----------------------------- > NOTE: tapelist file does not exists > it will be created on the next run > NOTE: Holding disk '/hold/DailySet1/': 767950848 KB disk space available, using 767848448 KB > Warning: Identity file /var/backups/.ssh/id_rsa_amanda not accessible: No such file or directory. > Host key verification failed. > ERROR: directory '/raid/DailySet1' does not exist > ERROR: conf info dir '/buildbot/amanda/AMdb/DailySet1/curinfo' (Permission denied) > ERROR: index dir '/buildbot/amanda/DailySet1/AMdb' (Permission denied) > Server check took 0.830 seconds > Amanda Backup Client Hosts Check > -------------------------------- > ERROR: amanda.coyote.den: selfcheck request failed: error sending REQ: write error to: Broken pipe > Client check: 1 host checked in 1.062 seconds. 1 problem found. > (brought to you by Amanda 3.5.1) > > That is actually 3 ERROR's & 1 WARNING > The first one above points at the /raid/Dailyset1, and has 40660 perms from the /, owned by backup:backup. > The second also exists and is owned by backup;backup from the root, but curinfo does not yet exist > Same thing with the 3rd error, 40660 perms all the way to it and owned by backup:backup all he way. > > What am I doing wrong? And what does it need to satisfy the .ssh warning, that file and its parent dir does not exist. > > Nothing above is telling me what I need to do next. > > Thank you. > > Cheers, Gene Heskett, CET. >