My guess is that amandad is not running. Check the inetd.conf and
services to make sure they are correct.
Siobhan Gowen wrote:
This log exists on all the machines except the one that's failing. I just
got this dumped on me so I'm not very familiar with amanda. I can't seem to
find it ever completing successfully. Although since it's in Japan our day
is their night so a find is scanning the holding disk. Are there relative
logs on the amanda backup server I could look at?
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:owner-amanda-users@;amanda.org]On Behalf Of Joshua Baker-LePain
Sent: Thursday, October 31, 2002 11:58 AM
To: Siobhan Gowen
Cc: Alex Specogna; [EMAIL PROTECTED]
Subject: Re: timeout
On Thu, 31 Oct 2002 at 11:38am, Siobhan Gowen wrote
The machine is up and the amanda server and the client can ping eachother.
All running Solaris 2.6. On same net/subnet as other clients that don't
time
out. Any suggestions???
I upped the etimeout value from 500 to 5500
This has nothing to do with etimeout.
Amanda Backup Client Hosts Check
--------------------------------
WARNING: Japan-Collect1b: selfcheck request timed out. Host down?
Client check: 9 hosts checked in 30.183 seconds, 1 problems found.
Is there anything in /tmp/amanda/amandad*debug on Japan-Collect1b? Make
sure the debug file you look at is time-stamped at the time you ran
amcheck.
--
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University
--
Paul T. Root CCSA, CCSE, CCNA
Qwest Communications PAG: +1 (877) 693-7155
600 Stinson Blvd, Flr 1S WRK: +1 (612) 664-3385
Minneapolis, MN 55413 FAX: +1 (612) 664-4778
