On Friday 16 November 2018 21:49:51 Chris Nighswonger wrote: > On Fri, Nov 16, 2018 at 7:36 PM Gene Heskett <[email protected]> wrote: > > On Friday 16 November 2018 15:38:27 Debra S Baddorf wrote: > > > > On Nov 16, 2018, at 2:09 PM, Gene Heskett <[email protected]> > > > > wrote: > > > > > > > > On Friday 16 November 2018 14:38:58 Chris Nighswonger wrote: > > > >> On Fri, Nov 16, 2018 at 2:30 PM Gene Heskett > > > >> <[email protected]> > > > > > > > > wrote: > > > >>> from amanda as usr, find /usr/local -name 'planner' > > > >>> returns that its in /usr/local/libexec/amanda/planner > > > >>> Now I'll find out (maybe) what it thinks of my changes. Ignore > > > >>> that faint knocking sound. :) But I assumed you meant > > > >>> backup_job was your config dir, in my case > > > >>> /usr/local/etc/amanda/Daily so it failed. > > > >> > > > >> backup_job is the name of the backup rather than the directory. > > > >> So in my case it looks like this: > > > >> > > > >> /usr/lib/amanda/planner campus > > > > > > > > ooohhkkaaay. Can I use wild cards like "Daily PublicA*" ? > > > > > > > > No, the logfile error already posted prevents it from running so > > > > it never gets to PublicA in any form. > > > > > > > >> Be sure to run it as your backup user. > > > > > > > > amanda in this case. > > > > > > > >> Sorry for any confusion there. > > > >> > > > >> Kind regards, > > > >> Chris > > > > > > > > Thanks Chris > > > > > > I’m not familiar with the syntax, but I would suspect it wants > > > planner <configname> node <DLE-Nickname> > > > > > > which in my case, is the “homeu” word in the following: > > > node homeu /home { > > > include “./u*” > > > } > > > > > > You have to give it a nickname, because ALL the DLEs for this > > > disk (“/home”) are based on that same disk location /home > > > So you nickname the A parts, or the AF (a-f) parts, etc. > > > > > > If it WASN’T a tar subset (using includes or excludes) then > > > you would skip the nickname and just put the disk area /home > > > But for subsets, you need a name for each one. > > > > > > Deb Baddorf > > > > The dle's in question: > > > > coyote PublicAar /home/gene/PublicA/ { > > comp-coyote-tar > > include "./[a-r]*" "./[-]*" "./_*" > > } 1 local > > > > coyote PublicAsz /home/gene/PublicA/ { > > comp-coyote-tar > > include "./[s-z]*" > > } 1 local > > > > coyote PublicAAZ /home/gene/PublicA { > > comp-coyote-tar > > include "./[A-Z]*" > > } 1 local > > > > /usr/local/libexec/amanda/planner Daily coyote PublicA* planner: could not open log > > file (null): Bad address > > > > So the above last line seems to be the showstopper > > Odd. It appears that it thinks your configuration file for Daily is > missing a logdir directive...
>From my /usr/local/etc/amanda/Daily/amanda.conf logdir "/usr/local/var/amanda/Daily" # log directory Which is where its actually keeping those logs > My production server planner version is 3.3.6. > > The 4.0.0alpha planner appears to have a few options which the 3.3.6 > version does not: > > --starttime > --log-filename > --no-taper > --no-dump > --no-flush > --no-vault > --from-client > --exact-match > > The general syntax seems to be such as this: > > /usr/lib/amanda/planner configuration [options] host diskname So for me: $conf host diskname /usr/local/libexec/planner Daily coyote /home/gene/PublicA* should work to show those 3 dle's shown above. but lets try a single dle, PublicAAZ planner: could not open log file (null): Bad address but lets see what strace says Damn, I forgot how noisy that can be. At one point it goes into a cleanup loop close(3) thru 1023 EBAD file descriptor I've found where it opens amanda.conf, no complaints And where it opens the disklist, no complaints but another handfull of lines later, its apparent that it did not obtain the logdir entry from amanda,conf as it exits with the same null pointer error. I'll go see if I can find something in the amanda-dbg directory. Thats in /tmp/amanda-dbg/server/planner And its says the strace is a lie. Fri Nov 16 15:03:50.206900809 2018: pid 29304: thd-0x992be00: planner: pid 29304 ruid 1001 euid 1001 version 3.5.1: start at Fri Nov 16 15:03:50 2018 Fri Nov 16 15:03:50.207115234 2018: pid 29304: thd-0x992be00: planner: parse error: could not open conf file '/usr/local/etc/amanda/PublicA*/amanda.conf': No such file or directory Fri Nov 16 15:03:50.207180822 2018: pid 29304: thd-0x992be00: planner: critical (fatal): errors processing config file But that is /not/ where amanda.conf lives either. So I don't have the correct commandline yet. I'm frustrated, what the hell is "diskname" if its not the dle we want to look at. Define that puppy in English please. Copyright 2018 by Maurice E. Heskett -- 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>
