False Alerts

I am running ServerCheck 7.14.2 and have the Temp / Humid, Flooding, and Power sensors. They are connected to the same switch as the server running the ServerCheck program. I am receiving numerous false alerts and all of them are due to the following: "A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond ."



Any suggestions would be greatly appreciated.



A sample of my alert history is below.

POWERUP Thu Jan 15 11:13:37 2009 OK DOWN PWR OK UNKNOWN

HUMIDITY Thu Jan 15 11:04:35 2009 OK DOWN 18.1 A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond

TEMPERATURE Thu Jan 15 11:02:14 2009 OK DOWN 73.04 A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond

FLOODING Thu Jan 15 11:00:52 2009 OK DOWN Dry A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond

FLOODING Thu Jan 15 10:48:00 2009 DOWN OK Dry 00:09:45

HUMIDITY Thu Jan 15 10:45:57 2009 DOWN OK 17.8 00:08:06

FLOODING Thu Jan 15 10:43:34 2009 OK DOWN Dry UNKNOWN

HUMIDITY Thu Jan 15 10:41:47 2009 OK DOWN 17.6 A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond

POWERUP Thu Jan 15 10:39:26 2009 DOWN OK PWR OK 00:09:45

POWERUP Thu Jan 15 10:35:00 2009 OK DOWN PWR OK A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond

TEMPERATURE Thu Jan 15 10:24:56 2009 DOWN OK 73.58 00:11:30

HUMIDITY Thu Jan 15 10:24:12 2009 DOWN OK 16.5 00:08:31

FLOODING Thu Jan 15 10:24:11 2009 DOWN OK Dry 00:08:26

TEMPERATURE Thu Jan 15 10:20:46 2009 OK DOWN 73.94 A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond

HUMIDITY Thu Jan 15 10:17:50 2009 OK DOWN 15.4 A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond

FLOODING Thu Jan 15 10:14:36 2009 OK DOWN Dry A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond

POWERUP Thu Jan 15 10:11:11 2009 DOWN OK PWR OK 00:08:26

POWERUP Thu Jan 15 10:03:54 2009 OK DOWN PWR OK A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond

HUMIDITY Thu Jan 15 10:00:34 2009 DOWN OK 15.2 00:09:25

TEMPERATURE Thu Jan 15 10:00:24 2009 DOWN OK 74.48 00:11:30

FLOODING Thu Jan 15 09:57:18 2009 DOWN OK Dry 00:09:45

HUMIDITY Thu Jan 15 09:56:24 2009 OK DOWN 16.5 A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond

TEMPERATURE Thu Jan 15 09:55:58 2009 OK DOWN 71.6 A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond

FLOODING Thu Jan 15 09:52:52 2009 OK DOWN Dry A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond

FLOODING Thu Jan 15 09:43:07 2009 DOWN OK Dry 00:08:26

HUMIDITY Thu Jan 15 09:42:49 2009 DOWN OK 15.9 00:07:43

FLOODING Thu Jan 15 09:38:41 2009 OK DOWN Dry A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond

HUMIDITY Thu Jan 15 09:38:39 2009 OK DOWN 15.9 A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond

What intervals have you set for the sensors:

- interval when OK

- interval when DOWN

- retry interval

and how many retries before DOWN ?

Number of retries before monitor fails? 5 interval 15 seconds

Minimal interval between 2 checks 250 seconds

Interval when status is down 250 seconds



Under Default Monitor values i have:

interval 180

intervalwhendown 180

retries 3

retryinterval 5

I have resolved the issue myself. Apparently HP Servers with teamed network connections have problems communicating with the Tibbo devices. I hope this helps anyone else having similar issues.

Thank you for the feedback