110926 12:09:41 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
InnoDB: Last MySQL binlog file position 0 3329, file name /var/lib/mysql/mysql-bin.004279
110926 12:09:42 InnoDB: Started; log sequence number 46 4210009908
110926 12:09:42 [Note] Recovering after a crash using /var/lib/mysql/mysql-bin
110926 12:09:42 [Note] Starting crash recovery...
110926 12:09:42 [Note] Crash recovery finished.
110926 12:09:42 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.0.45-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution
来自网站管理员:
#2002 - The server is not responding (or the local MySQL server's socket is not correctly configured)
据我所知,每次我访问数据库时,它都会崩溃
答案1
由于 HDD 故障,MySQL 无法读取数据库的某些部分。
mysqldump 也会因此失败。
我最终编写了一个 Python 脚本来提取 Innodb 数据库中所有可读部分。
总之:
- 使用 dd 镜像硬盘(http://www.thegeekstuff.com/2010/10/dd-command-examples/)
- 通过 mysqldump 备份数据库(使用 python 脚本跳过不可读的内容)
- 导入到新系统
答案2
根据您的说法,您是否尝试过对数据库信息所在的磁盘执行强制完整 fsck?
答案3
重启 MySQL 后重启 webmin。根据你的发行版,可能需要
service webin restart
或者
/ect/init.d/webin restart