[Xymon] 'Invalid timespec' in xymond.log

[John Thurston]

It is certainly possible . .

That is what is noted in the man-page, but I have a memory of digging 
through the code and noticing that a semicolon was accepted in the same 
way as the comma. Of course, that was years ago and I can not now find 
my notes on the subject.

FWIW, these semicolons parse correctly on a host's 'info' page

But I suppose that doesn't mean they are parsed correctly everywhere 
downtime is considered.

And the total number of complaints in the log doesn't align with the 
number of downtimes I have defined with semicolons. Maybe those messages 
are being triggered by messages for hosts with downtimes defined . . but 
my downtimes are (for the most part) defined in .default. lines so 
affect every host (so every message evaluation).

If the semicolon is causing a parsing problem, I'd expect to see one for 
each line in hosts.cfg
If it is causing a problem evaluating messages, I'd expect to see one 
for each yellow or red bubble

I'm not saying it /isn't/ causing those problems. Just that I can't make 
the number of logged lines reconcile with either scenario.

--
Do things because you should, not just because you can.

John Thurston    907-465-8591
John.Thurston at alaska.gov
Department of Administration
State of Alaska

On 11/27/2023 10:38 AM, Jeremy Laidman wrote:
> Hi John
>
> On Tue, 28 Nov 2023, 06:24 John Thurston, <john.thurston at alaska.gov> 
> wrote:
>
>     I have 'DOWNTIME' specifications like
>
>>     DOWNTIME=60:*:*;*:1630:0800
>>
> Is it possible the semicolon is supposed to be a comma?
>
> J
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xymon.com/pipermail/xymon/attachments/20231127/20cc0908/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Pd0qIjV7fIgoSMJs.png
Type: image/png
Size: 10289 bytes
Desc: not available
URL: <http://lists.xymon.com/pipermail/xymon/attachments/20231127/20cc0908/attachment.png>