Tech

MySQL ERROR! The server quit without updating PID file

Neil Gee — Thu, 31 Oct 2013 09:05:45 +0000

ERROR! The server quit without updating PID file
ERROR! MySQL server PID file could not be found!

Getting these bad boy errors on your mysql on OSX, there seems to be lots of solutions about how to fix this, Google hell, this more than likely happens if mysql is running and the OS is updated like from OSX Mountain Lion to Mavericks.

The mysql.socket is no longer visible in /tmp eventhough mysql thinks it is. The .pid file in the mysql data folder is gone and mysql just wont behave without it.

So possible solutions are:

Remove /etc/my.cnf or just back it up for now:

sudo mv /etc/my.cnf /etc/my.cnf.bak

Another solution is remove any .err files in the data folder or create missing .pid ones that the error message warns:

neilg@[/usr/local/mysql/data]: sudo /usr/local/mysql/support-files/mysql.server start
Starting MySQL
. ERROR! The server quit without updating PID file (/usr/local/mysql/data/neils-iMac.local.pid).

So you could remove the .err files like so:

rm *.err /usr/local/mysql/data/

Not too sure about recreating the .pid file, i tried this and it just removed itself!

But these may not solve the issue, I found a clean install of the latest mysql will address the issue by installing all components from the dmg.

Download the latest mysql and pick the Mac OS X 10.7 (x86, 64-bit), DMG Archive version.

Install all components and restart, now you should have mysql server running again but now you will need to migrate the old data to the new. First up make sure mysql is not running either from System Prefs or the Terminal.

sudo /usr/local/mysql/support-files/mysql.server stop

Migrate Databases

The key directory from the previous mysql instance that needs to be copied is :

/usr/local/mysql-5.5.13-osx10.6-x86_64/data

So in this instance the previous mysql version was 5.5.13 - the steps are rename the new data directory and copy in the old one.

Change Name of newer data directory

sudo mv /usr/local/mysql-5.6.14-osx10.7-x86_64/data /usr/local/mysql-5.6.14-osx10.7-x86_64/dataold

Copy Old Databases into new location

sudo cp -rf /usr/local/mysql-5.5.13-osx10.6-x86_64/data /usr/local/mysql-5.6.10-osx10.7-x86_64/

Start Mysql

sudo /usr/local/mysql/support-files/mysql.server start

That should fix the issue

How to Install CloudFlare Apache Module on cPanel Server

gowranngee — Sat, 26 Oct 2013 05:21:25 +0000

Get the mod_cloudflare Apache module installed and configured on a cPanel server.

Download the Pearl installer script that will allow you to compile the Apache EasyScript to include the mod_cloudflare module

