On Wednesday 03 October 2018 09:37:42 Gene Heskett wrote: > On Wednesday 03 October 2018 09:01:03 Nathan Stratton Treadway wrote: > > On Wed, Oct 03, 2018 at 01:48:25 -0400, Gene Heskett wrote: > > > the error messages changed to > > > > > > ERROR: coyote: selfcheck request failed: No defined tcp_port_range > > > in '/usr/local/etc/amanda-security.conf' > > > ERROR: shop: selfcheck request failed: No defined tcp_port_range > > > in '/usr/local/etc/amanda-security.conf' > > > ERROR: lathe: selfcheck request failed: No defined tcp_port_range > > > in '/usr/local/etc/amanda-security.conf' > > > ERROR: GO704: selfcheck request failed: No defined tcp_port_range > > > in '/usr/local/etc/amanda-security.conf' > > > ERROR: picnc: selfcheck request failed: No defined tcp_port_range > > > in '/usr/local/etc/amanda-security.conf' > > > > Do your amanda-security.conf files include "tcp_port_range=" lines? > > > > The template amanda-security.conf file should be generated by the > > "make_security_file" utility within the common-src/ subdirectory > > during the build. So if the files installed on the client machines > > are missing tcp_port_range line, search in your build logs and build > > directory to see if the template is generated correctly (i.e. with > > that line included), and work forward from there.... > > Nathan > > 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. > > If i haven't screwed the moose here with all this putzing around, > changing perms all over the place, killing heyu in the process > according to a message I got this morning, I am about to cd to the > 3.3.7p1 tree and type as root:make install. > > At least it works albeit not well with regard to the planner. > > To the amanda folks in general, this has turned into a greek orgy with > its apparently total lack of cross version compatibility. Definitely > NOT my definition of progress. I also have several builds of > amanda-4.alpha that were less trouble and worked!
Done, back on 3.3.7p1, amcheck is happy, and the make install seems to have fixed heyu. Thats a head scratcher for sure unless the install does a bunch of chowns/chmods to restore what I did with chown's and chmod's trying to make 3.5.1 work, failing rather spectacularly. Now, I do look forward to the next release, in hopes that it will not leave fatherless children laying around like 3.5.1 has done. And that the planner gets some tlc. What I see in the emails is that the planner says its going to do "this" which bears little resemblance to what it claims to have actually done in the rest of the same email. As a user of amanda since 1998, when it did what it said it was going to do, this needs TLC in several departments. Documentation included. -- Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>
