selfcheck request timeout

Hey gurus!

I've checked many many resources about this error and I've done justabout everything they've asked, but I can't get rid of it, and I don'treally even know if it's a show stopper or not. Here's my situation:

I've freshly installed the Ubuntu Universe package for Amanda-Server,Amanda-Common, and Amanda-Client. The version I'm getting from amadminis 2.4.5p1. This is running on a Dell 1950 Xeon Quadcore with 2 GB ofRAM. The Server is running on my home LAN, so all IPs on its subnet areprivate. The server is also running VMWare Server hosting WindowsServer 2003 but I'm not sure that has any bearing on this. All datawill be backing up to a Overland XPress LXB 10-Tape robot with a QuantumSDLTI tape drive in it. I believe it supports 160GB tapes uncompressed,and that's what I've run the amtapetype -e parameter with. All this isworking beautifully. I can use the amtape controller to swap tapes,reset to known configs, label tapes, and I've got it all patchedtogether with the chg-zd-mtx built-in tape changer script.

My problems come in when I try to run amcheck DailySet1. The tapeserver checks run fine, with the expected warnings due to never havingrun a backup job before. The client check mewls and cries, indicatingthe selfcheck request timed out, and asks if the host is down. As thehost is the same as the one running the check, it obviously isn't down.As you can guess, this Ubuntu package has DailySet1 as it's defaultbackup set name. In installing/configuring the client, I've done thefollowing:


customized the /etc/amandahosts (symlinked by ~backup/.amandahosts)

customized the /etc/hosts.allow for the amandad, amindexd, andamidxtaped daemonscustomized the /etc/services to register the 3 above daemons as servicesfor the xinetd superservercreated a drop file in /etc/xinetd.d with the standard recommendedparameters and restarted the xinetd superserver

something that wasn't mentioned on any of the FAQs and mail lists was tochange the group on the 3 above daemons to the backup group (the groupspecified for the backup user which will be the user running amanda)IPTABLES is not running on this host, so it isn't a firewall issue,unless the port calls go running about the LAN rather than stayinginternal, which I can't imagine is happening.

netstat -a |grep amanda reports the following:
tcp        0      0 *:amandaidx             *:*                     LISTEN
udp        0      0 zeus.chaos.short:amanda *:*

Obviously the output has concatenated my FQDN, but Iwhat I don't know,is if those are all the services that should be listening, and whetherthose are the correct protocols that they are listening to.

Thus, I've done rather a lot of research to get this running, and that'snot including the many days spent ironing out the kinks in the serverissues. This one has me stumped, as the error logs don't even make apeep that something in the system is even running, much less failing...Any help that anyone could provide would be deeply appreciated. Afterall, as they say, backups are like wives...you don't realize howimportant they were until you don't have them anymore!


Best regards,
Kermit Short