Nagios Support Forum

I was able to fix this issue with the following methods: Permissions sudo permissions were not setup correctly to allow Nagios access to the script or executables the script wanted to call. There is more here, but basically, I did not verify that it was exactly the same as our NRPE plugin was setup....

I have a custom plugin that checks to see if Puppet is working on our servers. It fails with the error below. All other builtin NCPA plugins are working. I tried creating a /home/nagios directory with nagios permissions but then the script errors with other errors (/usr/local/ncpa/plugins/check_pupp...

Apologies for the delay. This thread can be considered resolved. See below for my best explanation of what happened and how I resolved it. tl;dr Perfdata directories were moved to a new host named Bad_Host. This was the name I chose when we had a service with a blank field in the name. We were unabl...

Thank you for the responses. It does not appear that we have the perfdata directory in the snapshot. To be clear, in this instance I am referencing "Configuration Snapshots." This could be my issue. Additionally, our backup link displays the "Error: This component requires php-pecl-ss...

We had an issue yesterday where we decided to restore from the previous nights snapshot. This was because we had a service that appeared to have blank fields. Editing the service and saving would only create a new service with blank fields while saving the old service id with the altered fields. Thi...

tgriep,

Thank you. That worked very well.

Sorry for the delay. I was on vacation for a few weeks and actually ended up drastically breaking our Nagios server for a few hours yesterday (separate issue).

There does not seem to be any items added in the Service State History for the service when I create a failure. There are leftover items from my previous day's testing that correlate with some of the passive check results I created on the service. The items that are reported are all reported as HARD...

We have a few services that do not trigger alerts when the host service has failed. These service monitors were fully functioning at some point and would send alerts when there was a failure. Recently we discovered this issue when a host was completely down and only a few alerts came in for some of ...

I just updated to the 5.5.1 release. I have the message with the red background "The update did not complete successfully. Please try updating manually." The logs from the update don't report any error. The install seems fine. Running "/usr/local/nagiosxi/scripts/repair_databases.sh&q...

I think we are settling on this code as a simple work around. We are using Puppet to deploy the update so it should be pretty smooth. Posting it here to help others and get feedback. Replace lines 74-78 with: free_version=`free -V | gawk '{print $4}'` free_requiredver=3.3.10 if [ "$(printf '%s\...