On Mon, April 13, 2015 11:13 am, Andy Smith wrote:
J.C. Cleaver wrote:
When you do a "xymoncmd xymond_alert --dump-config" do the 'TIME' lines show up properly? And, generally speaking... is the interval selection working?
I just want to try to narrow down if this is a display issue in the CGI or something going wrong with the parsing generally.
-jc
On Mon, April 13, 2015 5:55 am, Scot Kreienkamp wrote:
Confirmed here as well.
Scot Kreienkamp
From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Brandon Dale Sent: Monday, April 13, 2015 1:01 AM To: Gavin Stone-Tolcher; xymon at xymon.com Subject: Re: [Xymon] alerts.cfg ÂTIME=Â broken in v4.3.19?
The same thing is happening for me in 4.3.19
I have TIME=*:0800:2200 in alerts.cfg and it now shows as Â-Â in info column and the config report
Regards,
Brandon
From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Gavin Stone-Tolcher Sent: Monday, 13 April 2015 10:09 AM To: xymon at xymon.com<mailto:xymon at xymon.com> Subject: [Xymon] alerts.cfg ÂTIME=Â broken in v4.3.19?
Hi, I am seeing something unusual in the Âinfo display for alerting on v4.3.19:
alerts.cfg entry:
HOST=mixtec.cc.uq.edu.au SERVICE=fping,bbd MAIL irt-work-sms at xyz.cc.uq.edu.au<mailto:irt-work-sms at xyz.cc.uq.edu.au> DURATION>3m TIME=W:0945:1800 COLOR=red REPEAT=1w FORMAT=SMS RECOVERED
Âinfo for mixtec.cc.uq.edu.au (v4.3.19)
Alerting: Service Recipient 1st Delay Stop after Repeat Time of Day Colors bbd irt-work-sms at xyz.cc.uq.edu.au<mailto:irt-work-sms at xyz.cc.uq.edu.au> (R) 3m 1s - 1w - red fping irt-work-sms at xyz.cc.uq.edu.au<mailto:irt-work-sms at xyz.cc.uq.edu.au> (R) 3m 1s - 1w - red
Notice Â-Â for ÂTime of DayÂ!
Âinfo for mixtec.cc.uq.edu.au (reverted to v4.3.18)
Alerting: Service Recipient 1st Delay Stop after Repeat Time of Day Colors bbd irt-work-sms at xyz.cc.uq.edu.au<mailto:irt-work-sms at xyz.cc.uq.edu.au> (R) 3m 1s - 1w W:0945:1800 red fping irt-work-sms at xyz.cc.uq.edu.au<mailto:irt-work-sms at xyz.cc.uq.edu.au> (R) 3m 1s - 1w W:0945:1800 red
ÂTime of Day seems correct.
Is anyone else seeing similar?
Cheers, Gavin Stone-Tolcher, IT Support Officer, Network Operations and Incident
Display issue. Tested today, the alerts worked for me as expected.
Andy
Thanks...
Yeah, looks like this was caused by a bug when EXTIME support was added. This should be fixed in 4.3.20.
Regards, -jc