Possible new Bug found on 2024R1.4

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
Post Reply
sgomeztd
Posts: 51
Joined: Tue Apr 30, 2019 11:00 am

Possible new Bug found on 2024R1.4

Post by sgomeztd »

I have updated to 2024R1.4.4 and while some of the issues with required field are fixed, it seems not of all them.

When creating a new service, if I assign the service to a hostgropup but do not select any hosts I get an error saying "Must select at least one host for a service definition! Select a host under Common settings -> Manage host"
User avatar
lgute
Posts: 410
Joined: Mon Apr 06, 2020 2:49 pm

Re: Possible new Bug found on 2024R1.4

Post by lgute »

Hi @sgomeztd,

Thanks for reaching out. Are you referring to this line in the changelog for XI 2024R1.4.4?
Fixed an issue where several required fields were not being validated in the CCM [GL:XI#1896] – BB
Please let us know if you have any other questions or concerns.

-Laura
bbahn
Posts: 379
Joined: Thu Jan 12, 2023 5:42 pm

Re: Possible new Bug found on 2024R1.4

Post by bbahn »

Hello @sgomeztd,

There were a couple more configurations that were missed in 1.4.4 that have been resolved in 2024R2. Please let us know if you find anything still broken.
Actively advancing awesome answers with ardent alliteration, aptly addressing all ambiguities. Amplify your acumen and avail our amicable assistance. Eagerly awaiting your astute assessments of our advice.
sgomeztd
Posts: 51
Joined: Tue Apr 30, 2019 11:00 am

Re: Possible new Bug found on 2024R1.4

Post by sgomeztd »

lgute wrote: Tue Jul 08, 2025 4:18 pm Hi @sgomeztd,

Thanks for reaching out. Are you referring to this line in the changelog for XI 2024R1.4.4?
Fixed an issue where several required fields were not being validated in the CCM [GL:XI#1896] – BB
Yes, I had 1.4.3 and was having issues with max_checks_attemps that was displaying errors that it was mandatory. That error got fixed with the update to 1.4.4 but I'm not sure if the error I mentioned was already on 1.4.3 or is something introduced on 1.4.4. Anyway, I'll update in a few weeks to 2024R2
Post Reply