Page 2 of 3

Re: Fusion database lock issue

Posted: Tue Nov 06, 2018 7:40 am
by hbouma
Files sent in PM

Re: Fusion database lock issue

Posted: Tue Nov 06, 2018 9:39 am
by tgriep
Thanks. I received the files and shared them with the other Techs.

The only thing I found in the logs is a lot of failed authentication checks.
One of the accounts that is used to authentication to the Nagios servers is failing so can you find the server that is having the issue and fix the login issue?

Re: Fusion database lock issue

Posted: Tue Nov 06, 2018 10:09 am
by hbouma
I have looked through the passwords and tested them. It is complaining about 3 servers passwords. Each password entered is correct, but the tests don't work. My guess is that the failures are due to the special characters in the password. They all contain a #.

Is fusion unable to handle a password that has a #, and if so, do I need to update any Nagios files if I change the administrative password? Are there any other characters that Fusion cannot handle in the password that Nagios XI can handle?

Re: Fusion database lock issue

Posted: Tue Nov 06, 2018 12:02 pm
by tgriep
I asked about ant limitation on using special characters and the developers say they should work.
I did some testing and it seems that the issue seems to be with the "Test Fusion Settings" button
I added a # to one of the passwords and the Test button failed but the polling seemed to work.

I'll put in a Bug Fix for the test button but make sure you update the username, password and the Fusekey for those servers.

Another thing I saw is that the URL for some of the servers on the Fusion server were missing the trailing / . Update those as well.

Re: Fusion database lock issue

Posted: Tue Nov 06, 2018 12:07 pm
by hbouma
Ok, I updated all the URL's to have the trailing /. We will have to wait and see what happens with the database.

Re: Fusion database lock issue

Posted: Tue Nov 06, 2018 12:32 pm
by tgriep
What is happening is that the polling scripts that are run by cron are not exiting which is using up the memory.
Then when the kernel detects that the memory is getting tight, the Out of Memory killer goes and kills of the MYSQL server to free up memory so the system can continue to run.
I haven't found the errors that are causing the pollers to not exit so we may need to wait until it happens again.

Re: Fusion database lock issue

Posted: Tue Nov 06, 2018 12:47 pm
by hbouma
Is there something I should turn on to help capture some additional information if this happens again?

Re: Fusion database lock issue

Posted: Tue Nov 06, 2018 1:44 pm
by martinnick
Just to elaborate on the initial posting. This issue appears to be similar, (if not the very same) to a previous problem discussed in https://support.nagios.com/forum/viewto ... 17&t=50159 and subsequently worked with by one of the support engineers on ticket #100103 which was re-opened for that purpose. A Fusion component addon was ultimately supplied as part of the resolution after a few remote sessions with the engineer.

Re: Fusion database lock issue

Posted: Tue Nov 06, 2018 4:37 pm
by tgriep
Can you login to the Fusion server and go to the Admin > Manage Components menu, provide a screen capture of it and post it here?

Re: Fusion database lock issue

Posted: Tue Nov 06, 2018 4:42 pm
by tgriep
Try this, go the Admin > Manage Components menu and upload this zip file to the Fusion server.

Then let the system run for about an hour and run this command as root and post the output to the ticket.

Code: Select all

ps -ef --cols=300