> On Nov 12, 2018, at 5:30 PM, Gene Heskett <[email protected]> wrote:
>
> On Monday 12 November 2018 15:44:04 Nathan Stratton Treadway wrote:
>
>> On Mon, Nov 12, 2018 at 15:18:05 -0500, Gene Heskett wrote:
>>>> So, if you want to do the deep dive to try to debug that quirk...
>>>> the next step will be to look through the
>>>> /var/log/amanda/Daily/amdump.20181112*
>>>> log file (assuming the run in question started after midnight this
>>>> morning; if not the datetime-stamp would be 20181111* of course).
>>>
>>> It did, I have some other stuff so it isn't started till about
>>> 03:05.
>>>
>>>> Find the "ANALYZING ESTIMATES..." section, and cut-and-paste the
>>>> log lines that discuss coyote:/var from that section on down
>>>> through INITIAL SCHEDULE, PROMOTING DUMPS IF NEEDED, and on
>>>> through the GENERATING SCHEDULE section.... and we'll see if
>>>> those lines tell us anything useful...
>>>
>>> Ok but my local prefix is /usr/local, and there is no such text
>>> in /usr/local/tmp*, so the .debug files there are quite small, 15 to
>>> 20
>>
>> (Look at the top of the output of "amadmin Daily status"; the very
>> first line should be
>> Using: [PATH...]/amdump.1
>> , where [PATH...] is the path to the directory containing the amdump.*
>> and log.* files. [That will be a different directory than the one
>> containing the *.debug log files.])
>>
>> Nathan
>
> Mmmmmm, my amadmin from a 3.5.1 (p1) build doesn't claim to have a status
> option:
> amanda@coyote:/tmp/amanda-dbg$ /usr/local/sbin/amadmin Daily status
> /usr/local/sbin/amadmin: unknown command "status"
>
> And I do not think I am specifically building it that way.
>
> I seem to be full of puzzles. And I'm equally sure it is being an
> excedrin headache. :(
>
Gene - the command was corrected later. It should be
amstatus Daily
Deb Baddorf
