Don't know if this problem has been solved for you, but if you are using
hosts.allow/deny, you may find it necessary to permit aanda access in
hosts.allow.
For me, simply adding to hosts.allow
amandad: (ip of backup host)
worked a treat.
On Wed, 21 Feb 2001, John R. Jackson wrote:
...
... Another curious problem is that in the faq it says to do a
netstat -a | grep -i amanda
and that this should return something. I get nothing when I do this.
/etc/services has a listing for amanda and kamanda etc...
Then xinetd is not set up right (which has been a real PITA recently)
"John R. Jackson" wrote:
... Another curious problem is that in the faq it says to do a
netstat -a | grep -i amanda
and that this should return something. I get nothing when I do this.
/etc/services has a listing for amanda and kamanda etc...
Then xinetd is not set up right (which
"Toby" == Toby Bluhm [EMAIL PROTECTED] writes:
Toby Hitting the PID with -HUP did not do the trick
Toby for me.
xinetd needs a SIGUSR1 (or USR2; there is a slight difference,
check the manpage) to reload its config. SIGHUP just makes it
dump its current state to /tmp. Why they decided
Thanks, that worked. And yes, that is truely odd. I wonder how many scripts
were rendered useless because of this change... :)
I have a new problem however. amdump works, but only for one disk.
All of the disks to be backed up are on the same machine (the tape server and
client are the same
... The e-mail report comes back like this for all but 1 share:
192.168.1. /usr/local lev 0 FAILED [disk /usr/local offline on 192.168.1.10?]
What does amcheck say?
If you comment out everything in disklist for this client except
/usr/local and run amdump, what's in
Hi Holm
I've just started with amanda on Red Hat. Spent a long night getting it working (with
a lot of help from this list).
Here's my entry in xinetd.conf... (not touched)
==
defaults
{
instances = 60
log_type= SYSLOG authpriv
Unfortunately this is nearly identical to what I have (save the disable=no
which didn't make things go). I've found that I can run amandad by hand and
it acts as predicted (timing out after 30 seconds) but it still isn't being
called from xinetd. Another curious problem is that in the faq it
