Nagios Support Forum

I've repeatedly reconfigured services thresholds for MSSQL Server, so that the status is not critical.
Nagios keeps ignoring my changes that I make after going to Home Dashboard -> Service -> Critical, click on a service, go to configure, re-configure this service -> Monitoring, make changes to Monitor the service with this command: (Advanced users only), and click update.

I've changed Cache Object Count to warning 2000 and critical 5000 from the defaults of 10 and 20 a number of times. Nagios GUI keeps showing them as 10 and 20. If I use the Nagios Core Config Manager, it may show the edits.

I've already deleted the host once because of false critical alerts, and tried importing it. It seems like Nagios XI will only pick up the threshold changes made on the import before I have a baseline. I also was unable to delete the host directly due to whatever bug. I had to manually delete every service first, before I could the host.

Any ideas on how to resolve when I add back the host? I actually used Nagios XI a few years ago, so I am not an entirely new user.

Hi @CAUARqq6815IeV9X,

Can you advise what Linux distro you have your XI system installed on, and what version of XI you are running? When you click the Update button after making your Service configuration change, what happens next?

Debian 12 bookworm
Nagios XI 2024R1.3.2

Configuration applied successfully and backend was restarted.
Then if I go back to the same service and go to re-configure it again the command is exactly the same before I made changes.

If I go to Nagios Core manager from there, I can find the changes I made, and restart Nagios core.

Even if I manually shutdown and restart, the service stays as critical based on the old threshold instead of the threshold I set.

The only way I've managed to get some of the alarms off is be deleting all alarms, deleting the host, and using a wizard again with new thresholds. I still have a dozen service alarms that I need to updated thresholds on unfortunately.

I'm wondering if you're encountering a problem with the configuration not being applied correctly.

https://support.nagios.com/kb/article/v ... s%20column.

Have a look here for how to check the status of the configuration and whether there were nay problems with the configuration you applied.

Yes, the configurations may not be applied correctly.

I also was unable to delete the host directly due to whatever bug. I had to manually delete every service first, before I could the host.

This, along with the rest of your issues, does make it sound like there is something strange going on with your Nagios Core configuration. I believe the next best step for you to resolve this issue would be to open a case with our Support department and send in a Profile of your system (Admin>System Config>System Profile).

Our Support technicians will be better suited to a deep dive into your system to determine the root cause of this issue.

I think you may have the same issue I was coming on here to post a case about. Since the latest upgrade I have made changes and it will not apply. I found if you go into CCM for one of the changes you made that lists as not applied, make not active and save, edit again and make active and save again. You will now be able to apply changes and ALL the outstanding changes will apply and not just the one you have been working with.



I will log a case when i get time soon so I can include more detail but saving changes has definitely been broken.

Cheers

Thanks, I tried a complete reinstall first to see if it will solve the issue. I normally do not install standard system tools, and installed those first before the NagiosXI install. I still had to install rpm and curl before running the installation on Debian 12.

Unfortunately, I still had the problem, and may need to contact support.

Thanks Darrenh. I am using the free version, and don't want to start a trial to avoid stepping on any toes in my organization. I wanted to demo this to a peer inside my firm who should be running nagios or something similar, but he would be the one to start a trial.

Hi,

I will explain my issue which sounds like yours but with more detail you can decide.

If I (scrap this - use the bulk edit or) manually change a setting of an established monitor and save and apply i find the monitor has not applied and it is still monitoring using the old values. The way I have worked around it because this is new with this release is I go to CCM, core config manager, find the monitor, edit it and untick Active and save. Edit it again and tick to make active and click save. Now when you "apply configuration" the changes will be applied and new values active.

You definitely should not need to reinstall or run the wizard again.

Also deleting the services for a host before being able to delete the host is normal behaviour for Nagios.

A problem with the wizard I have been meaning to highlight in the forum is that when you run it again for a host it does not remember the existing settings, so you are starting from scratch. this is annoying if you monitor a lot of services or processes as you need to set them up again. my 2c.

Good luck with the sneaky trial.