Upgrade mysql version
This would probably make sense on Amazon EC2 instance where it comes by default with
mysql 5.5, as of this writing, and you want to upgrade mysql to the next version.
In this example I have used version 5.5 for the upgrade mysql example. But, technically the methodology would work for other versions as well unless mysql drastically changes folder locations.
How to upgrade mysql from 5.5 to 5.6
First go ahead and move the mysql 5.5 to new folder
sudo mv /var/lib/mysql /var/lib/mysql55
Then grab the tar from mysql download page [Here]
Once you download the tar file containing the new mysql version do the following commands on your terminal.
sudo tar -xvf yourDownloadedTar.tar
sudo rpm -ivh MySQL-shared-5.6.17-1.el6.x86_64.rpm
sudo rpm -ivh MySQL-client-5.6.17-1.el6.x86_64.rpm
sudo rpm -ivh MySQL-server-5.6.17-1.el6.x86_64.rpm
This would upgrade your current mysql version to mysql 5.6 or which ever is the new mysql version.
Then restart mysql for the change to take effect.
Am fighting to install my application on Amazon EC2.. I installed the mongo and php mongo driver then restarted apache to get the above error message.
The problem is loading precedence. Mongo, which is dependent on json.so, is being loaded ahead of the json.so hence crying over ‘Where Is My JSON.so ehiehiehi’
The fix would be to make sure we are loading json first before the mongo – actually this would be hte problem on while loading memcache as well..
On php.ini –
Right above the extension=mongo.so, add extension=json.so
Usually json.so will be loaded through its own ini file json.ini
On Redhat Linux it would be inside
So, go to the json.ini and comment the extension=json.so line
restart httpd/apache and
Installing CLI gems will be through yum, so for the case of the git it will be:
sudo yum install git
Trying to SSH into the Amazone EC2 and getting the above error? it has something to do with lesser permission on the pem file.
All you have to do is change the permission as
sudo chmod 400 /path/to/your/file.pem
Then you can follow the usual ssh -i file.pem ec2-user@your-v-server..