Hopefully this will help someone else having the same pain. # This was resolved by logging into mysql and running: # at this point my wordpress site stated error connecting to database. # remove all STATS_PERSISTENT clauses on table creation statments # manually update the all-databases.sql file and Sudo apt-get install mysql-server mysql-client mysql-common php5-mysql # I had to remove the mysql files as well you find you need to start MySQL as well, you can just insert mysqld or mysql. ![]() # remove a flag that would prevent the installation 1 port 80 : Connection refused Closing connection 0 curl: (7) Failed to. Rm /etc/apt//ondrej-(mysql something please check) # Remove mysql 5.6 from debs (otherwise it will reinstall 5.6) Sudo apt-get remove -purge mysql-server mysql-client mysql-common # we are going to remove the mysql files so don't skip this) However it wasn't straight forward so here is what I had to do: # Manually get mysql running if it is not In the end I downgraded to mysql 5.5 which comes when you would normally perform a sudo apt-get install mysql-server command. This was from Kyle C's answer (except with mysqld instead of mysql). Sudo chown mysql /var/run/mysqld/mysql.sock The symptoms were the that the mysql.sock file at /var/run/mysqld/mysql.sock would get removed but never recreated, so I was having to manually run the following commands every time mysql was updated or the server rebooted: sudo touch /var/run/mysqld/mysql.sock The same problem plagued me for ages on an Ubuntu 12.04 Digital Ocean VPS with mysql 5.6 installed from a PPA. Note: If you had mysql extension for php, you will need to reinstall this too. Hope this helps, and thought I might add after doing this all my databases and tables where still available, however I did have to recreate the users and passwords for those databases. You should see mysql start/running, process xxxxx MySQL should now be running, you can check this by doing the following: sudo service mysql status Install MySQL sudo apt-get install mysql-server mysql-client Optionally you may use aptitude, by replacing apt-get -purge with aptitude Remove MySQL sudo apt-get -purge remove mysql-server ![]() The steps to completely removing and reinstalling MySQL are as follows: What I had to do was completely reinstall MySQL, to do this you will need to use the sudo command. This did NOT fix the problem for me! But it may for some. If you find that your tables are in fact corrupt, there are several steps that can be taken to fix them. ![]() To start in safe mode, run: sudo /usr/bin/mysqldsafe -usermysql -skip-grant-tables. Sudo chown mysql /var/run/mysql/mysql.sock Important Running MySQL in safemode lowers the security settings, potentially allowing another person access to your data. Author: Mellnik Current Version: 1. I might create MellAdmin 2.0 with MySQL R38 in future but no promisses. This could be an issue so you may check there and if its missing you can replace it by doing the following: sudo touch /var/run/mysql/mysql.sock This script is outdated and I do not give support anymore. I tried several different methods to get it resolved, I did notice that /var/run/mysql/mysql.sock was missing. Anyway after trying to change them back to the default setting MySQL still would not start. Please use the full name instead.ġ31216 22:40:25 Plugin 'FEDERATED' is disabled.ġ31216 22:40:25 InnoDB: The InnoDB memory heap is disabledġ31216 22:40:25 InnoDB: Mutexes and rw_locks use GCC atomic builtinsġ31216 22:40:25 InnoDB: Compressed tables use zlib 1.2.8ġ31216 22:40:25 InnoDB: Using Linux native AIOġ31216 22:40:25 InnoDB: Initializing buffer pool, size = 128.0Mġ31216 22:40:25 InnoDB: Completed initialization of buffer poolġ31216 22:40:25 InnoDB: highest supported file format is Barracuda.ġ31216 22:40:26 InnoDB: Waiting for the background threads to startġ31216 22:40:27 InnoDB: 5.5.34 started log sequence number 1609544ġ31216 22:40:27 /usr/sbin/mysqld: unknown variable 'default-character-set=utf8'ġ31216 22:40:27 InnoDB: Starting shutdown.ġ31216 22:40:27 InnoDB: Shutdown completed log sequence number 1609544ġ31216 22:40:27 /usr/sbin/mysqld: Shutdown completeġ31216 22:40:27 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.On Ubuntu 12.04 I had this same problem after changing buffer sizes in /etc/mysql/my.cnf file, I think I got a little carried away. Please use the full name instead.ġ31216 22:40:25 Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. But after I restart the computer, when I restart MySQL, it failed, and the log from /var/log/mysql is: 31216 22:40:25 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysqlġ31216 22:40:25 Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Today I install MySQL on my Ubuntu 13.10, and it worked very well.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |