[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [hobbit] Purple Problems
- To: hobbit (at) hswn.dk
- Subject: RE: [hobbit] Purple Problems
- From: Tim Grzechowski <tim.grzechowski.osv (at) fedex.com>
- Date: Fri, 02 Jan 2009 15:16:25 -0600
- Thread-index: Aclr7mD3RAw5lZQVRGS10276E5iB5gBB7/nwAAbGNdA=
The Ghost Client list is blank and blue (Disabled?).
Checked eight clients out of the ~100 and all of them are able to telnet to
the server on port 1984 without issue.
Shutdown the client on a client only machine. Copy /dev/null to
hobbitclient.log and clientlaunch.log . Started 'runclient.sh start' --
hobbitclient.log is empty. clientlaunch.log has two lines that show it has
started.
No change.
I shut down the client (on the server) and hobbit server itself. Checked /
cleared the logs. Restarted both the server, and after a couple minutes
restarted client on the server as well.
No change. Still not showing at of the pertinent info.
On the server checked client-local.cfg and bb-hosts in hobbit's /etc
directory and they are fine and the last day of access was weeks before this
issue popped up.
Any other ideas?
/tg
P.S. All the file systems have ample available space.
_____
From: Stef Coene [mailto:stef.coene (at) docum.org]
Sent: Thursday, January 02, 2009 17:44:28 +0100
To: hobbit (at) hswn.dk
Subject: Re: [hobbit] Purple Problems
What you did with your script is deleting all checks that are purple.
A purple check is a check that has not been updated for a while. So
removing
a purple check can be done in 2 ways: like you did by deleting the check or
by sending a new status. In your case, you need to check why the status is
not been send to the hobbit server. Check the client logs, you can also try
a telnet on the hobbit port (default 1984) from the client to the hobbit
server to see if there is a network problem. Also, check the ghost client
list (can be found on the hobbit server in the menu).
Happy new year and wishes you all a good monitoring time,
Stef