On Mon, 7 Feb 2005 15:46:20 -0600
 donald.ritchey AT exeloncorp DOT com wrote:
> The message indicates that the self-check portion of the amcheck command 
> timed out while communicating with either itself or the client. Make sure 
> that xinetd configuration files are set up correctly to respond to the 
> Amanda commands sent over the Amanda UDP port.
> 
> 1. Check your /etc/services file on each machine to ensure that you have
> the amanda UDP 10080 service defined in the file.

Did this already everything looks fine. I set it up just like another client
that works to this server.

> 
> 2. Check your /etc/inetd.conf file or /etc/xinetd.d file(s) have the 
> appropriate entries for amanda (I use Amanda at work on a Tru64 UNIX system
> and my home server is Fedora Core 3, your mileage may vary....)

I also did this already, again everthing looks good.


> 
> 3. Check the contents of the /tmp/amanda debug files from the amcheck

from the server's debug file:

amcheck: debug 1 pid 26575 ruid 33 euid 0 start time Mon Feb 7 21:11:33 2005
amcheck: dgram_bind: socket bound to 0.0.0.0.932
amcheck: pid 26575 finish time Mon Feb 7 21:12:03 2005

I get the following in the client's secure log file?

Feb 7 21:13:32 "clients name" xinetd[1338]: START: amanda pid=17335
from="server ip"
 
I substituted "client name" and "server ip" for the actual server and client

> operation to get more detailed explanations of why the operation is
> failing.
> 
> Best wishes,
> 
> Don
> 
> Donald L. (Don) Ritchey
> Information Technology
> Exelon Corporation
> 
> -----Original Message-----
> From: Don Carlton [mailto:don.carlton AT citadel DOT edu]
> Sent: Monday, February 07, 2005 1:41 PM
> To: amanda-users AT amanda DOT org
> Subject: client version varies from server
> 
> 
> On my amanda server (redhat 7.3) I'm running amanda-server-2.4.2p2-7 and on
> the client I'm running amanda-client-2.4.4p1-0.3E (RedHat ES). I keep
> getting
> "selfcheck request timed out" when I try to run amcheck on the server? Is
> this caused by the different versions??
> 
> 
> ************************************************************************
> This e-mail and any of its attachments may contain Exelon Corporation
> proprietary information, which is privileged, confidential, or subject 
> to copyright belonging to the Exelon Corporation family of Companies. 
> This e-mail is intended solely for the use of the individual or entity 
> to which it is addressed. If you are not the intended recipient of this 
> e-mail, you are hereby notified that any dissemination, distribution, 
> copying, or action taken in relation to the contents of and attachments 
> to this e-mail is strictly prohibited and may be unlawful. If you have 
> received this e-mail in error, please notify the sender immediately and 
> permanently delete the original and any copy of this e-mail and any 
> printout. Thank You.
> ************************************************************************
>