On Wed, Oct 03, 2018 at 09:37:42 -0400, Gene Heskett wrote:
> Now I am confused, you are saying that in effect I have to copy this
> tarball to every client machine in my disklist and add this file to all
> those and rebuild as client?
>
> Sorry, that doesn't cut it. The clients are running whatever version is
> available from their repo's, as old as 3.3.1 in one case.
>
No, you don't have to update the amanda-security.conf file on the client
if you aren't upgrading the client's Amanda; I have many old clients
running against the server whch has 3.5 and didn't have to change any of
them that way....
I had in mind from the error messages you quoted that your upgrade
proceedure pushed the new version out to all your machines... but
knowing now that that is not the case, it sounds like what's going on
here is that amcheck prints the same error message once for each client
system it checks, but the actual error is just on the server side. (I'm
assuming here that "server" is where you are attempting to upgrade to
3.5.)
So, get the line fixed in the amanda-security.conf on that server
machine, and I think that one fix will resolve all the copies of the
error message....
Nathan
----------------------------------------------------------------------------
Nathan Stratton Treadway - [email protected] - Mid-Atlantic region
Ray Ontko & Co. - Software consulting services - http://www.ontko.com/
GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt ID: 1023D/ECFB6239
Key fingerprint = 6AD8 485E 20B9 5C71 231C 0C32 15F3 ADCD ECFB 6239
