RESOLVED: Downtime comment bug?

[mcdonamw]

I just noticed a strange issue. I was looking at history for a couple of hosts today and noticed they all referenced the same 3 comments that were all posted today. One of the comments was supposedly posted by me, but I was not even in Nagios at time of the posts. Another comment posted by a colleague at same exact time. And a third posted by our third party MSP that manages patches on these systems, at the same exact time as the others.

The comments by me and my colleague suggest the hosts have scheduled downtime for tomorrow night/morning during specific hours.

When I look at all scheduled downtime, the only downtime scheduled are two recurring schedules. One schedule created by myself for the CPU service monitor for two specific hosts between 7am-9am. The other schedule is also a daily schedule but was created by my colleague and it's tied to a specific host group that has been confirmed not to contain any of these hosts.

Neither of these schedules should apply to any of the hosts I'm inspecting, but the history for EVERY host in my environment seemingly reflects the comments regarding these schedules. I don't understand why.

Further, the third comment is a comment by our MSP that manages patching for all hosts, but I cannot find any scheduled downtime that could be attributed as there is no other scheduled/recurring downtime. As such I don't know where this comment could even be coming from.

I feel as if I've discovered some sort of bug. Thoughts?

Nagios_ExampleHostWithIssue.png

RecurringDowntime.png

[lgute]

Hi @mcdonamw,

Thanks for reaching out.

What version of XI are you running?

We will dig into this and see if we can duplicate the behavior.

[mcdonamw]

We are on Nagios XI 2024R1.3.2

Also, I just noticed that it appears this displayed information isn't necessarily persistent, as if it's dynamically being generated each day. I looked at the same host from the original screenshot and the information from 4-28 is no longer listed in history. Instead, it just shows data from 4-29 and 4-30. I'm confused why today it's showing entries for the host plus 2 services this time but not originally and further why the event from MSP is showing the day prior in this screenshot vs the same timestamp as the other events in original screenshot.

Nagios_ExampleHostWithIssue_daysLater.png

[onegative]

Seeing this has me concerned...

I opened a support ticket regard this same behavior on my v5.11.3 instances. I have only Host Group Scheduled Downtime entries and I have the same type behavior. The support tech indicated that there is some type of bug ( https://github.com/NagiosEnterprises/na ... issues/910 ) and recommended me upgrading...so I see your version as 2024R1.3.2 having the same behavior...

duplicate_sched_downtime.png

duplicate_sched_downtime_2.png

What's going on here???
Danny

[lgute]

Hi @onegative and @mcdonamw,

Thank you for the information. These are 2 separate issues.

The History tab issue will be fixed in the next release of XI 2024R1.4.2.

The Core Issue was fixed in the Core 4.5.2 release. Core 4.5.3 was included in the XI 2024R1.2 release, so if you upgrade to XI 2024R1.2 you will get the fix.

[lgute]

@mcdonamw,

There is a hotfix for the History tab, if you don't want to wait.

In file /usr/local/nagiosxi/html/includes/components/historytab/historytab_content.php go to line 60 and add this line, before the GROUP BY:

Code: Select all

 "WHERE NC.object_id = $object_id ".

Then save the file and restart apache.

[onegative]

Thanks for this information...I'll give it a try.
Danny

[mcdonamw]

@mcdonamw,

There is a hotfix for the History tab, if you don't want to wait.

In file /usr/local/nagiosxi/html/includes/components/historytab/historytab_content.php go to line 60 and add this line, before the GROUP BY:

Code: Select all

 "WHERE NC.object_id = $object_id ".

Then save the file and restart apache.

I'll give it a try next week. Is there an ETA for the official updated release?

[sgardil]

I'll give it a try next week. Is there an ETA for the official updated release?

Currently we don't have an estimated time frame we can give out. It should be our next release, however there is a lot of changes in this release so we cant give a time frame on how long it will take for this release to be ready. Our socials will post on the release and if you are currently up to date you can check for updates in XI to see if it has been released.

[llucklinn]

The term could relate to issues like comments not loading, disappearing, or causing crashes during server downtime or maintenance, but the exact nature depends on the platform. Ragdoll Hit