Cheers for the direction.
Thanx
On Fri, 2005-05-06 at 23:37 +0200, Stefan G. Weichinger wrote:
Hi, Lei Zhong,
on Freitag, 06. Mai 2005 at 21:52 you wrote to amanda-users:
LZ I checked /var/log/messages. It reports that Service
LZ amandaidx: missing '{' [file=/etc/xinetd.d/amandaidx]
I just installed Amanda
server and client on a Fedora machine. I ran amcheck and amdump locally. They
were both successful. However, when I ran amrecover, I got the error
amrecover: cannot connect to FQDN of my machine: connection
refused. I checked /etc/host and hosts.allow. I also put
--On Friday, May 06, 2005 12:03:13 -0400 Lei Zhong [EMAIL PROTECTED] wrote:
I just installed Amanda server and client on a Fedora machine. I ran
amcheck and amdump locally. They were both successful. However, when I
ran amrecover, I got the error amrecover: cannot connect to FQDN of my
I checked /var/log/messages. It reports that Service
amandaidx: missing '{' [file=/etc/xinetd.d/amandaidx]
[line=2]
Service amidxtape: missing '{' [file=/etc/xinetd.d/amidxtape] [line=2]
Can somebody help me out? Thanks, Lei
On Fri, May 06, 2005 at 03:52:27PM -0400, Lei Zhong wrote:
I checked /var/log/messages. It reports that Service amandaidx:
missing '{' [file=/etc/xinetd.d/amandaidx] [line=2]
Service
amidxtape: missing '{'
Hi, Lei Zhong,
on Freitag, 06. Mai 2005 at 21:52 you wrote to amanda-users:
LZ I checked /var/log/messages. It reports that Service
LZ amandaidx: missing '{' [file=/etc/xinetd.d/amandaidx] [line=2]
LZ
LZ Service amidxtape:
Hi,
I've configured tapeless backup, and trying to verify the data by
running amrecover. It says Connection refused
I had port in /etc/services, and xinetd enabled; and also an entry
lnx200.gibbons.com root
in .amandahosts
Server is itself client, and recovery is done on it.
Here's the
I found it.
The installation set the user of amandaidx and amidxtape to amanda, but
I dont know why Amanda requires root to run it, which conflicts with the
default setting.
bao wrote:
Hi,
I've configured tapeless backup, and trying to verify the data by
running amrecover. It says Connection
On Wed, 26 Feb 2003, bao wrote:
I found it.
The installation set the user of amandaidx and amidxtape to amanda, but
I dont know why Amanda requires root to run it, which conflicts with the
default setting.
Amanda run amandaidx and amidxtape under the user amanda.
but it s the server part
I have an amanda server s6a.server.com
and I backed up clients s2a.client.com /home to the
server.
On the server amanda user is amanda
on the client amanda user is root
when I log on to the client and type
amrecover -s s6a.server.com -t s6a.server.com
I get amrecover: cannot connect to
On Mon, Jun 03, 2002 at 04:16:11PM -0500, Rebecca Pakish wrote:
You're right, that worked.
Joshua, I should have tried that sooner when you suggested it. But I'm
racking my notes trying to remember why I changed that to yes in the first
place. I know I just used this configuration to
Hello all,
I know this topic was just covered, but the answers really don't seem to be
helping me.
I've been running amanda for almost a year now, and have been indexing and
successfully recovering individual files. All of a sudden I'm getting this
error:
[root@ants root]# amrecover uadaily
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
On Mon, 3 Jun 2002 at 9:02am, 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...
Ah, yes, that should work (I
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
Joshua Baker-LePain wrote:
On Mon, 3 Jun 2002 at 8:39am, Rebecca Pakish wrote
[root@ants root]# amrecover uadaily
AMRECOVER Version 2.4.2p2. Contacting server on slaw.unterlaw.com ...
amrecover: cannot connect to slaw.unterlaw.com: Connection refused
***amrecover debut says:
amrecover:
I've got wait=no there, but I don't know that that is your issue.
There's a reason I have wait=yes, but for the life of me I can't remember
what it is.
What's the output of 'chkconfig --list'?
[root@slaw etc]# chkconfig --list
keytable0:off 1:on2:on3:on4:on5:on
On Mon, 3 Jun 2002 at 9:38am, Rebecca Pakish wrote
xinetd based services:
chargen-udp:off
chargen:off
daytime-udp:off
daytime:off
echo-udp: off
echo: off
time-udp: off
time: off
There's your problem -- the service isn't running. Maybe an xinetd
upgrade changed the functionality such that the three services in one
file method doesn't work any longer. In any case, break your
/etc/xinetd.d/amanda file into three files -- amanda, amandaidx, and
amidxtape -- and restart
Can you telnet to each of thes ports?
$ telent target amandaix (use 'quit' to exit)
[root@slaw etc]# telnet slaw.unterlaw.com amandaidx
Trying 10.1.7.23...
telnet: connect to address 10.1.7.23: Connection refused
$ telnet target amidxtape ('quit' or CR to exit)
[root@slaw etc]# telnet
On Mon, 3 Jun 2002, Joshua Baker-LePain wrote:
- On Mon, 3 Jun 2002 at 9:38am, Rebecca Pakish wrote
-
- xinetd based services:
- chargen-udp:off
- chargen:off
- daytime-udp:off
- daytime:off
- echo-udp: off
-
If not, reload xinetd and check the messages file for any errors.
Also make sure that ipchains or iptables is not filtering the port.
I don't see where they are...
That was very unclear of me...I meant I don't see where they are filtering
the port. (There I go having half the conversation in my
I'm not so sure. I have a similar setup -- all three in one file --
and chkconfig reports the same thing to me. However, amrecover works
fine for me.
I've been using the one-file method for some time now and it's always
worked for me, as well. That's what's so confusing about this...it's all
On Mon, Jun 03, 2002 at 10:15:34AM -0500, Rebecca Pakish wrote:
Can you telnet to each of thes ports?
$ telent target amandaix (use 'quit' to exit)
[root@slaw etc]# telnet slaw.unterlaw.com amandaidx
Trying 10.1.7.23...
telnet: connect to address 10.1.7.23: Connection refused
Not
On Mon, 3 Jun 2002, Rebecca Pakish wrote:
- Can you telnet to each of thes ports?
-
- $ telent target amandaix (use 'quit' to exit)
-
- [root@slaw etc]# telnet slaw.unterlaw.com amandaidx
- Trying 10.1.7.23...
- telnet: connect to address 10.1.7.23: Connection refused
This is definitly a
Do you have nmap ? Try:
# nmap -sT -p 10082 chena
[root@slaw etc]# nmap -sT -p 10082 slaw.unterlaw.com
Starting nmap V. 2.54BETA22 ( www.insecure.org/nmap/ )
The 1 scanned port on slaw.unterlaw.com (10.1.7.23) is: closed
Nmap run completed -- 1 IP address (1 host up) scanned in 1 second
On Mon, 3 Jun 2002 at 2:08pm, Rebecca Pakish wrote
Where the heck is 10082/tcp amandaidx???
Try this. Do '/etc/init.d/xinetd restart'. Then, look in
/var/log/messages for the messages from xinetd, ending with a line like
this:
Jun 3 15:27:23 $HOST xinetd[29922]: Started
Summation:
amandaidx is looping and looping and looping until xinetd can't take it any
more and kills it.
After a fresh restart of xinetd, nmap reveals:
[root@slaw amanda]# nmap slaw.unterlaw.com
Starting nmap V. 2.54BETA22 ( www.insecure.org/nmap/ )
Interesting ports on slaw.unterlaw.com
Try changing this and restarting xinetd. See if the problem continues.
- service amandaidx
- {
- protocol= tcp
- socket_type = stream
- wait= yes
- user= amanda
- group = disk
- groups = yes
-
When you change the configuration to nowait ( wait = no ) for amandaidx,
you should see this problem end.
On Mon, 2002-06-03 at 15:59, Rebecca Pakish wrote:
Summation:
amandaidx is looping and looping and looping until xinetd can't take it any
more and kills it.
After a fresh restart of
You're right, that worked.
Joshua, I should have tried that sooner when you suggested it. But I'm
racking my notes trying to remember why I changed that to yes in the first
place. I know I just used this configuration to recover a file a couple of
months ago and the wait=yes was in place then!!
Hi,
I'm having some problem with amrecover it always saaid the the server refuse the
connection ¨
What I'm missing.
here is the debubg:
orion:/#amrecover
AMRECOVER Version 2.4.2p2. Contacting server on orion.lsn.ca-indosuez.com ...
amrecover: cannot connect to orion.lsn.ca-indosuez.com:
Has the server supported Amanda clients before? This sounds like a needed
service is turned off at orion. Check /etc/inetd.conf.
R Becker
On Thu, 30 May 2002 [EMAIL PROTECTED] wrote:
Hi,
I'm having some problem with amrecover it always saaid the the server refuse the
connection ¨
What
Yes I was able to do a back from Orion and from another hosts
**
DISCLAIMER - E-MAIL
---
The information contained in this E-Mail is intended for the named
recipient(s). It may contain certain privileged and
: Thursday, May 30, 2002 4:03 AM
To: [EMAIL PROTECTED]
Subject: amrecover connection refused
Hi,
I'm having some problem with amrecover it always saaid the the server refuse
the
connection ¨
What I'm missing.
here is the debubg:
orion:/#amrecover
AMRECOVER Version 2.4.2p2. Contacting server
Hello,
i had read about problems with amrecover 2.4.2p1 in this list. I know I
need some patches to fix this problem.
Where can i get the patches and install notes?
Thanks to every response.
--
MfG / best regards Thomas Halm
i had read about problems with amrecover 2.4.2p1 in this list. I know I
need some patches to fix this problem.
Where can i get the patches and install notes?
It would be difficult to supply patches for that problem. As I
recall, the changes got tangled up in some other things, and there are
Hi all,
Thanks for helping on 'hostname lookup failure' issue.
But now I have another trouble.
AMRECOVER Version 2.4.2. Contacting server on CNCBACK ...
amrecover: Error connecting to server: Connection refused
and it seems having response from amandaidx via tcpdump,
17:43:21.497311 lo
AMRECOVER Version 2.4.2. Contacting server on CNCBACK ...
amrecover: Error connecting to server: Connection refused
Assuming it's not a TCP wrappers issue or something like that, there is
a problem with the 2.4.2 amrecover and how it connects to the servers
that is fixed in the current source
39 matches
Mail list logo
