Back on the list, this server aparently does not set a reply-to. So a reply to list comes up with a blank To: address line.
On Friday 31 July 2015 12:21:39 Debra S Baddorf wrote: > Grr! My etimeout is 2000 but yours is certainly in that ball > park. I’d try it at 20,000 (without the comma) just to see if it > changes anything. For a while. Although, I guess “waiting forever” > is what it is currently already doing, isn’t it? Yes Deb. Even tried at 2400, no solution. > > Hmmm. Thinking. > Deb Baddorf > > On Jul 31, 2015, at 7:35 AM, Gene Heskett <[email protected]> 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. > > > > And it failed last night again, after only 3 days uptime. and only > > this machine. From an amcheck and GO704 is turned off: > > gene@coyote:/usr/local/etc/amanda/Daily$ sudo -i > > [sudo] password for gene: > > root@coyote:~# su amanda -c "/usr/local/sbin/amcheck Daily" > > Amanda Tape Server Host Check > > ----------------------------- > > Holding disk /usr/dumps: 747640 MB disk space available, using > > 747140 MB Searching for label 'Dailys-20':found in slot 20: volume > > 'Dailys-20' Will write to volume 'Dailys-20' in slot 20. > > NOTE: skipping tape-writable test > > Server check took 0.258 seconds > > > > Amanda Backup Client Hosts Check > > -------------------------------- > > WARNING: GO704: selfcheck request failed: No route to host > > Client check: 4 hosts checked in 20.009 seconds. 1 problem found. > > > > (brought to you by Amanda 3.3.7p1) > > > > amcheck seems incapable of finding and reporting the problem, what > > ever it is. > > > > I will reboot before its scheduled to run early in the morning which > > will fix it for a few days. In the meantime what can I show here > > that might be educational? > > > >> 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 > > > > 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> 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>
