On Sunday 13 August 2006 23:20, Lengyel, Florian wrote:
>Identical, except for identd on one client (the client that
>doesn't work doesn't have identd).

Permissions and all?  In some cases thats all important.

OTOH, the client that doesn't have inetd SHOULD have xinetd, and a 
directory of control files in /etc/xinetd.d, and the one for the amanda 
daemons should look something like this, noting that this file can be 
named anything because its the contents that count:
=====================
# default = off
#
# description: Part of the Amanda server package
# This is the list of daemons & such it needs
service amanda
{
 disable = no
 socket_type = dgram
 protocol = udp
 wait  = yes
 user  = amanda
 group  = disk
 groups  = yes
 server  = /usr/local/libexec/amandad
}
service amandaidx
{
 disable = no
        socket_type     = stream
        protocol        = tcp
        wait            = no
        user            = amanda
        group           = disk
        groups          = yes
        server          = /usr/local/libexec/amindexd
}
service amidxtape
{
 disable = no
        socket_type     = stream
        protocol        = tcp
        wait            = no
        user            = amanda
        group           = disk
        groups          = yes
        server          = /usr/local/libexec/amidxtaped
}
==========================
Those paths are as installed by the tarball build, rpms will probably not 
have the 'local' in the path.  The user is whoever will be the one to 
invoke amdump etc.  The 'group' must have write perms to the disks.

If you edit this file, then do a 'service xinetd restart' from the command 
line as root to make the edits effective w/o a reboot.

I hope this helps.

>-----Original Message-----
>From: owner-amanda-users AT amanda DOT org on behalf of Gene Heskett
>Sent: Sun 8/13/2006 7:06 PM
>To: amanda-users AT amanda DOT org
>Subject: Re:
>
>On Sunday 13 August 2006 18:07, Lengyel, Florian wrote:
>>I'm using Amanda 2.4.4p3 on a Debian system (stable release)
>>I have one client that times out during the self-check--I'm mystified.
>>What do I do to debug this? There are no firewalls--everything is
>>on the same subnet.
>>
>>
>>[amanda@amanda ~]$ amcheck Daily
>>Amanda Tape Server Host Check
>>-----------------------------
>>WARNING: holding disk /var/tmp/amanda: only 9477560 KB free (10485760 KB
>> requested) amcheck-server: slot 2: date 20060713 label Daily002 (exact
>> label match) NOTE: skipping tape-writable test
>>Tape Daily002 label ok
>>Server check took 34.036 seconds
>>
>>Amanda Backup Client Hosts Check
>>--------------------------------
>>WARNING: rt: selfcheck request timed out.  Host down?
>>Client check: 8 hosts checked in 30.485 seconds, 1 problem found
>>
>>(brought to you by Amanda 2.4.4p3)
>>[amanda@amanda ~]$
>
>Double check the install on the client, everything.  Compare to identical
>files on another client, or even the server.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2006 by Maurice Eugene Heskett, all rights reserved.