amanda stopped working: selfcheck fails
Hi.
I run backups with Amanda every weekend and today it failed, completely.
What changes have happened, if any, were due to package upgrades, I
haven't touched amanda, ssh or inetd in a long while according to my
diary. Certainly not in the last week!
Amanda Tape Server Host Check
-----------------------------
Searching for label 'DailySet1-13':found in slot 13: volume 'DailySet1-13'
Will write to volume 'DailySet1-13' in slot 13.
NOTE: skipping tape-writable test
Server check took 0.300 seconds
Amanda Backup Client Hosts Check
--------------------------------
ERROR: mononoke: selfcheck request failed: Connection refused
ERROR: flyingraspi: selfcheck request failed: Connection refused
Client check: 3 hosts checked in 13.274 seconds. 2 problems found.
(brought to you by Amanda 3.5.1)
Setup:
* (debian testing) mononoke: runs the server and also is one of the
clients (bsdtcp)
* (debian testing) clarisse: client (ssh)
* (debian 9.11) flyingraspi: client (bsdtcp)
All three systems are freshly booted. Router has been rebooted, as well.
ping and ssh work as expected on all of them.
Restarting inetd:
* flyingraspi: no errors
* mononoke and clarisse, both show the following entry in daemon.log:
inetd[1719886]: amanda/tcp: unknown service
I'm not even 100% sure whether it's inetd (my bet) or xinetd but here
they are:
/etc/inetd.conf: (unchanged)
amanda stream tcp nowait backup /usr/lib/amanda/amandad amandad
-auth=bsdtcp amdump amindexd amidxtaped
/ect/xinetd.d/amanda: (unchanged)
service amanda
{
disable = no
flags = ipv4
socket_type = stream
protocol = tcp
wait = no
user = backup
group = disk
groups = yes
server = /usr/lib/amanda/amandad
server_args = -auth=bsdtcp amdump amindexd amidxtaped
senddiscover
}
Any clues? I'd like to hear from people already using Amanda but the one
question I have for everyone is: how do I verify which inetd version I
am using? (and then remove the irrelevant config).
Thanks,
Andrea.
Reply to: