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 w
For the benefit of those who might be reading this thread in the archives
someday...
This test worked just fine:
> $ .../amindexd -t
> 220 clerk AMANDA index server (2.4.2p2) ready.
> SECURITY USER root
> 200 Access OK
> DATE 2002-01-17
> 200 Working date set to 2002-01-17.
> QU
On Tuesday 15 January 2002 12:13 pm, you wrote:
> 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 /.amandahosts on the tape server have a line like:
>
>localhost root
>my.server r
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 w
