Looks to me like xinetd is working correctly. If xinetd was refusing the connection you wolkd never see the 220 prompt.
Some sugesstions: 1. Does <amandahome>/.amandahosts on the tape server have a line like: localhost root my.server root 2. It may be necessary to add the server name to /etc/hosts. 3. Try # amrecover -s localhost -t localhost -C <config> On Tue, 15 Jan 2002, Eric Hillman wrote: - - And yes, I have read the FAQ. - - On my RedHat 7 server, Amrecover invariably dies with an "Unexpected server - end of file" error. All other amanda functions (amdump, acheck, alabel) work - great. I have the sneaking suspicion that xinetd is somehow to blame, mainly - because of this error message which shows up in /var/log/messages whenever I - run amrecover: - - Jan 15 11:05:25 www xinetd[27241]: refused connect from 206.101.101.101 - - (I changed the IP address, but it is the eth0 address, despite the fact that - I'm using 'amrecover -s localhost') - - but... /etc/hosts.allow is set up to allow access from my own host and every - conceivable alias or variation thereof. Ditto for .amandahosts. And - telnetting directly to the ports seems to work. I can even get an amandaidx - session going, after a fashion (the line in ALL CAPS is my input): - - [root@penguin tmp]# telnet localhost 10082 - Trying 127.0.0.1... - Connected to localhost.localdomain (127.0.0.1). - Escape character is '^]'. - 220 penguin AMANDA index server (2.4.1p1) ready. - I CANT SPEAK YOUR CRAZY MOON LANGUAGE - 500 Access not allowed - 200 Good bye. - Connection closed by foreign host. - - Any suggestions on what I'm missing, or how I can track down why this is - happening? - -- -- Stephen Carville UNIX and Network Administrator Ace Flood USA 310-342-3602 [EMAIL PROTECTED]
