On Fri, Nov 16, 2018 at 19:31:15 -0500, Gene Heskett wrote:
> /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
This sort of error is what you get when you try start using yourself an
"internal" utility -- there's a reason it's in the lib/amanda directory
rather than the bin directory :)
In Amanda 3.5's planner it seems a log file is required, but since the
program is written under the asumption that it will always be called by
the driver process, there is no error checking to make sure it's
actually provided -- when it isn't, the program simply attempts to open
a file using uninintialized variable for the filename....
It seems the provided filename is used for writing to, so to avoid
confusion I'm guessing the best idea is to just write to a temporary
file unrelated to any log file that Amanda itself would create.
So, for example, I got my Amanda 3.5.1 planner to run successfully using
the command:
# su backup -c "/usr/lib/amanda/planner TestBackup --log-filename
/tmp/testplanner.log"
(where "backup" is the Amanda Unix user, and TestBackup is my Amanda
config name)
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
