|
Re: selfcheck request timeout
2008-01-23 10:40:37
Thanks, Paul, for your helpful responses! As you requested, I've tried
to run the amadmin command but it seems this version doesn't know that
parameter of amadmin:
backup@zeus:~$ amadmin DailySet1 config
amadmin: unknown command "config"
However, as this is a binary package, I'm not entirely certain of all
the options used to build it. The package notes indicate that the
"Amanda User" is backup with group backup.
The permissions for the amandahosts file are:
-rw-rw---- 1 backup backup 120 2008-01-21 22:06 amandahosts
There is indeed a /tmp/amanda directory as follows, but it is empty.
Permissions, as you see, are set correctly.
drwx--S--- 2 backup backup 4096 2008-01-23 00:45 amanda
Neither root nor backup users on the system are receiving mail from the
amanda process, failure notices or otherwise. With no helpful logs or
other output, I can't tell where things are failing, so if anyone has
any gotchas, I'd love to hear about it! Thanks for the help Paul!
-Kermit
Paul Bijnens wrote:
On 2008-01-23 04:40, Kermit Short wrote:
Hey gurus!
I've checked many many resources about this error and I've done
just about everything they've asked, but I can't get rid of it, and I
don't really even know if it's a show stopper or not. Here's my
situation:
[...]
backup set name. In installing/configuring the client, I've done the
following:
customized the /etc/amandahosts (symlinked by ~backup/.amandahosts)
especially here: are the permissions of this file correct?
Is that path up top ~backup/.amandahosts secure (not writeable by anone
but root or backup-user?)
customized the /etc/hosts.allow for the amandad, amindexd, and
amidxtaped daemons
customized the /etc/services to register the 3 above daemons as
services for the xinetd superserver
created a drop file in /etc/xinetd.d with the standard recommended
parameters and restarted the xinetd superserver
OK. we have to believe you that you did not make any error in there.
We cannot verify that part of the setup.
something that wasn't mentioned on any of the FAQs and mail lists was
to change the group on the 3 above daemons to the backup group (the
group
"the 3 above daemons???" which ones?
That also seems to imply that you have a discrepancy between the
username that is compiled into the executable ( with the configure
option --with-user=...) and the one that you use to run the set
of programs. They should match!
What is the output of "amadmin xx config"
and look at the expected username, in the configure options.
specified for the backup user which will be the user running amanda)
IPTABLES is not running on this host, so it isn't a firewall issue,
unless the port calls go running about the LAN rather than staying
internal, which I can't imagine is happening.
netstat -a |grep amanda reports the following:
tcp 0 0 *:amandaidx *:*
LISTEN
udp 0 0 zeus.chaos.short:amanda *:*
Obviously the output has concatenated my FQDN, but Iwhat I don't
know, is if those are all the services that should be listening, and
whether those are the correct protocols that they are listening to.
seems ok.
Thus, I've done rather a lot of research to get this running, and
that's not including the many days spent ironing out the kinks in the
server issues. This one has me stumped, as the error logs don't even
make a peep that something in the system is even running, much less
failing...
Any help that anyone could provide would be deeply appreciated.
After all, as they say, backups are like wives...you don't realize
how important they were until you don't have them anymore!
Look at the debug files on the client in /tmp/amanda?
If there are no files at all, then maybe the directory /tmp/amanda
itself is not writeable by the backupuser, e.g. because you once
have run some program as root (and then /tmp/amanda gets created
as user root, making it unwritable for the real backup user).
|
|
|
