Nagios Support Forum

Ran the scripts and Everything appears normal again!

Thanks so much for the support!

It appears that one of the hosts in our Nagios XI system is in a weird state such that it is alerting, but is not in the CCM or in Nagios Core.

How do we remove this entry from Nagios XI?

I tried running the "repair_database.sh" script, but that didn't fix the problem.

Raised mem limit to 256MB. And set that one variable to 100,000.

Ta-da! It works!

Thanks.

I tailed the ssl_error_log and am getting this error message when refreshing the Mass Ack page: [Mon Dec 03 11:14:03 2018] [error] [client 10.1.xxx.7] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 1572827 bytes) in /usr/local/nagiosxi/html/includes/utils-xmlsta...

Nothing significant in the error_log: sudo tail -100 /var/log/httpd/error_log [Sun Dec 02 03:12:03 2018] [notice] Digest: generating secret for digest authentication ... [Sun Dec 02 03:12:03 2018] [notice] Digest: done [Sun Dec 02 03:12:03 2018] [notice] Apache/2.2.15 (Unix) DAV/2 PHP/5.3.3 mod_ssl/...

The Mass Acknowledge screen in NagiosXI was working fine. Then we added around 6000+ hosts to our NagiosXI instance of which there were about 100 or so which were in a DOWN state. I went to acknowledge these new hosts which were Down, but the Mass Acknowledge screen is now blank and doesn't display ...

Figured it out. Misconfigured filesystem permissions in /etc/snmp -- "nagios" group needs to be able to write to those files and directory. Strangely, NagiosXI gui never notes this. It seems to think that the action of creating a trap receiver was successful even though it was not. I'd def...

We're currently having great difficulty adding an SNMP trap. We're able to go thru the motions and NagiosXI reports that the SNMP trap is added, but nothing shows up in the /etc/snmp/snmptt.conf.nxti file All real and test SNMP traps with the OID fail to get picked up and always end up in the /var/l...

Any reason why the API version wasn't updated when breaking changes to the API were made? This is pretty standard operating procedure for something like this, right? This is a bit frustrating for us because we have to refactor our code base first before we can update to 5.5.x To make our life easier...

Hey guys,
We just upgraded our Nagios dev box to 5.5.5 and now all of our scripts which use the API are now broken. Thankfully we haven't upgraded our production box yet.

Did the API change? We're still using v1 API, so there shouldn't be any breaking changes, right?