Hallo everyone,
thank you all for your fast and helpful response. Unfortunately the problem
persists.
Is there a way to filter out the (in my opinion faulty) SAS card?
Regards,
Timo
--
Get 100% visibility into
On 2013-08-13 05:49, Muhamad Faiz wrote:
Hi guys,
My Nagios setup are having high service check latency.
Check nagios latency result is 240 seconds!
./check_nagios_latency.sh -w 30 -c 60
CRITICAL: Latency at 240.183 seconds!
Change to Nagios 4 and your latency will most likely go away.
What are your
check_result_reaper_frequency
and
max_check_result_reaper_time
set to?
I use 3 and 15 respectively here.
Cheers,
Phil
--
Phil Randal
Infrastructure Engineer
Hoople Ltd | Thorn Office Centre | Hereford HR2 6JT
Tel: 01432 260415 | Email:
Hi,
In summery page of Nagios I am unable to view complete status information for a
service.
Is there any restriction for status information message length.Can some one
suggest how view full message.
My status information message length is around 70 char's.
Thanks,
Sandeep.
On 13 Aug 2013 05:22, Muhamad Faiz muhamad.f...@asia.xchanging.com
wrote:
My Nagios setup are having high service check latency.
Check nagios latency result is 240 seconds!
...
Any advice will be much appreciated.
If you haven't stopped / started the nagios daemon lately, then do that
Could you check that you're not accidentally running 2 nagios daemons?
On Tue, Aug 13, 2013 at 03:49:19AM +, Muhamad Faiz wrote:
Hi guys,
My Nagios setup are having high service check latency.
Check nagios latency result is 240 seconds!
./check_nagios_latency.sh -w 30 -c 60
Hi Sandeep,
I use longer messages routinely. They cannot have a carriage return/new
line in them, otherwise they will be cut off at that point.
For example:
This is a short message with more than 70 characters in it.
Will display in its entirety. The following won't:
This is a short
