On Sunday 05 March 2017 00:33:28 Jon LaBadie wrote: > Anyone ever seen a "Amanda Busy" message before? > > Got a little further with amdump_client. Now the > two remote clients (Fedora 24&25, Fedora binaries 3.4.2) > are connecting to the server (CentOS7.3, Zmanda binaries > 3.4.2). Of the three amdump_client commands, "list" is > working but "check" and "dump" are giving the message > "Busy, Amanda is busy, try again later". > > There are no amanda processes running, neither on the > server nor either of the clients. > > jl
3.4.2 is buggy, and will reuse the most recent tape. And an attempt to build 3.4.3 after the announcement of the bug fixed release blew completely up in my face here, so I had to rebuild from the tarball, 3.3.7p1, which I'd been running for 2 or 3 years, and everything is back to mostly normal here. I posted about it, but no reply's have been forthcoming in 2 days. Usually, my bug reports have been welcomed. Not this time. The setup instructions on this new amanda-security.conf file call for it to be owned by root, rw, and readable by everyone else, or chmod 0644, then an attempted backup bails out on every local entry in the disklist complaining that the file is group writeable when it is not, only the owner, root can write according to the perms. So either my whole filesystem is screwed, or the new amanda is not yet ready for prime time. And my whole filesystem, wheezy all up to date, seems to be working just fine. The weird part is that it backed up every other machine on my local network just fine, no complaints. WTH? 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>
