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 <amandahome>/.amandahosts on the tape server have a line like:
>
> localhost root
> my.server root
Yes, and then some. I've added "root" and "operator" lines for every
conceivable valid address for the system. ("operator" is the dumpuser, and
also the user that the amanda services run as under xinetd.)
> 2. It may be necessary to add the server name to /etc/hosts.
We use DNS instead of hosts, but, regardless, it's in hosts as well, with the
same name that DNS reports.
> 3. Try
>
> # amrecover -s localhost -t localhost -C <config>
Tried that too, same error message.
When setting this up originally, I went through hell moving, renaming,
chowning and chmodding files, as a number of things weren't readable by the
"operator" user or were in the wrong place. (In fact,
/var/lib/amanda/<config> and /etc/amanda/<config> are now the same directory,
symlinked.) Is there any chance my thrashing about has screwed up some vital
file there that could trigger this error? 'lsof' tells me nothing
particularly useful, although I did learn that amindexd is writing debug logs:
amindexd: debug 1 pid 2586 ruid 11 euid 11 start time Tue Jan 15 13:44:32 2002
amindexd: version 2.4.1p1
< 220 [server] AMANDA index server (2.4.1p1) ready.
> ����
< 500 Access not allowed
< 200 Good bye.
amindexd: pid 2586 finish time Tue Jan 15 13:44:45 2002
Not very helpful to me. Is there any way to ratchet up the debug level?
