[Xymon] dropping/making blue checks not persistent when restarting

[Root, Paul T]

So, there’s a couple things here.

First, how are you disabling (bluing out) a test (you call check)? Are you checking the “until OK” or are you providing a time limit for the disable? Also, if the test is green why would you want it disabled?

Second, why are you restarting xymon after a config change? All configuration files are re-read (except local-client.cfg) every 5 minutes.

Next, you say dropped tests reappear. Well of course. If the client is providing the test to the server, the server is going to display it. If you don’t want a test in xymon, it has to be disabled at the source.

I don’t understand your second paragraph. You you are saying that you disable a test and then wait 5-10 minutes and the disabled test will remain blue after restarting xymon?

From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Sven Schuster
Sent: Friday, May 19, 2017 7:55 AM
To: xymon at xymon.com
Subject: [Xymon] dropping/making blue checks not persistent when restarting

Hello everybody,

recently I've been seeing a strange issue on xymon server. When I make a check blue and shortly after xymon gets restarted due to configuration updates, that blue check will be green again afterwards. The same thing happens when a check is dropped and xymon gets restarted directly after that: the dropped check reappears.
If you wait some amount of time before restarting, say 5-10 minutes, the problem won't appear and everything will be fine. I also sync'ed on the server directly after making a check blue and before restarting (to avoid data not being written to disk for some strange reason), which unfortunately did not help.
Environment is xymon 4.3.27 on Debian jessie. Xymon has been updated to 4.3.28 because of this problem lately, with the problem appearing in 4.3.28, too. This server has just been upgraded from Debian wheezy to Jessie a few weeks ago. On wheezy xymon 4.3.27 was in use but didn't show this behaviour.

Did anybody notice such an odd behaviour or maybe have any thoughts regarding possible causes?

Thanks in advance,
Sven
This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xymon.com/pipermail/xymon/attachments/20170519/b7583b26/attachment.html>