> On Mar 30, 2018, at 12:52 PM, Chris Hoogendyk <[email protected]> wrote: > > My Amanda server spontaneously rebooted at 1:09am this morning. After > checking services, one of the first things I did was to check up on Amanda, > which should have been running at that hour. Since the system rebooted, there > are no /tmp debug files. However, the holding disk has stuff that was being > backed up – not much, since I have fast LTO7 tapes that it gets pushed out to. > > I did an `amcheck daily`, which in older versions would tell me I needed to > run amcleanup (I'm running Amanda 3.4.5 on Ubuntu 14.04 Server LTS). That > told me that there were 0 problems found. Then I ran `amcleanup daily`, > expecting it to spawn off and send an email report. Instead, I got: > > amcleanup: no unprocessed logfile to clean up > amcleanup: /usr/local/etc/amanda/daily/log/amdump exists, renaming it > amcleanup: /usr/local/sbin/amcleanupdisk stderr: amcleanupdisk: Invalid > header type: -2 (UNKNOWN) > > What do you make of this? What should I do, aside from just proceeding with > ongoing backups? > > It seems I will have no records of what did get backed up last night before > the reboot. It should have been substantial, since backups started around > 10:30pm last night. > > > -- > --------------- > > Chris Hoogendyk > > - > O__ ---- Systems Administrator > c/ /'_ --- Biology & Geosciences Departments > (*) \(*) -- 315 Morrill Science Center > ~~~~~~~~~~ - University of Massachusetts, Amherst > > <[email protected]> >
Since there was an amdump file, there is probably a log.* file too. Go to that directory, and try an “amtoc” to see what files it already dumped to tape/vtape. I like to configure the command “ amtoc -i -t -a ./log.yyymmnnxxxx “ but there are a number of flags available for the command. Deb Baddorf Fermilab
