Thomas Widhalm wrote:
Here is the error message of amcheck:
###############################
Amanda Backup Client Hosts Check
--------------------------------
ERROR: praxis.plus.sbg.ac.at: [could not access /dev/root (/):
Permission denied]
ERROR: ralph.edvz.sbg.ac.at: [could not access /dev/root (/): Permission
denied]
Client check: 3 hosts checked in 0.241 seconds, 2 problems found
###############################
and now the fstab entry in one of the machines:
###############################
LABEL=/ / ext3 defaults
1 1
###############################
I used to use GNUTAR. I recognized, that there are 2 instances of tar
installed on these systems! So I switched to DUMP, but it didn't work
out.
ok, we're mixing things up here, I believe.
Gnutar reads the directory tree, and does this as root by invoking the
suid-root program "runtar" (in libexec). Sometimes some overworked
security administrator runs a program that removes the suid-bit from
the executables. Or you could have the libexec dir NFS-mounted, and
you have the nosuid in the mount options.
Dump however needs access to the device. The device must be readable by
the group that amanda is in. Because the rundump is invoked by the
program "amandad", it inherits the groups from that that program. The
effective groups are initialised by xinetd. If the group is not the
PRIMARY group of amanda on that client, then you also need "groups =
yes", in the xinetd configuration file. Of course also verify that
"group = disk" for your installation.
Moreover, when you are using LVM on those devices, the /dev/root is
actually a symlink to /dev/volumegroup/logvolroot (and that again
is a symlink to /dev/mapper/something which should be group readable by
the group that amanda is in).
LVM sets the permissions of /dev/volumegroup too root:root 700.
That means that amanda cannot even find out where the link points to.
Also the device node itself is 600 and owned by root on creation
on several versions of LVM (only fixed recently).
But the VG directory still has the permissions too strict, even in the
most recent version.
You could change the permissions, but LVM change it again some
undefined time later.
I did not yet have time to find out if that only happens on boot or
mount; maybe a chmod in some local init.d is enough to fix the problem.
That's one of the reasons why I use gnutar.
The above output strongly make me think you are using DUMP and hit
the LVM problem.
Switch to gnutar again, and send the exact error message when you hit
permission problems again, together with ls -lL of the runtar in libexec.
--
Paul Bijnens, Xplanation Tel +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUM Fax +32 16 397.512
http://www.xplanation.com/ email: Paul.Bijnens AT xplanation DOT com
***********************************************************************
* I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, *
* F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, *
* init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... *
* ... "Are you sure?" ... YES ... Phew ... I'm out *
***********************************************************************
|
