I'm encountering an issue while trying to mute a notification for a service on my Nagios XI system. Despite my attempts, I was unable to mute it. Upon investigating, I observed an error message in the httpd error_logs from the backend. Does anyone know why this might be happening and how I can resolve this issue?
[Thu Aug 29 17:22:59.642767 2024] [:error] [pid 36088] [client 10.110.25.38:45610] PHP Notice: Trying to get property of non-object in /drbd/usr/local/nagiosxi/html/includes/components/xicore/status-object-detail.inc.php on line 1139, referer: http://localhost:80/nagiosxi/includes/components/xicore/status.php?show=services
[Thu Aug 29 17:22:59.642800 2024] [:error] [pid 36088] [client 10.110.25.38:45610] PHP Notice: Trying to get property of non-object in /drbd/usr/local/nagiosxi/html/includes/components/xicore/status-object-detail.inc.php on line 1139, referer: http://localhost:80/nagiosxi/includes/components/xicore/status.php?show=services
[Thu Aug 29 17:22:59.642804 2024] [:error] [pid 36088] [client 10.110.25.38:45610] PHP Warning: Invalid argument supplied for foreach() in /drbd/usr/local/nagiosxi/html/includes/components/xicore/status-object-detail.inc.php on line 1139, referer: http://localhost:80/nagiosxi/includes/components/xicore/status.php?show=services
Hmm, those are only warnings and notices - I'm not sure that's the root cause of your problem. What operating system and version of XI are you running? If it's an older version it may be a bug we have fixed by now. If it's a newer version I'll see if I can replicate the issue on my end to determine if it's an issue on your end or with XI itself.
Best Regards,
Cory Norell
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
@kenneth59
Look through the configuration and make sure you don't have "volatile" set to enabled for the service you're trying to mute.
I have run into this and other issues due to same setting.
Thank you for your response. I managed to find a workaround for my issue. My server is running on an older version of Nagios, and it seems the issue I'm facing has likely been addressed in the newer version.
Thank you for your response. I managed to find a workaround for my issue. My server is running on an older version of Nagios, and it seems the issue I'm facing has likely been addressed in the newer version.
Glad you found a fix. What was the work around you found if you don't mind sharing. It could help others if they run into a similar situation assuming they are on the same version. Obviously we recommend to update your system but we know not everyone wants to or has the ability to do so.
This method may not be the best approach, but it is a workable solution to address the issue.
Go to Core Config Manager.
Select the Service you want to stop.
Click on Alert Settings.
Under Notification Enabled, change the setting to Off.
Mute the alert.
Change the setting back to Skip.