perl <(curl https://raw.github.com/tylerl/util/master/easyapache/cloudflare.pl) install

Next login to your cPanel server, go to EasyApache update script.

Move along the wizard until you get to the short options list or exhaustive list and select the Mod CloudFlare option.

Save and build the new profile.

Install Drush via PEAR on a cPanel Server

Neil Gee — Mon, 30 Sep 2013 05:46:04 +0000

How to install Drush via PEAR on a cPanel Server

Install PEAR

The first thing that you need to do is make sure that PEAR is running

pear version

If PEAR is not installed it can be easily added via EasyApache Update via WHM in the Exhaustive Options List, check the box and recompile to add in PEAR to your server.

Once you have PEAR installed, you need to get the PEAR user config file set up - go to your cPanel GUI interface and click on PHP PEAR Packages you will see a config-set screen display 'suceeded'

Now on the command line go to your home directory and see your PEAR config

cd

ls -la .pea*

-rw-r--r-- 1 letit letit 527 Dec 15 01:05 .pearrc

Link PEAR to the drush channel to download the package

pear channel-discover pear.drush.org

Output should be:

Adding Channel "pear.drush.org" succeeded

Discovery of channel "pear.drush.org" succeeded

Install drush

pear install drush/drush

Upgrading drush

For future upgrades just run

pear upgrade drush

For drush commands type drush and see what is available - otherwise check the drush website and a starting point for basic drush commands here.

Get Apache, MySQL, PHP and phpMyAdmin working on OSX 10.9 Mavericks

Neil Gee — Sat, 10 Aug 2013 07:42:10 +0000

Get your Local Web Development Server Up & Running on OSX 10.9 Mavericks

With the new OS out of the bag, getting the AMP stack running on OSX 10.9 Mavericks is is pretty much the same as on OS X Mountain Lion 10.8. This tutorial will go through the process on getting Apache, MySQL, PHP and phpMyAdmin running on the new Maverick Californian driven OS.

If you had your local development already set up in OSX 10.8 and simply did an upgrade to 10.9, your MySQL, Apache and phpMyAdmin settings should all be good, you just need to enable PHP

Apache/WebSharing

The web sharing option has not made it back in 10.9, which was previously a GUI option in System Preferences back in 10.7, but fear not Apache is installed ready to be switched on.

No Web Sharing Option in System Preferences

Apache is pre-installed in the OS and needs to be enabled via the command line - this needs to be done in Terminal which is found at /Applications/Utilities/Terminal

For those not familiar with the Terminal, it really isn't as intimidating as you may think, once launched you are faced with a command prompt waiting for your commands - just type/paste in a command and hit enter, some commands give you no response - it just means the command is done, other commands give you feedback - lets get to it....

to start it

sudo apachectl start

to stop it

sudo apachectl stop

to restart it

sudo apachectl restart

To find the Apache version

httpd -v

The version installed in OSX Mavericks is Apache/2.2.24

After starting Apache - test to see if the webserver is working in the browser - http://localhost - you should see the "It Works!" text.

Document Root

Document root is the location where the files are shared from the file system and is similar to the traditional names of 'public_html' and 'htdocs', OSX has historically had 2 web roots one at a system level and one at a user level - you can set both up or just run with one, the user level one allows multiple acounts to have their own web root whilst the system one is global for all users. It seems there is less effort from Apple in continuing with the user level one but it still can be set up with a couple of extra tweaks. It is easier to use the user level one as you don't have to keep on authenticating as an admin user.

System Level Web Root

- the default system document root is still found at -

http://localhost/

The files are shared in the filing system at -

/Library/WebServer/Documents/

User Level Root

The other web root direcroty which is missing by default is the '~/Sites' folder in the User account. You need to make a "Sites" folder at the root level of your account and then it will work. Upgrading from a previous OS X version preserves the Sites folder but removes the ability to web serve from it - this is where you need to add in a 'username.conf' file.

Create a Sites folder at the account root level

Check that you have a “username.conf” filed under:

/etc/apache2/users/

If you don’t (very likely), then create one named by the short username of the account with the suffix .conf, it's location and permissions/ownership is best tackled by using the Terminal, the text editor 'nano' would be the best tool to deal with this.

Launch Terminal, (Applications/Utilities), and follow the commands below, first one gets you to the right spot, 2nd one cracks open the text editor on the command line (swap 'username' with your account's shortname, if you don't know your account shortname type 'whoami' the Terminal prompt):

cd /etc/apache2/users

sudo nano username.conf

Then add the content below swapping in your 'username' in the code below:

<Directory "/Users/username/Sites/">
Options Indexes MultiViews
AllowOverride All
Order allow,deny
Allow from all
</Directory>

Permissions on the file should be:

-rw-r--r--   1 root  wheel  298 Jun 28 16:47 username.conf

If not you need to change...

sudo chmod 644 username.conf

Restart Apache for the new file to be read:

sudo apachectl restart

Then this user level document root will be viewable at:

http://localhost/~username/

Overide .htaccess

If you are going to use the document root at /Library/WebServer/Documents it is a good idea to allow any .htaccess files used to override the default settings - this can be accomplished by editing the httpd.conf file at line 217 and setting the AllowOverride to All and then restart Apache. This is already taken care of at the Sites level webroot by following the previous step.

/etc/apache2/httpd.conf

PHP

PHP 5.4.17 is loaded in the latest preview of OSX 10.9 Mavericks and needs to be turned on by uncommenting a line in the httpd.conf file.

sudo nano /etc/apache2/httpd.conf

Use "control" + "w" to search within nano and search for 'php' this will land you on the right line then uncomment the line (remove the #):

LoadModule php5_module libexec/apache2/libphp5.so

Write out and Save using the nano short cut keys at the bottom 'control o' and 'control x'

Reload apache to kick in

sudo apachectl restart

To see and test PHP, create a file name it "phpinfo.php" and file it in your document root with the contents below, then view it in a browser.

 <?php phpinfo(); ?>

MySQL

MySQL is again a missing component in OS X 10.9 and needs to be dowloaded from the MySQL site use the Mac OS X ver. 10.7 (x86, 64-bit), DMG Archive version (works fine on 10.9).

When downloading you don’t have to sign up, look for » No thanks, just take me to the downloads! - go straight to the download mirrors and download the software from a mirror which is closest to you.

Once downloaded install the 3 components. You may need to adjust the Security and Privacy System Pref to allow installs of 3rd party apps because of the new security feature of Mountain Lion known as the 'Gatekeeper', which keeps unscrupulous installer packages at bay.

To get around this without changing the global preferences (better!) right click or command click the .pkg installer to bring up the contextual menu and select open, then you get the warning - then click Open.

Install all 3...

mysql5.6.xxx.pkg
MySQLstartupitem.pkg
MySQLPrefPane

The first is the MySQL software, the 2nd item allows MySQL to start when the Mac is booted and the third is a System Preference that allows start/stop operation and a preference to enable it to start on boot.

You can start the MySQL server from the System Preferences or via the command line

sudo /usr/local/mysql/support-files/mysql.server start

To find the MySQL version from the terminal, type at the prompt:

/usr/local/mysql/bin/mysql -v

This also puts you in to an interactive dialogue with mySQL, type \q to exit.

After installation, in order to use mysql commands without typing the full path to the commands you need to add the mysql directory to your shell path, (optional step) this is done in your “.bash_profile” file in your home directory, if you don’t have that file just create it using vi or nano:

cd ; nano .bash_profile

export PATH="/usr/local/mysql/bin:$PATH"

The first command brings you to your home directory and opens the .bash_profile file or creates a new one if it doesn’t exist, then add in the line above which adds the mysql binary path to commands that you can run. Exit the file with type “control + x” and when prompted save the change by typing “y”. Last thing to do here is to reload the shell for the above to work straight away.

source ~/.bash_profile

mysql -v

You will get the version number again, just type “\q” to exit.

Set the MySQL root password

Note that this is not the same as the root or admin password of OSX - this is a unique password for the mysql root user, use one and remember/jot down somewhere what it is.

/usr/local/mysql/bin/mysqladmin -u root password 'yourpasswordhere'

Use the single 'quotes' surrounding the password

Fix the 2002 MySQL Socket error

Fix the looming 2002 socket error - which is linking where MySQL places the socket and where OSX thinks it should be, MySQL puts it in /tmp and OSX looks for it in /var/mysql the socket is a type of file that allows mysql client/server communication.

sudo mkdir /var/mysql

sudo ln -s /tmp/mysql.sock /var/mysql/mysql.sock

phpMyAdmin

phpMyAdmin is installed pretty much the same way as before.

Fix the 2002 socket error first if you haven't done so from the MySQL section-

sudo mkdir /var/mysql

sudo ln -s /tmp/mysql.sock /var/mysql/mysql.sock

Download phpMyAdmin, the zip package and move the folder with its contents into the document root level renaming folder to 'phpmyadmin'.

Make the config folder

mkdir ~/Sites/phpmyadmin/config

Change the permissions

chmod o+w ~/Sites/phpmyadmin/config

Run the set up in the browser

http://localhost/~username/phpmyadmin/setup/ or http://localhost/phpmyadmin/setup/

You need to create a new localhost mysql server connection, click new server.

Switch to the Authentication tab and set the local mysql root user and the password.
Add in the username “root” (maybe already populated, add in the password that you set up earlier for the MySQL root user set up, click on save and you are returned to the previous screen.
(This is not the OSX Admin or root password - it is the MySQL root user).

Make sure you click on save, then a config.inc.php is now in the /config directory of phpmyadmin directory, move this file to the root level of /phpmyadmin and then remove the now empty /config directory.

Now going to http://localhost/~username/phpmyadmin/ will now allow you to interact with your MySQL databases.

To upgrade phpmyadmin just download the latest version and copy the older 'config.inc.php' from the existing directory into the new folder and replace - backup the older one just in case.

Permissions

To run a website with no permission issues it is best to set the web root and its contents to be writeable by all, since it's a local development it should'nt be a security issue.

Lets say that you have a site in the User Sites folder at the following location ~/Sites/testsite you would set it to be writeable like so:

sudo chmod -R a+w ~/Sites/testsite

If you are concerned about security then instead of making it world writeable you can set the owner to be Apache _www but when working on files you would have to authenticate more as admin you are "not" the owner, you would do this like so:

sudo chown -R _www ~/Sites/testsite

This will set the contents recursively to be owned by the Apache user.

If you had the website stored at the System level Document root at say /Library/WebServer/Documents/testsite then it would have to be the latter:

sudo chown -R _www /Library/WebServer/Documents/testsite

So I think it's worth setting up the User level root as there is less authentication!

That's it! You now have the native AMP stack running ontop of the tamed Mavericks wave.

If you need virtual hosts configured I have added a separate guide on how to set these up in the Apache config files.

That's it! You now have the native AMP stack running ontop of OSX Mavericks.

Install WordPress on OS X Lion 10.7 and Mountain Lion 10.8

Neil Gee — Fri, 09 Aug 2013 06:03:28 +0000

If you want to get WordPress 3.6 quickly installed on your OS X machine for development or just to learn the software you can install all the necessary components including Apache, PHP, MySQL, phpMyAdmin and WordPress in one foul swoop without launching the Terminal. This type of install works best if you don't use Apple's built-in web sharing software.

Super fast and super easy from Bitnami that puts all the required software in one easy installation. This tutorial covers up to OS X Mountain Lion 10.8.4 and will work on OSX Mavericks 10.9

Download The Software

Get latest bundled installer here WordPress version 3.6 this will download the compressed zip to your download folder, decompress and leave the installer 'bitnami-wordpress-3.6-0-osx-x86-installer'

OSX 10.8 Mountain Lion Install Issue

Mountain Lion has extra security installed by default on installing non-Apple and non-App Store Applications, if you get the error below on the installation you need to adjust a System Preference. (OS X 10.7 Lion does not have this issue).

System Preferences > General > Allow Applications Downloaded from: Anywhere (as below)

Install The Software

Run the installer

Make sure both packages are checked

Leave the default location in the Applications folder

Set a login and password - this will set username and password for WordPress admin account and only password for phpMyAdmin (the username is root)

Install the files

Launch the WordPress application

Where Stuff Is

After you launch the application your browser will launch and you will be brought to the home location

The default home URL is http://127.0.0.1:8080

The default home for your WordPress is http://127.0.0.1:8080/wordpress

The default home for your WordPress Login is http://127.0.0.1:8080/wordpress/wp-admin or http://127.0.0.1:8080/wordpress/wp-login.php — the user is 'admin' and the password is what you set earlier

The WordPress installation comes with a few plugins pre-installed to cover SEO, Spam, Contact Forms and Google Analytics - that's it from here you get into your WordPress project

The default home for your phpMyAdmin is http://127.0.0.1:8080/phpmyadmin - the user is 'root' and the password is what you set earlier.
You don't need to go here unless you want to - the database that WordPress needs has already been created and is in use, it is named 'bitnami_wordpress'

On login to phpmyadmin you have access to the backend MySQL databases

All the files and software needed to make the installation are all filed in /Applications/wordpress-3.6-0 with the most important being 'manager-osx' if something isn't working check here to see if your websharing and database tools are running, which are Apache and MySQL - start the servers if required.

To Remove the Bitnami Stack and WordPress Installation

Run the /Applications/wordpress-3.6-0/uninstall application

Troubleshooting Port Numbers

The WordPress/Bitnami Stack uses port 8080 for websharing - if you are already using that port you are prompted for an alternative port number as it won't be able to bind to the default port, this also applies to SSL which uses 8443 and MySQL which uses port 3306.

If you want to install WordPress manually on a workstation that already has an AMP stack try this method.

Deleting Zombie Spam Users in Drupal

Neil Gee — Sat, 13 Jul 2013 05:39:53 +0000

Like a Zombie invasion anonymous spam Drupal users keep on coming, registering at the door with weird ass email addresses piling on the amount of users on your site with a status of blocked. Most of these blocked users are a result of a registration request at:

http://mydomain.com/user/register

One way to keep the hordes at bay is to use a Captcha style challenge for the user to answer on input. But even then it suprises how many get through and jam the people queues. You can mass delete these blocked Drupal users in one foul swoop in the database.

Crank open your Drupal database in the command line or phpMyAdmin and run:

DELETE FROM users WHERE `status` = 0 AND `uid` != 0;

Zombies are zapped - ready for the next onslaught!

To Future Proof

Instead of the Captcha module you can try the Mollom alternative which offers more of a whole spam monitoring service . Get the Mollom module and sign up for a Mollom account, single personal site is free. Get your keys from the Mollom account and enter them in your Mollom module. Then add your forms to be protected.

Then add a captcha to the form.

The Mollom service also provides text analysis spam methods for content submissions, blogs and forums and is not restricted to just the Drupal framework, it can also be used on WordPress as an alternative to Akismet, using Mollom hands down is the number 1 tool to combat spam.

Trimming the Fat on a Huge Drupal 7 Database

Neil Gee — Thu, 11 Jul 2013 00:29:51 +0000

Are you staring at a rather large Drupal database, why is it so big how did it get so huge?

Check for the Culprit Table

In phpMyAdmin open the database and sort by the size column

or directly in the Command Line via MySQL;

SELECT TABLE_NAME, table_rows, data_length, index_length, 
round(((data_length + index_length) / 1024 / 1024),2) "Size in MB"
FROM information_schema.TABLES WHERE table_schema = "DRUPAL_DATABASENAME_GOES_HERE";

Disable Access Log

A lot of the time one of the biggest tables will be 'accesslog' which is a log of visitor analytics similar to Google Analytics, so if you have your Google stuff in order no need for this right?

Access log is controlled at /admin/config/system/statistics and if your setting is set to never, the database is going to get huge, just change the setting to a lower value or just turn it off.

Database or System Logging

One other thing to keep the database size down is to turn off Drupal logging to the database and keep the logs just writing to the System Log instead.

Database logging off

System logging on

Now your Drupal 7 database will be a much more manageable size.

Making Images Responsive in Drupal 7, Remove inline width and height styling

Neil Gee — Sun, 12 May 2013 04:41:04 +0000

Making images in Drupal 7 optimised for responsive layout requires a CSS declaration to allow the scaling and a php function to remove existing inline styling width and height attributes.

CSS

The best CSS style on images to make them scale is

img {max-width:100px; height:auto;}

You may need to use the !important declaration if another CSS style is overriding.

It is best practice to optimise/size the image from the start at the widest width that you want it displayed as that way it will always fill its parent container reponsively but not exceed its physical width in pixels. (So you wont see it wider and abnormally big).

Preprocess PHP Function

By stripping out the inline width and height values of images that Drupal sets you will make your images responsive on more devices and older browsers. You can take advantage of one of the preprocessors that Drupal uses by adding a function in your template.php file in your theme folder, just add in the code below and swap out YOURTHEMENAME for your theme name.

// Remove Height and Width Inline Styles from Drupal Images
function YOURTHEMENAME_preprocess_image(&$variables) {
  foreach (array('width', 'height') as $key) {
    unset($variables[$key]);
  }
}

Thats all there is to it, now all your images will flex to fit.

Upgrade MySQL Database from 5.5 to 5.6 on OSX 10.8 Mountan Lion

Neil Gee — Tue, 09 Apr 2013 09:26:38 +0000

MySQL version 5.6.14 is available for download for OSX, a double click and install is available named Mac OS X ver. 10.7 (x86, 64-bit), DMG Archive. (Don't worry about the 10.7 naming, Works fine in OSX 10.9 and OSX 10.8)

Stop the MySQL Server

sudo /usr/local/mysql/support-files/mysql.server stop

Download and Launch the DMG

There is no upgrade option in the installer and you are presented with the 3 installations:

You need to install all the three installers.

Control/Right click the mysql-5.6...pkg to avoid the security GateKeeper. Follow the installation processes.

Location of MySQL 5.6 Data

MySQL data and files will be stored at:

/usr/local/mysql-5.6.14-osx10.7-x86_64

and an 'mysql' directory alias is also created that points to the same location

/usr/local/mysql

which points to

mysql -> mysql-5.6.14-osx10.7-x86_64

Your previous installation is maintained and will be filed in the same location with the appropraite version you were using, like so:

/usr/local/mysql-5.5.13-osx10.6-x86_6

What needs to be done is to migrate the database and tables to the new version.

Migrate Databases

The key directory from the previous instance that needs to be copied is :

/usr/local/mysql-5.5.13-osx10.6-x86_64/data

So in this instance the previous mysql version was 5.5.13 - rename the new data directory and copy in the old one and fix file ownership to MySQL:

Change Name of newer data directory

sudo mv /usr/local/mysql-5.6.14-osx10.7-x86_64/data /usr/local/mysql-5.6.14-osx10.7-x86_64/dataold

Copy Old Databases into new location

sudo cp -rf /usr/local/mysql-5.5.13-osx10.6-x86_64/data /usr/local/mysql-5.6.14-osx10.7-x86_64/

Set Correct Ownership to MySQL

sudo chown -R _mysql /usr/local/mysql-5.6.14-osx10.7-x86_64/data

Start MySQL and Repair

Now we need to start the MySQL database and run a repair/upgrade tool on the older databases

sudo /usr/local/mysql/support-files/mysql.server start

Run the Upgrade Tool

/usr/local/mysql/bin/mysql_upgrade

If you get errors on the first run, run the command again

Restart MySQL

sudo /usr/local/mysql/support-files/mysql.server restart

Check the Version

/usr/local/mysql/bin/mysql

Set MySQL Password

/usr/local/mysql/bin/mysqladmin -u root password 'yourpasswordhere'

my.cnf

In the latest version of MySQL 5.6 there is a default 'my.cnf' file that the database references that is now stored in:

/usr/local/mysql-5.6.14-osx10.7-x86_64/my.cnf

So if you have made any customisations to the behaviour of MySQL then these will now need to be added in the new my.cnf file and make a copy to /etc so any global changes will be read in when MySQL is launched.

How do I know if my website has been hacked?

Neil Gee — Thu, 14 Mar 2013 02:04:34 +0000

Check with Google

If you think that your site may have been hacked but are not too sure - you can check to see what Google thinks at the following URL

http://www.google.com/safebrowsing/diagnostic?site=mydomain.com

Just swap out mydomain.com with your actual domain name

What you will see from the returned page is if Google thinks its been hacked.

If your website has been hacked, you can see which pages have been infected via the Google Webmaster Tools, they hava a Malware section which will list all the pages - so if you haven't set your site up with Google WebMaster Tools do this as a first step. Once you have WebMaster Tools set up check the malware section to see what the damage is.

From this point you have a couple of choices based on your skill level, if you don't know how to fix the malware just copy the listed malware provided by Google and email it to your service provided and ask them to help or otherwise roll up your sleeves get access to your website via preferably the command line SSH or FTP and get ready to search and delete the malware code from the infected files.

Check with Sucuri

Sucuri will scan your site for malware and let you know is your CMS up to date and also advise if you are on blacklists.

Tech

MySQL ERROR! The server quit without updating PID file

Migrate Databases

Change Name of newer data directory

Copy Old Databases into new location

Start Mysql

That should fix the issue

How to Install CloudFlare Apache Module on cPanel Server

Install Drush via PEAR on a cPanel Server

Install PEAR

Link PEAR to the drush channel to download the package

Install drush

Upgrading drush

Tags:

Get Apache, MySQL, PHP and phpMyAdmin working on OSX 10.9 Mavericks

Get your Local Web Development Server Up & Running on OSX 10.9 Mavericks

Setting Stuff Up

Apache/WebSharing

Document Root

System Level Web Root

User Level Root

Overide .htaccess

PHP

MySQL

Set the MySQL root password

Fix the 2002 MySQL Socket error

phpMyAdmin

Permissions

Tags:

Install WordPress on OS X Lion 10.7 and Mountain Lion 10.8

Download The Software

OSX 10.8 Mountain Lion Install Issue

Install The Software

Where Stuff Is

To Remove the Bitnami Stack and WordPress Installation

Troubleshooting Port Numbers

Tags:

Deleting Zombie Spam Users in Drupal

To Future Proof

Tags:

Trimming the Fat on a Huge Drupal 7 Database

Check for the Culprit Table

Disable Access Log

Database or System Logging

Tags:

Making Images Responsive in Drupal 7, Remove inline width and height styling

CSS

Preprocess PHP Function

Tags:

Upgrade MySQL Database from 5.5 to 5.6 on OSX 10.8 Mountan Lion

Stop the MySQL Server

Download and Launch the DMG

Location of MySQL 5.6 Data

Migrate Databases

Change Name of newer data directory

Copy Old Databases into new location

Set Correct Ownership to MySQL

Start MySQL and Repair

Now we need to start the MySQL database and run a repair/upgrade tool on the older databases

Run the Upgrade Tool

Restart MySQL

Check the Version

Set MySQL Password

my.cnf

Tags:

How do I know if my website has been hacked?

Check with Google

Check with Sucuri

Tags: