Do you mean the red status details? Going to the host and checking this
entry via history it says:
Wed Jul 18 14:13:39 2012 conn NOT ok
Service conn on hostshere.imaginenetworksllc.com is not OK : Host does not
respond to ping
System unreachable for 1 poll periods (0 seconds)
I'm not sure if this is working or not - 0.0.0.0 .default. #
testip
Looking at the hosts 4 of them do not have testip listed, they may do DNS.
The remainder do not use DNS and specifically state testip.
Now one of the hosts (compass) give me an Internal Server Error for this
one red entry. A couple other older red events work. Maybe a clue?
Josh Luthman
Office: XXX-XXX-XXXX
Direct: XXX-XXX-XXXX
XXXX Wayne St
Suite XXXX
Troy, OH XXXXX
On Wed, Jul 18, 2012 at 4:18 PM, Henrik Størner <user-ce4a2c883f75@xymon.invalid> wrote:
On 18-07-2012 21:56, Josh Luthman wrote:
This would be the right time:
clientdata.log
2012-07-18 14:19:39 Tried to down BOARDBUSY: Invalid argument
history.log
2012-07-18 14:19:39 Tried to down BOARDBUSY: Invalid argument
2012-07-18 14:27:36 Will not update
/home/hobbituser/data/hist/**foohostname,**imaginenetworksllc,com.bbd -
color unchanged (green)
#last line repeated for every host that experience this problem
hobbitd.log
2012-07-18 14:19:49 Setup complete
page.log
2012-07-18 14:19:39 Tried to down BOARDBUSY: Invalid argument
The "BOARDBUSY" and "Setup complete" point to Hobbit being restarted. I
noticed you did this, so that would be around that time.
The "Will not update" is normal - hobbitd_history does a sanity check when
it receives the first status update for each status, to make sure the
history-file is in sync with the current status (updates may have been lost
while Xymon was down).
In other words nothing here that would explain what you're seeing.
What reason was given in the detailed status log for the ping test failing
? DNS lookup failure, ping timeout, ... ?
Regards,
Henrik
______________________________**
Xymon at xymon.com<