Several of us have problems where TCP based connections to nodes that are down.
(depending on the “auth” method in use) take long enough to timeout that they
cause
failures on other nodes which are NOT down.
I have older nodes which are still using udp connections, which do not
ever have this problem.
Does this sound like it may be involved in your case? “auth=bsdtcp” is the
default with all the modern
versions of amanda. I have the problem if the node down is “auth=bsdtcp”
or
“auth=krb5” but not on the “auth=bsd” nodes.
Deb Baddorf
Fermilab
On May 13, 2015, at 8:49 AM, Gene Heskett <[email protected]> wrote:
> Greetings all;
>
> Running 3.3.7p1 on assorted client installs.
>
> No clue why, but it appears that one of the machines (alias "shop") in
> the shop crashed last night, sometime after I closed up for the evening.
> I've also lost my ssh -Y link to it, and no ping response.
>
> When amdump ran, it was of course un-available.
>
> But that seems to have killed the backups for this machine too, as was
> only able to backup the lathe.
>
> amcheck, when I ran it just now, only reported;
> "WARNING: shop: selfcheck request failed: No route to host"
> One problem.
>
> But amdump totally failed this machine, "coyote", too. What sort of
> gremlins might do that?
>
> 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>
