Periodic issues with downtime and scheduling forced check

[WillemDH]

I have seen it happen multiple times over the last months. All of a sudden some user comes to me and complains downtime isn't working. The issue with the date format was one thing, but there seems to be another issue. This issue results in scheduling downtime not working for any user. it is also impossible to force schedule an immediate check with a quick action. The last few time I 'solved' the issue by rebooting the server. Today I solved it by restarting the nagios and crond service.

Is there any known issue which has the above symptoms? I've been searching through a few logs etc, btu didn't found anything useful. What else could I do to
1) detect this
2) resolve this

Grtz

Willem

[lmiltchev]

Are any of these users "AD/LDAP" users? Do they have capital letters in the usersnames? What's common among them (i.e. Date Format preferences, Security Settings, etc.)?

FYI, I imported an AD user (allcaps username) in one of my Nagios XI 5.2.3 test boxes, logged in as this user, and tried to schedule downtime. It failed...

We had a bug, where AD/LDAP users (with capital letters in the usernames) were not able to view reports. It is possible that scheduling downtime fails in a similar way. The bug will be fixed in the next release of XI. It is already fixed in our development revision. I am not able to recreate the issue in REV, only in the official release of 5.2.3 therefore I believe the issue has been fixed. However, I will do some more digging into this. Thanks!

[WillemDH]

98 % of my users are AD users. I changed their username to forname.surname in small leters when I created them. The date format has been set to the non-bugged YYYY-MM-DD HH:MM:SS several weeks ago. So normally it shouldn't be this bug. In fact I know for sure that setting downtime works untill some poitn in time where it fails for all users.
I did not see the issue re-appear since I created this thread. Please leave it open for a week or three. (no I will no respond to your responce.. )

[hsmith]

Please leave it open for a week or three.

Will do

[WillemDH]

This seems to be fixed with latest releases. Please close.