On my server I have 6 MySQL databases. They all power WordPress websites. For some reason, 2 of these databases are not accessible. To my knowledge they use INNODB, but I can't confirm it as even doing a:
mysql> use INFORMATION_SCHEMA;
mysql> SELECT * FROM TABLES;
hangs on me. The working databases seem fine (at least the websites are online). When I tried to access the bad database websites, it will just keep spinning.
If I do a:
mysql> use rbb;
mysql> SELECT * FROM wp_posts;
It will just hang.
My server is running CentOS 6.2 and up to now i've had no issues.
Any pointers would be much appreciated. I have no idea what to do next.
Even opening a Sequel Pro to the server hangs the application.
If I try a query and then check the process list in another connection, it shows:
+----+------+-----------+-----+---------+------+----------------+------------------------+
| Id | User | Host | db | Command | Time | State | Info |
+----+------+-----------+-----+---------+------+----------------+------------------------+
| 10 | root | localhost | rbb | Query | 45 | Opening tables | SELECT * FROM wp_users |
MySQL Version is 5.5.28-log:
mysql> SELECT @@version;
+------------+
| @@version |
+------------+
| 5.5.28-log |
+------------+
1 row in set (0.00 sec)
I was experimenting about a year ago with ClouSE, but haven't used this since. My error log does report this, however.
131207 20:49:38 [ERROR] ClouSE: S3 listObjects for 'hondurasproject' failed. SSL certificate problem, verify that the CA cert is OK. Details:
error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed.
I have tried a few times to restart the server, but it hasn't helped.
Server disk space is looking good. 66G is available. Output below:
[root@server log]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/xvda1 91G 21G 66G 24% /
tmpfs 1.9G 0 1.9G 0% /dev/shm
Best Answer
Yes, WordPress uses the default storage engine (which is InnoDB since MySQL 5.5).
I'm not sure I understand the problem. Can you execute the SELECT using the mysql command client? If you can, the problem is in the GUIs you use.
If you cannot (which means that you will receive an error, I think) you should investigate the error log. The only possible problem I can think now is a damaged table (REPAIR TABLE should solve the problem), but the error log should give you the exact answer.