This method that I use proven as alternate solution to repair MySQL. As we all know if anything problem with InnoDB database corruption the whole MySQL database will down. My method will change the InnoDB database engine to MyISAM or at least reduce the amount of database which is using InnoDB engine.
Recently we have permission issue with one of our server. Not sure what cause the change but all the files and folders permission are wrong.
Luckily we found the way on how to recover the server permission issue without to format the server.
Just follow this steps.
Sometimes monitoring server that use SNMP to monitor the service will show service down even though the service is not down. This is because of UDP flood to SNMP service triggering the false alarm. The port flooding causing monitoring server failed to retrieve information from the problem server.
The only purpose for me to install the program is to install Clusterssh to manage multiple ssh session in one time.
In this simple guide I assume that Xming server have been installed and running.
For those who don’t know what is Xming server please refer Xming project website.
It actually X server implementation for Windows.
One of the server have problem with MySQL. The MySQL table cannot edit at all. Restart the MySQL does not resolve the issue.
It turn out that the problem come from tmp folder.
So stop the MySQL first.
Recently there are few of our server overloaded because of Softaculous.
Not sure what trigger the overload but reinstall the software seem managed to solve the issue.
We have install our server with process monitoring script. When ever there are many process running exceeded define volume the notification will be sent to our report email.