On Sat, Nov 17, 2018 at 12:56 PM Nathan Stratton Treadway < [email protected]> wrote:
> On Sat, Nov 17, 2018 at 12:00:49 -0500, Gene Heskett wrote: > > But without the logdir on the cli as --logdir=/path/to, it still doesn't > > work because planner, although it does read amanda.conf, does not pickup > > the logdir entry in amanda.conf. And I just found that the configure > > disallows the setting of logdir as its a deprecated method. > > > > That damns us to specifying the --logdir on the cli, and I believe we > > should not use the same path as in amanda.conf, > > Yes, in v3.5 the planner --log-filename option tells the program where > to write some output, and it required. For these manual runs you don't > care about the info it writes there, so you just need to specify some > out-of-the-way place for it to write to. > > Since it's creating the file in question, and normally is passed that > argument by amdump which has already gone through the process of > building a log file name to use, the planner executable itself does not > look at the "logdir" config setting. > > (Note that the config option is "logdir", i.e. a directory, while the > planner command-line argument is a full path-to-a-specific-file-name -- > two different beasts.) > > > > my balance report this > > morning is blank for this mornings run. > > amanda@coyote:~/amanda-3.5.1$ /usr/local/sbin/amadmin Daily balance > > > > due-date #fs orig MB out MB balance > > ---------------------------------------------- > > 11/17 Sat 0 0 0 --- > > 11/18 Sun 3 17741 15322 -9.7% > > 11/19 Mon 5 27503 15341 -9.6% > > 11/20 Tue 1 49240 25295 +49.1% > > 11/21 Wed 6 17357 14821 -12.6% > > 11/22 Thu 7 1086 360 -97.9% > > 11/23 Fri 3 40754 15666 -7.6% > > 11/24 Sat 2 22109 22109 +30.4% > > 11/25 Sun 4 68490 43131 +154.3% > > 11/26 Mon 38 31911 17565 +3.6% > > ---------------------------------------------- > > TOTAL 69 276191 169610 16961 > > (estimated 10 runs per dumpcycle) > > > > > > So I am assuming I nuked one too many planner files when cleaning up > > from the aborted run. Planner does not leave its log files there in that > > directory anyway. Is it supposed to? All that left when its done is the > > amdump-datetime files. > > It's hard to know for sure without having seen the balance output before > your most recent run, but "amadmin ... balance" uses data from the info > files, not any sort of log files, so I am guessing the output above is > not related to the deletion of any "planner files". > > Rather, I think it just reflects the fact that you are running it after > today's dump has already finished, so nothing is due for full dumps > today. (Before we fixed the small-DLE bug you wouldn't see > completely-empty days because those small DLEs were always showing as > needing an immedate full dump... but now that that's fixed you will see > today as "empty" after today's dump has finished.) > > > So in the midst of all of this, be careful not to leave a stray log file in your 'logdir' or the planner will bork on the next run like so: NOTES: planner: WARNING: Argument '--start-time' matches neither a host nor a disk. The job still ran. I'm just not sure if there will be any issues to arise. If there is, I'll post back. Chris
