I am on 4.3.7 now; saw the behavior on earlier 4.3.x versions.
On Mon, Jan 9, 2012 at 11:20 AM, Josh Luthman
<user-4c45a83f15cb@xymon.invalid> wrote:
What version is this? I don't think I've got that bug.
Here's the most recent test that got everyone annoyed
Sat Jan 07 09:02:06 2012 green 2 days 4:48:10
Sat Jan 07 08:16:59 2012 red 0:45:07
Sat Jan 07 07:16:50 2012 yellow 1:00:09
Sat Jan 07 03:16:16 2012 green 4:00:34
Sat Jan 07 02:56:13 2012 red 0:20:03
Sat Jan 07 01:56:04 2012 yellow 1:00:09
notifications sent:
Sat Jan 7 01:56:04 2012 edprocs3.example.com.watch_oelogs
(10.100.4.57) user-e49400df80ec@xymon.invalid[139] 1325919364 0
Sat Jan 7 02:57:17 2012 edprocs3.example.com.watch_oelogs
(10.100.4.57) user-e49400df80ec@xymon.invalid[139] 1325923037 0
Sat Jan 7 02:57:17 2012 edprocs3.example.com.watch_oelogs
(10.100.4.57) alert1[149] 1325923037 0
Sat Jan 7 02:57:17 2012 edprocs3.example.com.watch_oelogs
(10.100.4.57) alert2[152] 1325923037 0
Sat Jan 7 02:57:17 2012 edprocs3.example.com.watch_oelogs
(10.100.4.57) alert3[153] 1325923037 0
Sat Jan 7 02:57:17 2012 edprocs3.example.com.watch_oelogs
(10.100.4.57) alert4[154] 1325923037 0
Sat Jan 7 03:07:21 2012 edprocs3.example.com.watch_oelogs
(10.100.4.57) alert1[149] 1325923641 0
Sat Jan 7 03:07:21 2012 edprocs3.example.com.watch_oelogs
(10.100.4.57) alert2[152] 1325923641 0
Sat Jan 7 03:07:21 2012 edprocs3.example.com.watch_oelogs
(10.100.4.57) alert3[153] 1325923641 0
Sat Jan 7 03:07:21 2012 edprocs3.example.com.watch_oelogs
(10.100.4.57) alert4[154] 1325923641 0
Sat Jan 7 07:16:53 2012 edprocs3.example.com.watch_oelogs
(10.100.4.57) user-e49400df80ec@xymon.invalid[139] 1325938613 0
Sat Jan 7 08:17:13 2012 edprocs3.example.com.watch_oelogs
(10.100.4.57) user-e49400df80ec@xymon.invalid[139] 1325942233 0
Sat Jan 7 08:17:13 2012 edprocs3.example.com.watch_oelogs
(10.100.4.57) alert1[149] 1325942233 0
Sat Jan 7 08:17:13 2012 edprocs3.example.com.watch_oelogs
(10.100.4.57) alert2[152] 1325942233 0
Sat Jan 7 08:17:13 2012 edprocs3.example.com.watch_oelogs
(10.100.4.57) alert3[153] 1325942233 0
Sat Jan 7 08:17:13 2012 edprocs3.example.com.watch_oelogs
(10.100.4.57) alert4[154] 1325942233 0
You can see on Saturday it went yellow at 1:56 , emailing
"user-e49400df80ec@xymon.invalid" which is our email alert, and then an hour later
it went red and started emailing the world. Then at 7:00 am the same
thing.
I note that all of these servers are on EDT, and this test went red
exactly an hour after going yellow because it's a custom test that
goes yellow after so many seconds and red an hour later.