自从我上周五进行了常规的软件包更新后,我的网络服务器出现了一个相当棘手的问题.我在使用mysql_connect()时遇到错误.
Warning: mysql_connect(): Headers and client library minor version mismatch. Headers:50532 Library:100005 in /srv/www/***/wp-includes/wp-db.php on line 1142
当我运行php -i时,我得到:
mysqli
MysqlI Support => enabled
Client API library version => 10.0.5-MariaDB
Client API header version => 5.5.32
apt-get install mariadb*
已安装以下软件包的结果:
libmariadbclient18 is already the newest version.
libmariadbclient18 set to manually installed.
mariadb-client is already the newest version.
mariadb-client-10.0 is already the newest version.
mariadb-client-10.0 set to manually installed.
mariadb-client-core-10.0 is already the newest version.
mariadb-client-core-10.0 set to manually installed.
mariadb-common …我在跑:
MariaDB 10.0.5
Ubuntu 12.04 LTS
Both up to the latest patch level as per last Friday
我之前的问题已经变得非常糟糕:
http://stackoverflow.com/questions/19910996/mysql-connect-headers-and-client-library-minor-version-mismatch-library10000
这导致了大量的损坏,因为我复制并删除了我的ibdata1,ib_logfile0和ib_logfile1以解决上述问题的症状.我想,当我下次启动mariadb服务时,这个问题就开始了.当我尝试选择一个受影响的表或运行mysqldump时,我得到以下内容:
mysqldump -u backupusr -p'somepass' --all-databases > dump.sql
mysqldump: Got error: 1932: "Table 'some_db.dw_commentmeta' doesn't exist in engine" when using LOCK TABLES
幸运的是(幸运的是)我的大型制作客户网站的数据仍然完好无损且网站在线.虽然该DB中至少有一个损坏的表.现在恢复我所有其他网站的数据库.
我还有原始的ibdata1,ib_logfile0和ib_logfile1文件.当我将这些文件移回/ var/lib/mysql /时,mariaDB服务无法启动.
我尝试过的一件事就是按照以下方式强制进行InnoDB恢复:
http://dev.mysql.com/doc/refman/5.0/en/forcing-innodb-recovery.html
但那没有效果.之后我尝试使用Mysql升级工具强制查看是否可以修复表:
mysql_upgrade --password --force
FATAL ERROR: Upgrade failed
所以这并没有告诉我任何事情.接下来我使用了REPAIR TABLE和ALTER TABLE ENGINE命令:
http://dev.mysql.com/doc/refman/5.0/en/rebuilding-tables.html
改变发动机:
MariaDB [sictnl_db]> ALTER TABLE si_users ENGINE = MyISAM;
ERROR 1932 (42S02): Table 'sictnl_db.si_users' doesn't exist in engine
修理台:
MariaDB …