Typically, when the Kernel Message queue does not clear out, it is caused by the MYSQL database not accepting the data fast enough or there was an issue that temporarily slowed the data flow like the max connections to the database was hit.
Open a root shell on the Nagios server and run the following commands. Get the /tmp/info.txt file and upload it to the post so we can see if the max connections are close and the sizes of the tables.
Code: Select all
mysql -u root -pnagiosxi -e "show global status like '%used_connections%'; show variables like 'max_connections';" >/tmp/info.txt
echo "SELECT table_schema as 'Database', table_name AS 'Table', round(((data_length + index_length) / 1024 / 1024), 2) 'Size in MB' FROM information_schema.TABLES ORDER BY (data_length + index_length) DESC;" |mysql -t -u root -pnagiosxi >>/tmp/info.txt
To see what happened, you would look in the /var/log/messages, the MYSQL log file and the Apace log files in the /var/log/httpd folder around the time the issue happened and look for MYSQL errors.
If you upload a System Profile here, we may be able to see the issue but the profile only goes so far back, we may not see it.
To get your system profile. Login to the Nagios XI GUI using a web browser.
Click the "Admin" > "System Profile" Menu
Click the "Download Profile" button
Save the profile.zip file and upload it to the forum post or PM it to me.
The
check_nrpe: Remote 10.6.155.39 does not support Version 3 Packets
messages do not get logged by nagios so they will not get put in the Kernel Message Queue.
Adding the -2 option to the command will only allow the plugin to use version 2 of the NRPE packets and should stop the messages.