Hi,
[EMAIL PROTECTED] said:
> WARNING: program /usr/local/amanda/libexec/planner: not setuid-root
> WARNING: program /usr/local/amanda/libexec/dumper: not setuid-root
> WARNING: program /usr/local/amanda/sbin/amcheck: not setuid-root
Just as the warning indicates, these executables (and some others) must
be installed setuid-root. If you run "make install" as root after building
the amanda source, it will do this for you. You can do this yourself, as
root, using the chown and chmod commands. Here is a list of the files that
are setuid on my system and the correct permissions:
-rwsr-x--- 1 root operator 72501 Jul 31 00:26 ./libexec/calcsize *
-rwsr-x--- 1 root operator 247833 Jul 31 00:27 ./libexec/dumper
-rwsr-x--- 1 root operator 64122 Jul 31 00:26 ./libexec/killpgrp *
-rwsr-x--- 1 root operator 328112 Jul 31 00:27 ./libexec/planner
-rwsr-x--- 1 root operator 61677 Jul 31 00:26 ./libexec/rundump *
-rwsr-x--- 1 root operator 62470 Jul 31 00:26 ./libexec/runtar *
-rwsr-x--- 1 root operator 339552 Jul 31 00:27 ./sbin/amcheck
* Only required on Amanda clients.
The paths above are relative to the Amanda installation heirarchy,
/usr/local in your case.
NOTE: The proper group owner for these files may be different than mine!
Replace the "operator" group above with the group that your Amanda
user belongs in. That may be "disk", "backup", or some other group.
> WARNING: info file
> /var/lib/amanda/InternalSet1/curinfo/workstation1/_etc/info: does not exist
[etc]
The info files should be created during the first successful amdump run. No
need to worry about these. You might make sure that the Amanda user owns
the /var/lib/amanda directory and all subdirectories.
> ERROR: workstation1: [host amandaserver.domain.com: port 1096 not secure]
This is a symptom of the amcheck executable being installed non setuid-root,
as detailed above.
> WARNING: workstation2: selfcheck request timed out. Host down?
Something on workstation2 or between amandaserver and workstation2 is
misconfigured.
On workstation2:
Check to make sure that the proper entries are in inetd.conf or (xinetd.conf
and the xinetd config dir if you use xinetd). Check /etc/services for the
various amanda entries. Check the various system logs for errors from
[x]inetd. Look in /tmp/amanda for *.debug files and see what they have to
say if there are any.
On the amanda server:
Check the /tmp/amanda/amcheck.*.debug files on the Amanda server and see if
they note any errors.
Check to see if a firewall between the amanda server and workstation2 is
eating your packets.
Make sure that hostname for workstation2 is resolvable to an IP address AND
that the IP address resolves to the hostname for workstation2. Testing
this with "nslookup" may not be sufficient since nslookup goes through
different steps to resolve hostnames/IP numbers than most other programs
(including Amanda). John Jackson has some programs that do the lookups just
as Amanda does:
ftp://gandalf.cc.purdue.edu/pub/amanda/gethostbyaddr.c
ftp://gandalf.cc.purdue.edu/pub/amanda/gethostbyname.c
It could be any number of other problems, but that's what I'd look at first.
Hope this helps,
-Ben
--
Benjamin Lewis Thank goodness modern convenience is a
Database Analyst/Programmer thing of the remote future.
Purdue University Computing Center -- Pogo, by Walt Kelly
[EMAIL PROTECTED]
