Re: RedHat Amandad xinetd.conf etc etc
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)
and it is not listening on the Amanda port, which means nothing is going
to work.
You did HUP xinetd, didn't you? Is xinetd logging anything?
Here's an xinetd.d file from Joshua E Warchol [EMAIL PROTECTED] that
is typical of those reported to work;
service amanda
{
protocol= udp
socket_type = dgram
wait= yes
user= amanda # whatever --with-user was
group = amanda # whatever --with-group was
groups = yes
server = /usr/local/libexec/amandad
server_args = amandad
}
I've found that I can run amandad by hand and it acts as predicted ...
You're not even getting that far. You need to figure out the xinetd
problem first.
Andrew
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: RedHat Amandad xinetd.conf etc etc
... 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)
and it is not listening on the Amanda port, which means nothing is going
to work.
You did HUP xinetd, didn't you? Is xinetd logging anything?
Here's an xinetd.d file from Joshua E Warchol [EMAIL PROTECTED] that
is typical of those reported to work;
service amanda
{
protocol= udp
socket_type = dgram
wait= yes
user= amanda # whatever --with-user was
group = amanda # whatever --with-group was
groups = yes
server = /usr/local/libexec/amandad
server_args = amandad
}
I've found that I can run amandad by hand and it acts as predicted ...
You're not even getting that far. You need to figure out the xinetd
problem first.
Andrew
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: RedHat Amandad xinetd.conf etc etc
"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) and it is not listening on the Amanda port, which means nothing is going to work. You did HUP xinetd, didn't you? Is xinetd logging anything? For RH esp. 7.0, and for any daemons, I find /etc/rc.d/init.d/script-name restart works the best. Hitting the PID with -HUP did not do the trick for me. Just my (2/100)*$ -tkb
Re: RedHat Amandad xinetd.conf etc etc
"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 to do it this way is anybody's guess :) -- Jon
RE: Redhat Amandad xinetd.conf etc etc
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 in this case) but only one directory get's backed up. The others just don't. 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?] There is no difference between the entry in disklist that works and the ones that don't. 192.168.1.10 /home always-full 192.168.1.10 /etc always-full 192.168.1.10 /boot always-full 192.168.1.10 /root always-full 192.168.1.10 /u1 always-full *** the one that works *** 192.168.1.10 /usr/local always-full #192.168.1.10 /mnt/win always-full **above never ever works, commented out*** If someone could share some insight that would help me understand why this is happening I would be grateful. Thanks again, Andrew - "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 to do it this way is anybody's guess :) -- Jon
Re: Redhat Amandad xinetd.conf etc etc
... 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 /tmp/amanda/sendsize*debug and /tmp/amanda/sendbackup*debug (if it gets updated) on the client? Andrew John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: RedHat Amandad xinetd.conf etc etc
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
log_on_success = HOST PID
log_on_failure = HOST RECORD
}
includedir /etc/xinetd.d
===
Here's the file "amanda" in the /etc/xinetd.d directory... (amanda is mentioned in
services)
===
service amanda
{
socket_type = dgram
protocol = udp
wait = yes
user = amanda
server = /usr/local/libexec/amandad
disable = no
}
The real life saver was when I added...
program"GNUTAR"
into the define dumptype in amanda.conf
Hope this helps
rgds
Dirk
- Original Message -
From: "Holm-Hansen" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, February 21, 2001 10:34 PM
Subject: RedHat Amandad xinetd.conf etc etc
I'm on my last brain cell...
I'm getting the dreaded "selfcheck request timed-out. Host down?" message from
amcheck. I've read and re-read the faq. After doing an "ls -lu" in the
server directory, I found that the executable isn't getting called when I run
amcheck. (I believe that is what ls -lu does).
in my /etc/xinetd.d directory I have the amanda file (and an identical amandad
just in case) that looks like this:
service amandad
{
socket_type = dgram
protocol = udp
wait = yes
user = amanda
group = amanda
server = /usr/local/libexec/amandad
instances = 10
server_args = amandad
}
I don't know why I have to have "wait = yes" but I saw it in another conf
file.
Also I built this from source with the user=amanda and group=amanda.
I realize that there are billions of that could be broken so if I need to
elaborate more, I'd be more than happy to :)...
Thanks,
Andrew
RE: RedHat Amandad xinetd.conf etc etc
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 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...
I'm even more lost now than I was 20 minutes ago... :)
Thanks for taking a swing at it Dirk,
If anyone else has any ideas, I'd be thrilled to hear them!
Andrew
= Original Message From "Dirk Webster" [EMAIL PROTECTED]
=
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
log_on_success = HOST PID
log_on_failure = HOST RECORD
}
includedir /etc/xinetd.d
===
Here's the file "amanda" in the /etc/xinetd.d directory... (amanda is
mentioned in services)
===
service amanda
{
socket_type = dgram
protocol = udp
wait = yes
user = amanda
server = /usr/local/libexec/amandad
disable = no
}
The real life saver was when I added...
program"GNUTAR"
into the define dumptype in amanda.conf
Hope this helps
rgds
Dirk
- Original Message -
From: "Holm-Hansen" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, February 21, 2001 10:34 PM
Subject: RedHat Amandad xinetd.conf etc etc
I'm on my last brain cell...
I'm getting the dreaded "selfcheck request timed-out. Host down?" message
from
amcheck. I've read and re-read the faq. After doing an "ls -lu" in the
server directory, I found that the executable isn't getting called when I
run
amcheck. (I believe that is what ls -lu does).
in my /etc/xinetd.d directory I have the amanda file (and an identical
amandad
just in case) that looks like this:
service amandad
{
socket_type = dgram
protocol = udp
wait = yes
user = amanda
group = amanda
server = /usr/local/libexec/amandad
instances = 10
server_args = amandad
}
I don't know why I have to have "wait = yes" but I saw it in another conf
file.
Also I built this from source with the user=amanda and group=amanda.
I realize that there are billions of that could be broken so if I need to
elaborate more, I'd be more than happy to :)...
Thanks,
Andrew
