On Fri, Jul 31, 2015 at 10:38:54PM -0400, Gene Heskett wrote: > On Friday 31 July 2015 17:06:30 Jon LaBadie wrote: > > > On Sun, Jul 19, 2015 at 04:21:29AM -0400, Gene Heskett wrote: > > > 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? > > > > You have probably already checked, but the etimeout > > is "per estimate". There could be up to 3 estimates > > per DLE. > > > > dtimeout is listed as being per "disk". I'm pretty > > sure in this context "disk" == "DLE". > > > > For the estimates, are you using the default "client" > > type of estimate rather than "calcsize" or "server". > > If yes, is there a reason you must use "client" style? > > You might try the much faster "calcsize" or the almost > > instantaneous "server" estimates. > > > > Jon > > And where is that set, Jon? > > Cheers, Gene Heskett
It is a dumptype parameter: estimate [ client | calcsize | server ]+ jon -- Jon H. LaBadie [email protected] 11226 South Shore Rd. (703) 787-0688 (H) Reston, VA 20190 (703) 935-6720 (C)
