Hi, community. New to Amanda here. After some luck setting up and testing a backup server with one client running Amanda 3.2.3 (on Fedora Core 15 and Fedora Core 8, respectively), I'm running into some very strange problems with a new configuration for a new client, running Amanda 2.5.1p2 on a Fedora Core 4 system.

After setting up the client for backup, amdump appears to have worked correctly. However, When I try to recover, I get the following error:

[root@myclient recover]# amrecover DailySet1
AMRECOVER Version 2.5.1p2. Contacting server on myserver...
[request failed: EOF on read from Amanda]
What's even more disturbing, however, is the fact that there are no log files to be seen on the client side. Looking in /var/log/amanda/, all I see is one file, install.log (no logs on the server side regarding amrecover either). This has made troubleshooting pretty much impossible. Standard commands in Amanda 3.2.3 like amadmin and amtape (and ammt too) yield

-sh-3.00$ amadmin
-sh: amadmin: command not found
-sh-3.00$ amtape
-sh: amtape: command not found
The only trace I can find of Amanda is in /var/log/messages, although I'm not sure if these logs are related to amrecover:

[root@myclient log]# tail messages
Jul 14 17:20:24 myclient kernel: e1000: eth0: e1000_watchdog_task: NIC Link is Down
Jul 14 17:20:27 myclient kernel: e1000: eth0: e1000_watchdog_task: NIC Link is Up 100 Mbps Full Duplex
Jul 14 17:20:40 myclient kernel: e1000: eth0: e1000_watchdog_task: NIC Link is Down
Jul 14 17:20:42 myclient kernel: e1000: eth0: e1000_watchdog_task: NIC Link is Up 100 Mbps Full Duplex
Jul 14 17:21:17 myclient smbd[1949]: [2011/07/14 17:21:17, 0] lib/util_sock.c:get_peer_addr(1229)
Jul 14 17:21:17 myclient smbd[1949]: getpeername failed. Error was Transport endpoint is not connected
Jul 14 17:21:17 myclient smbd[19037]: [2011/07/14 17:21:17, 0] lib/util_sock.c:get_peer_addr(1229)
Jul 14 17:21:17 myclient smbd[19037]: getpeername failed. Error was Transport endpoint is not connected
Jul 14 17:21:17 myclient smbd[19037]: [2011/07/14 17:21:17, 0] lib/util_sock.c:read_data(534)
Jul 14 17:21:17 myclient smbd[19037]: read_data: read failure for 4 bytes to client 0.0.0.0. Error = Connection reset by peer
Jul 14 17:21:20 myclient su(pam_unix)[19038]: session opened for user amandabackup by (uid=0)
Jul 14 17:24:47 myclient su(pam_unix)[19038]: session closed for user amandabackup
Jul 14 17:28:55 myclient smbd[18577]: [2011/07/14 17:28:55, 0] smbd/nttrans.c:call_nt_transact_ioctl(2332)
Jul 14 17:28:55 myclient smbd[18577]: call_nt_transact_ioctl(0x900eb): Currently not implemented.
Jul 14 17:30:19 myclient smbd[19106]: [2011/07/14 17:30:19, 0] lib/util_sock.c:get_peer_addr(1229)
Jul 14 17:30:19 myclient smbd[19106]: getpeername failed. Error was Transport endpoint is not connected
Jul 14 17:30:19 myclient smbd[19106]: [2011/07/14 17:30:19, 0] lib/util_sock.c:get_peer_addr(1229)
Jul 14 17:30:19 myclient smbd[19106]: getpeername failed. Error was Transport endpoint is not connected
Jul 14 17:30:19 myclient smbd[19106]: [2011/07/14 17:30:19, 0] lib/access.c:check_access(328)
Jul 14 17:30:19 myclient smbd[19106]: [2011/07/14 17:30:19, 0] lib/util_sock.c:get_peer_addr(1229)
Jul 14 17:30:19 myclient smbd[19106]: getpeername failed. Error was Transport endpoint is not connected
Jul 14 17:30:19 myclient smbd[19106]: Denied connection from (0.0.0.0)
Jul 14 17:30:19 myclient smbd[19106]: [2011/07/14 17:30:19, 0] lib/util_sock.c:get_peer_addr(1229)
Jul 14 17:30:19 myclient smbd[19106]: getpeername failed. Error was Transport endpoint is not connected
Jul 14 17:30:19 myclient smbd[19106]: Connection denied from 0.0.0.0
Jul 14 17:30:19 myclient smbd[19106]: [2011/07/14 17:30:19, 0] lib/util_sock.c:write_data(562)
Jul 14 17:30:19 myclient smbd[19106]: write_data: write failure in writing to client 192.168.0.232. Error Connection reset by peer
Jul 14 17:30:19 myclient smbd[19106]: [2011/07/14 17:30:19, 0] lib/util_sock.c:send_smb(769)
Jul 14 17:30:19 myclient smbd[19106]: Error writing 5 bytes to client. -1. (Connection reset by peer)
Here are the client files.

/var/lib/amanda/amanda-client.conf

Code:
conf "DailySet1"

index_server "myserver"
tape_server  "myserver"
tapedev              ""

auth "bsdtcp"
ssh_keys ""
/var/lib/amanda/.amandahosts

Code:
myclient amandabackup amdump
myserver amandabackup amdump
/etc/xinetd.d/amandaclient

Code:
service amanda
{
        disable         = no
        only_from       = myserver
        socket_type     = stream
        protocol        = tcp
        wait            = no
        user            = amandabackup
        group           = disk
        groups          = yes
        server          = /usr/lib/amanda/amandad
        server_args     = -auth=bsdtcp amdump
}
These settings worked for me when running amrecover on my other client (3.2.3). I've searched for information on this error, but it seems to be a rare one. Is it possible that I have to reinstall Amanda on my system? What could be the problem here?

Thanks in advance