Does it only ever get this error on level 0 backups, or does it happen on
all backups ever since a certain date/event/upgrade?
I suspect that the client 'tarsier' has a copy of amandad already loaded,
and that copy thinks that it's in the middle of a backup, and won't talk to
any server that wants to do another backup.
The dirty fix I have used for this is to send a -HUP to the amandad on the
client and hope it exits gracefully. You might also need to restart inetd if
amandad is being called by inetd.
If anyone else knows a better/cleaner way...
-----Original Message-----
From: Michael Lea [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 09, 2001 4:23 PM
To: [EMAIL PROTECTED]
Subject: NAK: amandad busy
I'm getting this error from my nightly backups:
FAILURE AND STRANGE DUMP SUMMARY:
tarsier /tarsier.1/www lev 0 FAILED [tarsier NAK: amandad busy]
the host is a solaris machine with the Mbs/duplex hardset, plugged into
a switch that has them hardset. This dir is the only dir we use gtar to
backup, it's 15+GB, and I don't think I've ever had a sucessful level 0
backup of it happen. What am I doing wrong?
Thanks.
--
.michael lea _/_/ "when in danger or in
Associate System Engineer _/_/ doubt, run in circles,
[EMAIL PROTECTED] _/_/ scream and shout"
