After upgrade to XI 5.5.5, Monitoring Engine red
Posted: Fri Jun 07, 2019 9:30 am
This Nagios XI server was successfully upgraded from V5.4.1 to V5.5.5. After the upgrade, the Monitoring Engine, Performance Grapher, and Database Backend are all red in the XI System Component Status dashlet on the Admin -> System Status page.
From an SSH session command line, "systemctl status" commands show that nagios and ndo2db are both active.
We have done a reboot, and also tried this sequence of commands with no ending change in status:
This would be a good list of commands to run on XI server when the monitoring engine is down:
service crond stop
service npcd stop
service nagios stop
service ndo2db stop
pkill -9 -u nagios
for i in $(ipcs -q | grep nagios |awk '{print $2}'); do ipcrm -q $i; done
rm -rf /usr/local/nagiosxi/var/dbmaint.lock
rm -rf /usr/local/nagiosxi/var/event_handler.lock
rm -rf /usr/local/nagiosxi/scripts/reconfigure_nagios.lock
service mysqld restart
service ndo2db start
service nagios start
service npcd start
service crond start
What is next?
From an SSH session command line, "systemctl status" commands show that nagios and ndo2db are both active.
We have done a reboot, and also tried this sequence of commands with no ending change in status:
This would be a good list of commands to run on XI server when the monitoring engine is down:
service crond stop
service npcd stop
service nagios stop
service ndo2db stop
pkill -9 -u nagios
for i in $(ipcs -q | grep nagios |awk '{print $2}'); do ipcrm -q $i; done
rm -rf /usr/local/nagiosxi/var/dbmaint.lock
rm -rf /usr/local/nagiosxi/var/event_handler.lock
rm -rf /usr/local/nagiosxi/scripts/reconfigure_nagios.lock
service mysqld restart
service ndo2db start
service nagios start
service npcd start
service crond start
What is next?