(Note: for the discussion below I'm assuming Amanda 3.5, since that's
what Gene is using.)
On Sat, Nov 17, 2018 at 00:43:40 -0500, Gene Heskett wrote:
> On Friday 16 November 2018 21:49:51 Chris Nighswonger wrote:
> >
> > 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*
(Remember from your disklist manpage that the fields are:
hostname diskname diskdevice
e.g. coyote PublicAAZ /home/gene/PublicA/
.... and notice in particular that you specify DLEs using the diskname, not
the diskdevice path [which matters when they are different, as they are
in the case of these particular DLEs].)
> 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
[...]
> 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
(I think this is from a different run: this debug file is from an
invocation where "PublicA*" the first argument on the command line, in
the spot where the config name goes -- obviously it doesn't find an
amanda.conf file in the directory for that particular config name....)
> 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.
The "planner" command line must start with ".../planner Daily
--log-filename FILEPATH" (in that order), followed optionally by the DLE
specifications.
In the case of the planner binary, the DLE-specification arguments
normally come directly from the command line used to invoke amdump, so
you can find out a little more about how to specify them on the
amdump(8) man page... though basically that just tells you to look at
amanda-match(7), which goes into all the details.
For your current project, it seems like the DLEs you are working on all
do have names starting with "PublicA", so something like
/usr/local/libexec/planner Daily --log-filename /tmp/testplanner.log coyote
'PublicA*'
should let you check the sizes of those specific DLEs without triggering
other DLEs to be calculated.
Note the single quotes around that last argument, to make sure the shell
doesn't try to expand the "*" but instead passes that string as-is to
"planner".
(You can use a command like
amadmin Daily disklist coyote 'PublicA*'
to see what DLE entries are found for a particular DLE specification to
make sure you have that correct before running the planner and actually
kicking off a round of estimates on the clients....)
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
