Groups > linux.debian.user > #201703

Re: Heck, why did the server freeze?

From	Reco <recoverym4n@enotuniq.net>
Newsgroups	linux.debian.user
Subject	Re: Heck, why did the server freeze?
Date	2018-10-26 20:20 +0200
Message-ID	<wNeSe-7bh-11@gated-at.bofh.it> (permalink)
References	<wMS5k-1PA-15@gated-at.bofh.it> <wMSI1-2hB-1@gated-at.bofh.it> <wN6Bj-2fr-1@gated-at.bofh.it> <wN6Bk-2fr-7@gated-at.bofh.it> <wNefw-6Js-3@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On Fri, Oct 26, 2018 at 07:38:56PM +0200, Alessandro Vesely wrote:
> On Fri 26/Oct/2018 11:27:36 +0200 Reco wrote:
> > On Fri, Oct 26, 2018 at 11:23:39AM +0200, Alessandro Vesely wrote:
> >> The problem is that the server froze.  I don't think that's what it is supposed
> >> to do when a card fails.
> > 
> > It's my impression too.
> 
> In general, it is too difficult to know if a link is good, at least on the
> local side.  I found nothing better than running pings by cron.

lldpd, there's no substitutes for that in a single L2 segment.
Taking WAN into account, pings seem the most reasonable way.

Reco

Back to linux.debian.user | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Heck, why did the server freeze? Alessandro Vesely <vesely@tana.it> - 2018-10-25 20:00 +0200
  Re: Heck, why did the server freeze? Brian <ad44@cityscape.co.uk> - 2018-10-25 20:40 +0200
    Re: Heck, why did the server freeze? Alessandro Vesely <vesely@tana.it> - 2018-10-26 11:30 +0200
      Re: Heck, why did the server freeze? Reco <recoverym4n@enotuniq.net> - 2018-10-26 11:30 +0200
        Re: Heck, why did the server freeze? Joe <joe@jretrading.com> - 2018-10-26 18:10 +0200
        Re: Heck, why did the server freeze? Alessandro Vesely <vesely@tana.it> - 2018-10-26 19:40 +0200
          Re: Heck, why did the server freeze? Reco <recoverym4n@enotuniq.net> - 2018-10-26 20:20 +0200

csiph-web