On Nov 3, 2014, at 5:18 PM, Gene Heskett <[email protected]> wrote: > On Monday 03 November 2014 17:55:38 Jon LaBadie did opine > And Gene did reply: >> On Mon, Nov 03, 2014 at 09:52:52AM -0500, Gene Heskett wrote: >>> Greetings; >>> >>> Running 3.3.6 here. >>> >>> Last night it played catchup ok, but when DST ended at 2am Sunday >>> morning, apparently all the timeout timers in amanda went aglay, and >>> it tried to quit, but left numerous bits and pieces still running, >>> hogging the machine heavily. It sent me the email as if it was >>> finished and had failed most DLE's. Half an hour later there were >>> still copies of chunker and gzip using 99% of the cpu. I did >>> eventually find the parent that was restarting stuff every time I >>> killed it, but eventually I gave up and rebooted as I was still >>> having 1 minute+ pauses between pressing a key and seeing it on >>> screen. >>> >>> Now that I think about it, ISTR I wound up rebooting it when the time >>> went fwd last spring. >>> >>> I know this isn't much to go on, but I thought it ought to be >>> reported that amanda gets all flustered when the clocks are changed >>> while it is running. >>> >>> Did anyone else have an amdump session running at 2 am Sunday? Did >>> it work, or blow up? >> >> Change the start time of your amdumps to 0301 ? >> >> jl > > That is a possibility Jon, but then what about all the housekeeping the > system fires off at 04:00? Amanda would not be done, and would likely log > all sorts of logging errors after logrotate and friends do their thing. > But I'll try it just for grins. Thanks. > > Cheers, Gene Heskett
Well then — start amanda at 02:05 as that is AFTER the change, and give you a little more time before 04:00. My 2 cents. Deb
