Unable to acknowledge or schedule downtime

[TBT]

It appears the issue has appeared again. We will proceed with the vacuum and report back.

[TBT]

Ran the following as suggested:

PostgreSQL 8.4.20

echo "vacuum;vacuum analyze;"|psql nagiosxi postgres
service postgresql restart

Tested acknowledgment immediately after, issue remains as initially reported, please advise.

[npolovenko]

@TBT, Based on the log files, it looks like you have too many eventman.php crons running. That may be causing your issue. Please run the following commands in order:

Code: Select all

service npcd stop
service nagios stop
service ndo2db stop
if grep --quiet pgsql /usr/local/nagiosxi/html/config.inc.php; then service postgresql stop; fi;
service mysqld restart
rm -rf /usr/local/nagios/var/rw/nagios.cmd
rm -rf /usr/local/nagios/var/nagios.lock
rm -rf /usr/local/nagios/var/ndo.sock
rm -rf /usr/local/nagios/var/ndo2db.lock
rm -rf /usr/local/nagiosxi/var/reconfigure_nagios.lock
rm -rf /var/lib/mrtg/mrtg_l
for i in `ipcs -q | grep nagios |awk '{print $2}'`; do ipcrm -q $i; done
pkill -9 -u nagios
if grep --quiet pgsql /usr/local/nagiosxi/html/config.inc.php; then service postgresql start; fi;
service httpd restart
service ndo2db start
service nagios start
service npcd start
service crond restart

Or a quick alternative solution would be to restart the server -> shutdown -r
After that please check if the problem is still there, and if it is please run: ps -ef and send us the output.
Thank you.

[TBT]

After a reboot, the issue remains as reported.

Oddly enough, a technician was able to acknowledge an alarm this morning prior to any action on my part. Roughly 2 hours later, I was unsuccessful with acknowledging an alarm, both prior to and after the reboot. Keeping in mind that the network element in alarm state was different from the one that was successful.

[npolovenko]

@TBT, I see. I think we need to escalate this issue to a support ticket. Please open one here: https://support.nagios.com/tickets/
Our technicians will give it a second look and possibly schedule a remote session to resolve this as quickly as possible.