mysql输入用户密码之后出错

hjq20

[root@test2 ~]# mysql -u root -p
Enter password:
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (111)

为什么我输入mysql数据库数据root密码之后会突然出现这些提示了？
我无法进入mysql数据库，请高手指教。

[ 本帖最后由 hjq20 于 2008-12-10 13:41 编辑 ]

gamester88

/etc/rc.d/init.d/mysqld status看看启动没有

hjq20

我查看mysqld是这样的结果

[root@test2 ~]# /etc/rc.d/init.d/mysqld status
mysqld dead but subsys locked

luo118

service mysqld start

先启动mysql 你的mysql 都还没有启动.

hjq20

mysqld我不知道为何启动不起来。。。

[root@test2 ~]# service mysqld start
Timeout error occurred trying to start MySQL Daemon.
Starting MySQL:  [FAILED]

cuci

去看log，有错误日志

luo118

vi /var/log/mysql.log 看一下日志

hjq20

这是我在mysqld.log的近期log，我不知道具体哪里出错了？请大哥帮下忙。。谢谢080520 16:55:08  mysqld started
080520 16:55:08  InnoDB: Started; log sequence number 0 1614564119
/usr/libexec/mysqld: ready for connections.
Version: '4.1.20'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  Source distribution
080527 14:27:06 [Note] /usr/libexec/mysqld: Normal shutdown

080527 14:27:07  InnoDB: Starting shutdown...
080527 14:27:12  InnoDB: Shutdown completed; log sequence number 0 1614564119
080527 14:27:12 [Note] /usr/libexec/mysqld: Shutdown complete

080527 14:27:12  mysqld ended

080527 14:30:16  mysqld started
080527 14:30:17  InnoDB: Started; log sequence number 0 1614564119
/usr/libexec/mysqld: ready for connections.
Version: '4.1.20'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  Source distribution
081128 18:32:28  mysqld started
081128 18:32:29  InnoDB: Log file /tmp/ib_logfile0 did not exist: new to be created
InnoDB: Setting log file /tmp/ib_logfile0 size to 100 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Progress in MB: 100
081128 18:32:31  InnoDB: Log file /tmp/ib_logfile1 did not exist: new to be created
InnoDB: Setting log file /tmp/ib_logfile1 size to 100 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Progress in MB: 100
081128 18:32:33  InnoDB: Log file /tmp/ib_logfile2 did not exist: new to be created
InnoDB: Setting log file /tmp/ib_logfile2 size to 100 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Progress in MB: 100
081128 18:32:35  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
081128 18:32:36  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 1614564364.
InnoDB: Doing recovery: scanned up to log sequence number 0 1614564364
081128 18:32:36  InnoDB: Error: page 7 log sequence number 0 1614569752
InnoDB: is in the future! Current system log sequence number 0 1614564364.
InnoDB: Your database may be corrupt.
081128 18:32:36  InnoDB: Error: page 2 log sequence number 0 1614568148
InnoDB: is in the future! Current system log sequence number 0 1614564364.
InnoDB: Your database may be corrupt.
081128 18:32:36  InnoDB: Error: page 6 log sequence number 0 1614573092
InnoDB: is in the future! Current system log sequence number 0 1614564364.
InnoDB: Your database may be corrupt.
081128 18:32:36  InnoDB: Error: page 45 log sequence number 0 1614572268
InnoDB: is in the future! Current system log sequence number 0 1614564364.
InnoDB: Your database may be corrupt.
081128 18:32:36  InnoDB: Error: page 63 log sequence number 0 1614573092
InnoDB: is in the future! Current system log sequence number 0 1614564364.
InnoDB: Your database may be corrupt.
081128 18:32:36  InnoDB: Error: page 8 log sequence number 0 1614573155
InnoDB: is in the future! Current system log sequence number 0 1614564364.
InnoDB: Your database may be corrupt.
081128 18:32:36  InnoDB: Error: page 0 log sequence number 0 1614573145
InnoDB: is in the future! Current system log sequence number 0 1614564364.
InnoDB: Your database may be corrupt.
081128 18:32:36  InnoDB: Flushing modified pages from the buffer pool...
081128 18:32:36  InnoDB: Error: page 9 log sequence number 0 1614573150
InnoDB: is in the future! Current system log sequence number 0 1614564364.
InnoDB: Your database may be corrupt.
081128 18:32:36  InnoDB: Error: page 10 log sequence number 0 1614573145
InnoDB: is in the future! Current system log sequence number 0 1614564364.
InnoDB: Your database may be corrupt.
081128 18:32:36  InnoDB: Started; log sequence number 0 1614564364
081128 18:32:36  InnoDB: Error: page 60 log sequence number 0 1614573140
InnoDB: is in the future! Current system log sequence number 0 1614564364.
InnoDB: Your database may be corrupt.
081128 18:32:36  InnoDB: Error: page 61 log sequence number 0 1614573145
InnoDB: is in the future! Current system log sequence number 0 1614564364.
InnoDB: Your database may be corrupt.
081128 18:32:36  InnoDB: Error: page 62 log sequence number 0 1614573145
InnoDB: is in the future! Current system log sequence number 0 1614564364.
InnoDB: Your database may be corrupt.
/usr/libexec/mysqld: ready for connections.
Version: '4.1.20'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  Source distribution
081201 11:29:39 [Note] /usr/libexec/mysqld: Normal shutdown

081201 11:29:40  InnoDB: Starting shutdown...
081201 11:29:42  InnoDB: Shutdown completed; log sequence number 0 1614564364
081201 11:29:42 [Note] /usr/libexec/mysqld: Shutdown complete

vermouth

先 killall -9 mysqld，再启动试试.检查端口是否开启，ps aux|grep mysql 能否看见。

hjq20

我输入提示没有进程被关闭，那可能是本来就没有把mysqld进程启动起来。。[root@test2 log]# killall -9 mysqld
mysqld: no process killed
[root@test2 log]# ps aux|grep mysql
root     27364  0.0  0.0  4196  664 pts/1    R+   14:52   0:00 grep mysql
[root@test2 log]#

该怎么解决了。。。请楼上的帮下忙。。。

[ 本帖最后由 hjq20 于 2008-12-10 15:00 编辑 ]