Dave Ewart wrote:

On Friday, 30.05.2003 at 15:04 -0400, Ron Bauman wrote:

Any ideas of why a client would work for a while then randomly not
be able to do a selfchecK? The other amanda client is still working
great...

I have a random problem like this as well running RH Linux.  The
client occasionally fails amcheck in the afternoon. (Backups run at
nite.)  When I look at portland, the client, I find the selfcheck task
"stuck" and I am unable to kill it, even with kill -9.  See if you
have the same problem.  On the client, try

ps -ef | grep amand

or grep with whatever your amanda user account is.

If you see selfcheck running, you'll be unable to get amcheck on the
server to finish until it's gone.  Just something to check.

Interesting to see this problem reported - I've had this happen
sporadically too.  The 'host down' error relates to the localhost and it
leaves 'selfcheck' and 'amandad' running in the background.  The server
is RH Linux 7.3, running AMANDA 2.4.2p2.

However, killing those processes does not make everything better.  The
problem seems unrelated to the AMANDA configuration.  The last time it
happened here, we were fortunate enough to have a 'maintenance window'
and rebooted the server and after that amcheck ran without complaint.
However, given that this is a production server, rebooting is not a good
solution.

Dave.

Dave

do you use 'localhost' or 'hostname' in the disk list.

--
Martin Hepworth
Senior Systems Administrator
Solid State Logic Ltd
+44 (0)1865 842300




**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************