This service has been scheduled for fixed downtime from 07-16-2019 12:45:53 to 07-20-2038 23:24:53. Notifications for the service will not be sent out during that time period.
But the comment is dated:
By Mesa de Ayuda at 2019-09-03 02:00:04
And if I look at scheduled downtimes none of the mysterious downtimes are listed, just the ones I expect to see are listed.
2 of XI5.6.14 Prod/DR/DEV - Nagios LogServer 2 Nodes
See my projects on the Exchange at BanditBBS - Also check out my Nagios stuff on my personal page at Bandit's Home and at github
Out of curiosity, can you find the service in /usr/local/nagios/etc/recurringdowntime.cfg
I ask because we recently fixed a bug whereas if you scheduled a wildcard downtime, it would get scheduled in this file, and put items in the downtime, but they would not show in the reoccurring downtimes page.
Either way, it does seem a mystery for the dates to be off...
Nothing in there except the few non-related items that should be. FYI, forgot to mention, running XI 5.6.3
2 of XI5.6.14 Prod/DR/DEV - Nagios LogServer 2 Nodes
See my projects on the Exchange at BanditBBS - Also check out my Nagios stuff on my personal page at Bandit's Home and at github
Also, just to make sure you noticed, look at the end date, year is 2038!
Apparently these downtimes keep getting created because there was an outage last week and no alerts were sent, but I see no history of the downtime before today either....
Apparently this happened when doing a mass acknowledge and schedule downtime.
2 of XI5.6.14 Prod/DR/DEV - Nagios LogServer 2 Nodes
See my projects on the Exchange at BanditBBS - Also check out my Nagios stuff on my personal page at Bandit's Home and at github
BanditBBS wrote:Also, just to make sure you noticed, look at the end date, year is 2038!
Apparently these downtimes keep getting created because there was an outage last week and no alerts were sent, but I see no history of the downtime before today either....
Apparently this happened when doing a mass acknowledge and schedule downtime.
Actually, looking at it again, it's possible that Mesa de Ayuda entered the downtime with a time that started before present and ended in 2038?
Have you contacted them to be sure they entered the times correctly?
I'm 100% sure they screwed up back on July 16th with a "mass acknowledge and schedule downtime" but how they screwed up, I am not sure.
Check this history on one of the services and look at the ack times and the downtime start times.....
Annotation 2019-09-03 123725.jpg
You do not have the required permissions to view the files attached to this post.
2 of XI5.6.14 Prod/DR/DEV - Nagios LogServer 2 Nodes
See my projects on the Exchange at BanditBBS - Also check out my Nagios stuff on my personal page at Bandit's Home and at github
Nope, just the items I expect to see, none of the mysterious ones for random service are shown there.
2 of XI5.6.14 Prod/DR/DEV - Nagios LogServer 2 Nodes
See my projects on the Exchange at BanditBBS - Also check out my Nagios stuff on my personal page at Bandit's Home and at github
The top two comments are updated with the current date/time whenever an apply configuration happens but the start and end date of the downtime stays the same. I just need ot find a way to remove these garbage downtimes and smack the user and tell them to not use ack and schedule downtime again!
2 of XI5.6.14 Prod/DR/DEV - Nagios LogServer 2 Nodes
See my projects on the Exchange at BanditBBS - Also check out my Nagios stuff on my personal page at Bandit's Home and at github
