浏览 4119 次
|
锁定老帖子 主题：linux下 mysql服务无法重启
精华帖 (0) :: 良好帖 (0) :: 新手帖 (0) :: 隐藏帖 (0)
|
|
|---|---|
| 作者 | 正文 |
|
发表时间：2016-09-21
160921 07:44:19 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
160921 7:44:19 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead. 160921 7:44:19 [Warning] '--default-character-set' is deprecated and will be removed in a future release. Please use '--character-set-server' instead. 160921 7:44:19 InnoDB: Initializing buffer pool, size = 8.0M 160921 7:44:19 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 21 225158025 160921 7:44:19 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... InnoDB: Doing recovery: scanned up to log sequence number 21 225225930 InnoDB: 1 transaction(s) which must be rolled back or cleaned up InnoDB: in total 75792 row operations to undo InnoDB: Trx id counter is 0 1072467712 160921 7:44:21 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 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 85298523, file name ./mysql-bin.000746 InnoDB: Starting in background the rollback of uncommitted transactions 160921 7:44:23 InnoDB: Rolling back trx with id 0 1072373890, 75792 rows to undo InnoDB: Progress in percents: 1160921 7:44:23 InnoDB: Started; log sequence number 21 225225930 160921 7:44:23 [Note] Recovering after a crash using mysql-bin 160921 7:44:25 [Note] Starting crash recovery... 160921 7:44:25 [Note] Crash recovery finished. 160921 7:44:26 [Warning] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--relay-log=mysqld-relay-bin' to avoid this problem. 160921 7:44:26 [Note] Slave SQL thread initialized, starting replication in log 'mysql-bin.000010' at position 16860, relay log './mysqld-relay-bin.000020' position: 4 160921 7:44:26 [Note] Event Scheduler: Loaded 0 events 160921 7:44:26 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.73-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 160921 7:44:26 [ERROR] Slave I/O: error connecting to master 'mengcheng@192.168.1.187:3306' - 下面是error日志，请大家分析下 retry-time: 60 retries: 86400, Error_code: 1045 2 3 4 5 6 7 8 9 10 11160921 7:45:47 [Note] /usr/libexec/mysqld: Normal shutdown 160921 7:45:47 [Note] Event Scheduler: Purging the queue. 0 events 160921 7:45:47 [Note] Slave I/O thread killed while connecting to master 160921 7:45:47 [Note] Slave I/O thread exiting, read up to log 'mysql-bin.000010', position 16860 160921 7:45:47 [Note] Error reading relay log event: slave SQL thread was killed 160921 7:45:48 InnoDB: Starting shutdown... 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35160921 07:50:48 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 160921 7:50:48 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead. 160921 7:50:48 [Warning] '--default-character-set' is deprecated and will be removed in a future release. Please use '--character-set-server' instead. 160921 7:50:48 InnoDB: Initializing buffer pool, size = 8.0M 160921 7:50:48 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 21 226798723 160921 7:50:48 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... 160921 7:50:49 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 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 160921 7:51:00 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 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 160921 7:51:11 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 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 160921 7:51:21 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 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 160921 7:51:31 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 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: Doing recovery: scanned up to log sequence number 21 231748685 InnoDB: 1 transaction(s) which must be rolled back or cleaned up InnoDB: in total 49814 row operations to undo InnoDB: Trx id counter is 0 1072467712 160921 7:51:42 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 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 85298523, file name ./mysql-bin.000746 InnoDB: Starting in background the rollback of uncommitted transactions 160921 7:51:43 InnoDB: Rolling back trx with id 0 1072373890, 49814 rows to undo InnoDB: Progress in percents: 1160921 7:51:43 InnoDB: Started; log sequence number 21 231748685 160921 7:51:44 [Warning] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--relay-log=mysqld-relay-bin' to avoid this problem. 160921 7:51:45 [Note] Slave SQL thread initialized, starting replication in log 'mysql-bin.000010' at position 16860, relay log './mysqld-relay-bin.000020' position: 4 160921 7:51:45 [Note] Event Scheduler: Loaded 0 events 160921 7:51:45 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.73-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 160921 7:51:45 [ERROR] Slave I/O: error connecting to master 'mengcheng@192.168.1.187:3306' - retry-time: 60 retries: 86400, Error_code: 1045 2 3 4 5 6 7 8 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 100 InnoDB: Rolling back of trx id 0 1072373890 completed 160921 7:57:03 InnoDB: Rollback of non-prepared transactions completed 声明：ITeye文章版权属于作者，受法律保护。没有作者书面许可不得转载。
推荐链接
|
| 返回顶楼 | |
