Index: [Article Count Order] [Thread]

Date:  Sat, 7 Oct 2006 08:25:06 +0200
From:  Michael Stauber <bq (at mark) solarspeed.net>
Subject:  [coba-e:07478] Re: SWATCH ERROR
To:  coba-e (at mark) bluequartz.org
Message-Id:  <200610070825.07264.bq (at mark) solarspeed.net>
In-Reply-To:  <039801c6e9d0$80515100$6501a8c0@mjrtab>
References:  <039801c6e9d0$80515100$6501a8c0@mjrtab>
X-Mail-Count: 07478

Hi mjr,

> Cron <root (at mark) ns5>    /usr/sbin/swatch -c /etc/swatch.conf
> /usr/sausalito/swatch/bin/am_network.sh: line 64: [: too many arguments

In "Active Monitor" / "Settings" turn off monitoring "Network Status". Save 
changes.

Generally the monitoring script for "Network Status" monitoring has a few 
minor problems. If your gateway doesn't react to pings because it has ICMP 
turned off, the monitoring script will report failed network status. There 
are also a few other occasions which the script can't deal well enough with 
either.

Even if everything works correct, the active monitor will (usually) be unable 
to notify you about failed network status - after all, how do you get that 
info if the network is down to begin with? It's only really useful if you are 
connected to the server via eth1 through a LAN or something like that. 

-- 

With best regards,

Michael Stauber