I checked the owner of the files it it was indeed set to the backup user, I
set it to root and it now works.
I did have to set a few other files to root (i.e. dumper, taper, etc) and I
am now performing a successful amdump.
Thanks for your help.
Regards,
Craig
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: 30 August 2001 19:55
To: Walker, Craig
Cc: [EMAIL PROTECTED]
Subject: Re: Errors with amcheck
Hi,
[EMAIL PROTECTED] said:
[...]
> I have fixed most of the problems I have encountered but the problem I am
> getting is a Port Not Secure error when trying to connect to Amanda
> clients.
[...]
> Amanda Backup Client Hosts Check
> --------------------------------
> ERROR: bill: [host rimmer: port 32884 not secure]
> ERROR: ben: [host rimmer: port 32884 not secure]
> Client check: 2 hosts checked in 0.502 seconds, 2 problems found.
Is amcheck installed SETUID root? If not, and you are running it as the
amanda user (as required), it won't be able to open a "secure" port below
1024. There are several other programs that must be setuid root, but I
think that's the only one in the "sbin" area (the rest are in libexec).
Some other problems that have caused this:
1. Firewalls that do Network Address Translation, since they usually munge
the
port numbers as they forward on the connection. I think there's
something in the FAQ-O-Matic about this.
2. Using --with-portrange during the "./configure" part of the build.
I don't recall the specifics, but I think this option was broken for
some time.
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]
