That's odd on the client that is working it is defined as 
amanda dgram udp wait amanda /opt/amanda/client/libexec/amandad amandad

However I did make that change and I still get the same error.
amandad: debug 1 pid 19689 ruid 30063 euid 30063: start at Tue Oct  9
10:49:22 2007
Could not open conf file "/etc/amanda/amanda-client.conf": No such file
or directory
amandad: time 0.002: amandad: invalid service

Which is also odd.
Considering the file inetd.conf was updated re-ran inetconv and
refreshed the inetd process.

amanda  dgram   udp     wait    amanda
/opt/amanda/client/libexec/amandad amdump
Anderson

-----Original Message-----
From: Jean-Louis Martineau [mailto:martineau AT zmanda DOT com] 
Sent: Tuesday, October 09, 2007 6:41 AM
To: Krahn, Anderson
Cc: amanda-users AT amanda DOT org
Subject: Re: client issues

There is difference between system services (amanda, amanaidx and 
amidxtaped) and
amanda services (amdump, selfcheck, sendsize, sendbackup, ...)

amandad is neither.
You want the amanda system service to be able to launch the amdump 
amanda service.

change your inetd.conf to:

amanda  dgram   udp     wait    amanda
/opt/amanda/client/libexec/amandad amdump


Jean-Louis


Krahn, Anderson wrote:
> Whenever the amcheck -c Full fails on the client the service in svcadm
> will go to maintenance.
>
> Here are the debug logs...
> cat amandad.20071008155445018.debug
> amandad: debug 1 pid 10963 ruid 30063 euid 30063: start at Mon Oct  8
> 15:54:45 2007
> Could not open conf file "/etc/amanda/amanda-client.conf": No such
file
> or directory    --- not using a client file
> amandad: time 0.002: amandad: invalid service  -- extremely odd
> considering they are in inetd.conf and /etc/services.
> amanda  dgram   udp     wait    amanda
> /opt/amanda/client/libexec/amandad amandad
>
> amanda    10080/udp    # amanda
> amandaidx 10082/tcp    # amanda
> amidxtape 10083/tcp    # Amanda
>
>