On Saturday 18 July 2015 10:40:38 Gene Heskett wrote: > Only on THIS machine, the remotes being backed up over the cat5 always > work. > > etimeout was 600, made it 1800 > dtimeout was 1800, made it 2400 > > uptime is 7 days & small change, 135 megs into swap on an 8Gb equipt > machine. > > A reboot fixes it, for a few days, then once its started, only a > reboot seems to fix it. > > The only clue might be fromn a grep for a "code 1", in > the /tmp/amanda-dbg/amdump############# files > > root@coyote:/tmp/amanda-dbg/server/Daily# grep "code 1" * > amdump.20150717030105.debug:Fri Jul 17 09:01:06 2015: thd-0x962a400: > amdump: planner finished with exit code 1 > amdump.20150718030105.debug:Sat Jul 18 09:01:06 2015: thd-0x980c400: > amdump: planner finished with exit code 1 > > Is that 10 minutes for the estimate per DLE, or a global for the whole > thing. I thought it was per DLE? > > Clues I could use. > > Thanks. > > Cheers, Gene Heskett
It's after 3Am and its going to fail again. Putting a tail on /tmp/amanda-dbg/server/Daily planner.####### right now shows: OPTIONS features=ffffffff9efefbffffffffff3f; /home 0 SIZE 72650 /home 1 SIZE 150 /etc 0 SIZE 4410 /etc 1 SIZE 380 /root 0 SIZE 60 /root 1 SIZE 20 /usr/src 0 SIZE 25100 /usr/src 1 SIZE 1730 /usr/local 0 SIZE 40 /usr/local 1 SIZE 30 /usr/lib/amanda 0 SIZE 4000 /usr/lib/amanda 1 SIZE 10 /var/lib/amanda 0 SIZE 880 /var/lib/amanda 1 SIZE 400 /lib/firmware 0 SIZE 53630 /lib/firmware 1 SIZE 60 ---- Sun Jul 19 03:01:08 2015: thd-0x8751c00: planner: security_close(handle=0x89b29c0, driver=0xf76cb1e0 (BSDTCP)) Sun Jul 19 03:01:08 2015: thd-0x8751c00: planner: security_stream_close(0x89b3008) Nothing beyond that, and the rest of the amanda processes are sitting at the bottom of the htop display using zero resources or cpu time. Waiting for planner to give a code 0 return, which I don't think it will get. So it got the report for /lib/firmware ok. a du -h shows the remaining 41M /lib/firmware 1.1M /lib/xtables 8.0K /lib/lsb/init-functions.d 24K /lib/lsb 4.0K /lib/systemd/system/sockets.target.wants 4.0K /lib/systemd/system/poweroff.target.wants 4.0K /lib/systemd/system/halt.target.wants 4.0K /lib/systemd/system/dbus.target.wants 4.0K /lib/systemd/system/basic.target.wants 4.0K /lib/systemd/system/multi-user.target.wants 4.0K /lib/systemd/system/reboot.target.wants 136K /lib/systemd/system 140K /lib/systemd 517M /lib/ But I've no clue if amanda sorts this in the same order as a du -h or an ls would. Is this helpfull? In the meantime, I am going to reboot and run a session by hand as this will be 3 days running it has failed. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>
