In my case they are bound until you attempt to run amrecover. As soon as it
attempts to access the index server then you get the following in the
messages log:
Oct 10 15:23:11 blight xinetd[1255]: warning: can't get client address:
Transport endpoint is not connected
Oct 10 15:23:11 blight xinetd[1256]: warning: can't get client address:
Transport endpoint is not connected
Oct 10 15:23:11 blight xinetd[1257]: warning: can't get client address:
Transport endpoint is not connected
Oct 10 15:23:11 blight xinetd[1258]: warning: can't get client address:
Transport endpoint is not connected
Oct 10 15:23:11 blight xinetd[1259]: warning: can't get client address:
Transport endpoint is not connected
Oct 10 15:23:11 blight xinetd[1260]: warning: can't get client address:
Transport endpoint is not connected
Oct 10 15:23:11 blight xinetd[1261]: warning: can't get client address:
Transport endpoint is not connected
Oct 10 15:23:11 blight xinetd[1248]: amandaidx service was deactivated
because of looping
>From that point on, it doesn't show up in netstat anymore because xinetd
deactivated it.
markh
-----Original Message-----
From: Bernhard R. Erdmann [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 10, 2001 4:03 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: Amrecover - Amandaidx Looping?
> I have read extensively and have failed to find a solution to my
> problem. I am hoping someone will know what I have done wrong. I
> can't
> seem to get "amrecover" to work for me.
Check using netstat if the following port are bound:
$ netstat -an|grep :1008.
tcp 0 0 0.0.0.0:10082 0.0.0.0:*
LISTEN
tcp 0 0 0.0.0.0:10083 0.0.0.0:*
LISTEN
udp 0 0 0.0.0.0:10080 0.0.0.0:*
$ grep ^am /etc/services
amanda 10080/udp # amanda backup services
amandaidx 10082/tcp # amanda backup services
amidxtape 10083/tcp # amanda backup services
