Page 1 of 1
Monitor Engine issue
Posted: Mon Jul 20, 2020 10:15 pm
by tpwebb
From recommendation of previous post, I have created a new entry
For the monitoring engine not starting issue, what errors are you seeing and where exactly? Try starting it directly on the command line with:
Code: Select all
/usr/local/nagios/bin/nagios /usr/local/nagios/etc/nagios.cfg
I have attached the profile and the session txt file from the above command
Regards
Terrence
Moderator's Note: The profile has been shared with the support team but has been removed from the public forum.
Re: Monitor Engine issue
Posted: Tue Jul 21, 2020 4:28 pm
by benjaminsmith
Hi Terrace,
Looking over the logs in the profile, I noticed that SELinux is enabled on this server, and that's not compatible with Nagios XI.
SELinux policy enabled; httpd running as context system_u:system_r:httpd_t:s0
Lets disable that and run a full re-start, then let me know if the issue is resolved.
Disable SELinux on CentOS 7 / RHEL 7 / Fedora Linux
The run through the following commands to do a full restart:
Code: Select all
systemctl stop crond
systemctl stop npcd
systemctl stop nagios
pkill -9 -u nagios
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
systemctl restart mariadb
systemctl start nagios
systemctl start npcd
systemctl start crond
If you're still having issues, please attach the database log to the ticket. Thanks, Benjamin
Reference:
Nagios XI Log Locations and Descriptions
Re: Monitor Engine issue
Posted: Wed Jul 22, 2020 12:42 am
by tpwebb
Hello,
I have verified that SELinux is disabled, and ensured it is disabled in the
SELinux status: disabled
[root@nagios mysql]# getenforce
Disabled
[root@nagios mysql]#
I have also checked the file "/etc/selinux/config" and it is disabled.
The log still shows the SELinux policy is enabled
The database log file is below
mysqld.zip
Regards
Terrence.
Re: Monitor Engine issue
Posted: Wed Jul 22, 2020 3:37 pm
by benjaminsmith
Hi Terrence,
Thanks for the logs. Actually, the current database log does look better, I'm not seeing the following error in that one:
Code: Select all
2020-07-20T07:35:22.976508Z 0 [Warning] [MY-010909] [Server] /usr/libexec/mysqld: Forcing close of thread 415 user: 'ndoutils'.
Have you noticed any improvement or is the monitoring engine still stopping? One thing I noticed the following on the command subsystem log:
Code: Select all
usr/local/nagios/etc/hosts: Cannot utime: Operation not permitted
Log in as root and run the following script:
Code: Select all
/usr/local/nagiosxi/scripts/reset_config_perms.sh
Also, let's check the max connection on the database, what is the output to the following commands:
Code: Select all
mysql -uroot -pnagiosxi -e "show variables like 'max_connections';"
mysql -uroot -pnagiosxi -e "show global status like 'Max_used_connections';"
Can you send us an updated profile, I'd like to see if the load has come down and check the logs once more. If this is affecting your monitoring, we can also roll back ndo if necessary, please let me know.