Disable until OK 🔗 link

Dear all,

I tested to disable ALL until OK on a server.  When I started the server all nettests changed color. clamd is not started automatically so it turned red. The client-tests remained blue.

Is this a bug or a feature?
The only way to re-enable the tests is to disable them again with a finite time and then enable them.

Regards
Lars Ebeling

http://leopg9.no-ip.org
Hobbithobbyist

"It is better to keep your mouth shut and appear stupid than to open it and remove all doubt."
-- Mark Twain

Dear All,

when I poweroff a hobbitclient and disable all test for it until OK and then restart the server and the hobbitclient the cpu-test stays blue until OK. Ie the only problem is that the test is yellow since the server is recently rebooted.

I understand the way it works, but still it is OK. It is a bit annoying to see this blue icon.

-- 
Regards
Lars Ebeling

http://leopg9.no-ip.org
Hobbithobbyist

"It is better to keep your mouth shut and appear stupid than to open it and remove all doubt."
-- Mark Twain

Also, if a test was red before you reboot the machine (such as disk usage),
it will stay blue until either you re-enable it, or you fix the problem.
Sometimes you just want to disable the alerts while rebooting, but then have
everything go back to paging when the machine is back up.  In this case,
it's probably better to not use the "disable until OK" test, but just
disable it for a fixed amount of time.

On 3/9/07, 192.168.0.8 <user-1fecd3eafd52@xymon.invalid> wrote: