PDA

View Full Version : Windows Client Fails selfcheck with ACK warning



atomrat
December 6th, 2006, 06:07 PM
I have been search for the reason for the warning message. I have not been able to figure out what I am missing. I have reviewed and double checked most of the settings. Here are some of my files.

Client Side
inetd.conf
amanda stream tcp nowait amandabackup /usr/lib/amanda/amandad.exe amandad -auth=bsdtcp amdump amindexd amidxtaped

.amandahosts
sd-lnsrv02.vfz.lab amandabackup amindexd amidxtaped

amanda-client.conf
conf "DailySet1"
auth "bsdtcp"
index_server "sd-lnsrv02.vfz.lab"
tape_server "sd-lnsrv02.vfz.lab"

Server Side
.amandahosts
localhost root amindexd amidxtaped
localhost amandabackup
localhost.localdomain root amindexd amidxtaped
localhost.localdomain amandabackup
#sdspdxr3.vfz.lab root amindexd amidxtaped
sdspdxr3.vfz.lab amandabackup amindexd amidxtaped
sd-lnsrv02 amandabackup amdump
sd-lnsrv02 root amindexd amdixtaped

disklist
sdspdxr3.vfz.lab D:\ hard-disk-tar
sd-lnsrv02 /boot hard-disk-dump


Let me know if there is any other information that can help

Garry

Sachin
December 6th, 2006, 07:22 PM
Hi Gary,
Your client side amandahost should be like this:
sd-lnsrv02.vfz.lab amandabackup amdump

The format is:
<amanda-server-name> <backup-user-on-the-server> <service-to-which-access-is-given>

So on the client side there is no service of amindexd or amidxtaped available, this services are only applicable for server's amandahost file.

Disklist entry consisting diskdev as "D:\" might not work sometimes. If it doesnt works, please try "/cygwin/d/".

Hope this helps,

Regards,
Sachin

atomrat
December 6th, 2006, 07:37 PM
I changed the amandahosts on the client side to match what Sachin said it should be. I still get the same issue.

Thanks Sachin for helping.

Garry

Sachin
December 6th, 2006, 07:52 PM
Hi Gary,

Is your dns configured, are your server and client able to ping each other with fqdn?

Please go through these articles:
http://wiki.zmanda.com/index.php/Amcheck:_selfcheck_request_failed
http://wiki.zmanda.com/index.php/Windows_client

Regards,
Sachin

vdh
February 28th, 2007, 06:25 AM
I had a similar problem today while switching from a samba based backup to the Windows client.
Using tcpdump I noticed that the server was using UDP to connect to the client, while the inetd.conf on the client was set up to listen for TCP connections.

Adding auth "bsdtcp" to the dumptype definition solved the problem for me.