Can you telnet to each of thes ports?
$ telent <target> amandaix (use 'quit' to exit)
$ telnet <target> amidxtape ('quit' or CR to exit)
If not, reload xinetd and check the messages file for any errors.
Also make sure that ipchains or iptables is not filtering the port.
On Mon, 3 Jun 2002, Rebecca Pakish wrote:
- >That's not the file you're looking for. I believe it's
- >/etc/xinetd.d/amandaidx that allows amrecover to work remotely.
-
- I don't have that file...I have a file /etc/xinetd.d/amanda that looks like
- this...
- service amanda
- {
- protocol = udp
- socket_type = dgram
- wait = yes
- user = amanda
- group = disk
- groups = yes
- server = /usr/local/libexec/amandad
- }
-
- service amandaidx
- {
- protocol = tcp
- socket_type = stream
- wait = yes
- user = amanda
- group = disk
- groups = yes
- server = /usr/local/libexec/amindexd
- }
-
- service amidxtape
- {
- protocol = tcp
- socket_type = stream
- wait = no
- user = amanda
- group = disk
- groups = yes
- server = /usr/local/libexec/amidxtaped
-
- I get the same error when I try to run amrecover on the amanda server, as
- well, so it's not a remote issue.
-
- >You'll also need to make sure that the service is allowed in
- /etc/hosts.allow
- >(it's amindexd) on slaw from ants.
-
- I currently don't have anything in /etc/hosts.allow, but I never have, and
- I've run amrecover before. (?) What do I need to add, just a line that says
- amindexd?
-
- rap
-
-
--
-- Stephen Carville
UNIX and Network Administrator
DPSI (formerly Ace USA Flood Services)
310-342-3602
[EMAIL PROTECTED]
