Page 1 of 1

Upgrade from 5.5.9 to 5.6.2 cause high loading to mariadb

Posted: Sun May 26, 2019 10:18 pm
by certizen
I upgraded the Nagios XI from 5.5.9 to 5.6.2 from the WebUI https://<hostname>/nagiosxi/admin/updates.php, the process was declared completed successfully, however, I found the mysql loading spiked to high level (>150%) all the time and it made the response to the web interface with serious lags.

I tried to restart the whole server and repair the database by script

Code: Select all

/usr/local/nagiosxi/scripts/repair_databases.sh
but nothing help. I have no choice to downgrade the server back to 5.5.9

Could the support please look into this case. Thanks.

Re: Upgrade from 5.5.9 to 5.6.2 cause high loading to mariad

Posted: Tue May 28, 2019 11:40 am
by benjaminsmith
Hi @certizen,

It would be helpful for us to review your system profile to help determine the possible source. Have you made any changes to the database setup or configuration that would differ from the default installation?

To send us 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 share in a private message or upload it to the post/ticket.

Re: Upgrade from 5.5.9 to 5.6.2 cause high loading to mariad

Posted: Tue May 28, 2019 10:38 pm
by certizen
I downgraded the Nagios XI back to 5.5.9 but the same problem exist. I sent the system profile to you and please have a look.
Thanks.

Re: Upgrade from 5.5.9 to 5.6.2 cause high loading to mariad

Posted: Tue May 28, 2019 10:56 pm
by certizen
It is frustrating that I cannot send private message to the support staff as I am not an active in the forum. As it is a customer support channel which only paid user are able to use, it is not rational to impose such restriction. Please review and change such policy to improvement the experience of customer support.

Re: Upgrade from 5.5.9 to 5.6.2 cause high loading to mariad

Posted: Wed May 29, 2019 10:10 am
by benjaminsmith
Hello @certizen,

Sorry about the frustration, we have the forums setup so the user must have a minimum number of posts to send a private message to avoid spam. I just checked your permissions and you should be able to send a private message now.

Also, I sent an email message as well.

Re: Upgrade from 5.5.9 to 5.6.2 cause high loading to mariad

Posted: Thu May 30, 2019 9:13 pm
by certizen
benjaminsmith wrote:Hello @certizen,

Sorry about the frustration, we have the forums setup so the user must have a minimum number of posts to send a private message to avoid spam. I just checked your permissions and you should be able to send a private message now.

Also, I sent an email message as well.
I already sent you the system profile through PM yesterday. Hope you can investigate and troubleshoot the problem soon.

Re: Upgrade from 5.5.9 to 5.6.2 cause high loading to mariad

Posted: Fri May 31, 2019 10:08 am
by benjaminsmith
Hello @certizen,

I've reviewed the system profile and have notice a few issues to address. First, the database log contains entries for crashed database tables, open the terminal as root and run the repair script:

Code: Select all

/usr/local/nagiosxi/scripts/repair_databases.sh
Reference: Repairing the Nagios Xi Databases

Secondly you are using a different port number other the default (80) for you server. You'll want to open up /usr/local/nagiosxi/html/config.inc.php and edit the following line to set the port number for subsystem calls.

Code: Select all

// Allow for different http port for subsystem calls
$cfg['port_number'] = 18443
Save and the re-start Apache. Next, go to Admin > System Config > System Settings and make sure the correct Program URL is set:
system-settings.png
Lastly, in the Apache error log, you are getting this warning message.
AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using 192.168.X.X . Set the 'ServerName' directive globally to suppress this message
You can set the /etc/hosts file to map the FQDN to the ip address ( see this) to correct this. After making those changes, let me know if the issue is resolved.