On 09/17/2012 08:30 AM, John Horne wrote:
On Mon, 2012-09-17 at 07:59 -0400, Ralph Mitchell wrote:
I think white typically show up for tests that are dependent
on some other test. For example, the network tests do that.
I've recently had some ping failures, so ssh came up white, but
the client tests (cpu, memory,disk, ports, procs) all came
through OK.
Okay. But as far as I remember the 'procs' and 'files' tests
default to white. When the server is first installed there are
no defined processes or files to monitor so the tests go white.
For these tests the data comes from the client via the large
status text file sent to the server. Since we got an 'oversize'
message, not all the data was available. So I assume none of the
'procs' stuff was there, so the test went purple because it
hadn't seen anything for a while. The 'files' test, I assume, had
some data, but not enough to give a result of the test. So the
test went white. (Note, I *assume* that is how it works :-))
Anyway, my point is that I would like to know if a test goes
white regardless of the reason. It is an indication that
'something is not right', yet because we tend to keep an eye on
the 'non-green' page we were unaware, in this case, that the
'files' test had gone white.
While likely not what you're looking for, the test is called
"clear" and you can search for it under "Reports / Event log
report" if you want to see all events involving clear (though at
least in my version, 4.2.3, it shows both coming FROM clear and
going TO clear).
You can at least use this to see if the issue is widespread.