Oops, forgot to mention that... I can ping by name:
-bash-2.05b$ ping owl
PING owl (192.168.168.35) from 192.168.168.70 : 56(84) bytes of data.
64 bytes from owl (192.168.168.35): icmp_seq=1 ttl=64 time=0.200 ms
Thanks,
Matt
-----Original Message-----
From: Pavel Pragin [mailto:ppragin AT zmanda DOT com]
Sent: Tuesday, June 06, 2006 5:42 PM
To: Matt Emmott
Cc: amanda-users AT amanda DOT org
Subject: Re: HOST DOWN error connecting to new client
Matt Emmott wrote:
> Hi,
>
> I just compiled and installed Amanda 2.5.0p2 as a client on a Red Hat
> Enterprise ES 4 machine. Our server (which has been running for years)
> is a Red Hat 8 machine running Amanda 2.4.2p2. I've modified the
> disklist file in the archive section of our server to only back up the
> new server, named owl, via the following line:
>
> owl /home/path/to/files user-tar
>
> However, when I try to run /usr/sbin/amcheck Archive, I get the
> following error:
>
> ===============================================================
>
> Amanda Tape Server Host Check
>
> -----------------------------
>
> Holding disk /usr/amandatmp: 10851752 KB disk space available, that's
> plenty
>
> ERROR: label DailySet103 doesn't match labelstr "^archive[0-9][0-9]*$"
>
> (expecting tape archive09 or a new tape)
>
> NOTE: skipping tape-writable test
>
> NOTE: info dir /var/lib/amanda/Archive/curinfo/owl: does not exist
>
> NOTE: index dir /var/lib/amanda/Archive/index/owl: does not exist
>
> Server check took 18.177 seconds
>
> Amanda Backup Client Hosts Check
>
> --------------------------------
>
> WARNING: owl: selfcheck request timed out. Host down?
>
> Client check: 1 host checked in 29.998 seconds, 1 problem found
>
> ===============================================================
>
> This was just a test run, so the bad tape error is ok, and I assume
> the info and index errors are ok, since a backup has never been run.
> The problem is with the Host Down error. I've enabled Amanda in
> xinetd.d, and restarted xinetd. a chkconfig --list tells me that
> Amanda is up and running. There is no firewall on the server, and
> hosts.deny is empty.
>
> What else can I look at to figure out why this isn't connecting?
>
> Thanks,
>
> Matt
>
Hi,
maybee you should try using a FQDN for owl
see if you can ping owl from the machine you are running amcheck from
Pavel
|
