免费注册 查看新帖 |

Chinaunix

  平台 论坛 博客 文库
最近访问板块 发新帖
查看: 2366 | 回复: 1
打印 上一主题 下一主题

请问,mysql错误日志中这样的信息是什么含义? [复制链接]

论坛徽章:
0
跳转到指定楼层
1 [收藏(0)] [报告]
发表于 2005-10-07 14:47 |只看该作者 |倒序浏览
mysql会自己停掉~
检查日志发现以下信息,请大家给些处理建议~

InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
051006 21:17:33  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 2 158401524.
InnoDB: Doing recovery: scanned up to log sequence number 2 163643904
InnoDB: Doing recovery: scanned up to log sequence number 2 168886784
InnoDB: Doing recovery: scanned up to log sequence number 2 174129664
InnoDB: Doing recovery: scanned up to log sequence number 2 176833506
InnoDB: 3 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 3 row operations to undo
InnoDB: Trx id counter is 0 127720192
051006 21:17:34  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: Starting rollback of uncommitted transactions
InnoDB: Rolling back trx with id 0 127719625, 1 rows to undo
InnoDB: Rolling back of trx id 0 127719625 completed
InnoDB: Rolling back trx with id 0 127719619, 1 rows to undo
InnoDB: Rolling back of trx id 0 127719619 completed
InnoDB: Rolling back trx with id 0 127719618, 1 rows to undo
InnoDB: Rolling back of trx id 0 127719618 completed
InnoDB: Rollback of uncommitted transactions completed
051006 21:18:07  InnoDB: Flushing modified pages from the buffer pool...
051006 21:18:16  InnoDB: Started; log sequence number 2 176833506
/usr/local/mysql/bin/mysqld: ready for connections.
Version: '4.1.13-max-log'  socket: '/tmp/mysql.sock'  port: 3306  MySQL Community Edition - Experimental (GPL)
051006 21:18:28 [ERROR] /usr/local/mysql/bin/mysqld: Sort aborted
051006 21:18:32 [ERROR] /usr/local/mysql/bin/mysqld: Sort aborted
InnoDB: Error: tried to read 557056 bytes at offset 0 212992.
InnoDB: Was only able to read 434176.
051006 21:22:10  InnoDB: Operating system error number 4 in a file operation.
InnoDB: Error number 4 means 'Interrupted system call'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/mysql/en/Operating_System_error_codes.html
InnoDB: File operation call: 'read'.
InnoDB: Cannot continue operation.

Number of processes running now: 0
051006 21:22:11  mysqld restarted
051006 21:22:11  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...
051006 21:22:11  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 2 176836510.
InnoDB: Doing recovery: scanned up to log sequence number 2 179060785
051006 21:22:12  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
051006 21:22:25  InnoDB: Flushing modified pages from the buffer pool...
051006 21:22:31  InnoDB: Started; log sequence number 2 179060785
/usr/local/mysql/bin/mysqld: ready for connections.
Version: '4.1.13-max-log'  socket: '/tmp/mysql.sock'  port: 3306  MySQL Community Edition - Experimental (GPL)
051006 21:22:42 [ERROR] /usr/local/mysql/bin/mysqld: Sort aborted
051006 21:22:43 [ERROR] /usr/local/mysql/bin/mysqld: Sort aborted
InnoDB: Error: tried to read 524288 bytes at offset 0 212992.
InnoDB: Was only able to read 434176.
051006 21:28:30  InnoDB: Operating system error number 4 in a file operation.
InnoDB: Error number 4 means 'Interrupted system call'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/mysql/en/Operating_System_error_codes.html
InnoDB: File operation call: 'read'.
InnoDB: Cannot continue operation.

Number of processes running now: 0
051006 21:28:30  mysqld restarted
051006 21:28:30 [ERROR] Can't start server: Bind on TCP/IP port: Address already in use
051006 21:28:30 [ERROR] Do you already have another mysqld server running on port: 3306 ?
051006 21:28:30 [ERROR] Aborting

051006 21:28:30 [Note] /usr/local/mysql/bin/mysqld: Shutdown complete
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
051006 21:17:33  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 2 158401524.
InnoDB: Doing recovery: scanned up to log sequence number 2 163643904
InnoDB: Doing recovery: scanned up to log sequence number 2 168886784
InnoDB: Doing recovery: scanned up to log sequence number 2 174129664
InnoDB: Doing recovery: scanned up to log sequence number 2 176833506
InnoDB: 3 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 3 row operations to undo
InnoDB: Trx id counter is 0 127720192
051006 21:17:34  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: Starting rollback of uncommitted transactions
InnoDB: Rolling back trx with id 0 127719625, 1 rows to undo
InnoDB: Rolling back of trx id 0 127719625 completed
InnoDB: Rolling back trx with id 0 127719619, 1 rows to undo
InnoDB: Rolling back of trx id 0 127719619 completed
InnoDB: Rolling back trx with id 0 127719618, 1 rows to undo
InnoDB: Rolling back of trx id 0 127719618 completed
InnoDB: Rollback of uncommitted transactions completed
051006 21:18:07  InnoDB: Flushing modified pages from the buffer pool...
051006 21:18:16  InnoDB: Started; log sequence number 2 176833506
/usr/local/mysql/bin/mysqld: ready for connections.
Version: '4.1.13-max-log'  socket: '/tmp/mysql.sock'  port: 3306  MySQL Community Edition - Experimental (GPL)
051006 21:18:28 [ERROR] /usr/local/mysql/bin/mysqld: Sort aborted
051006 21:18:32 [ERROR] /usr/local/mysql/bin/mysqld: Sort aborted
InnoDB: Error: tried to read 557056 bytes at offset 0 212992.
InnoDB: Was only able to read 434176.
051006 21:22:10  InnoDB: Operating system error number 4 in a file operation.
InnoDB: Error number 4 means 'Interrupted system call'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/mysql/en/Operating_System_error_codes.html
InnoDB: File operation call: 'read'.
InnoDB: Cannot continue operation.

Number of processes running now: 0
051006 21:22:11  mysqld restarted
051006 21:22:11  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...
051006 21:22:11  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 2 176836510.
InnoDB: Doing recovery: scanned up to log sequence number 2 179060785
051006 21:22:12  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
051006 21:22:25  InnoDB: Flushing modified pages from the buffer pool...
051006 21:22:31  InnoDB: Started; log sequence number 2 179060785
/usr/local/mysql/bin/mysqld: ready for connections.
Version: '4.1.13-max-log'  socket: '/tmp/mysql.sock'  port: 3306  MySQL Community Edition - Experimental (GPL)
051006 21:22:42 [ERROR] /usr/local/mysql/bin/mysqld: Sort aborted
051006 21:22:43 [ERROR] /usr/local/mysql/bin/mysqld: Sort aborted
InnoDB: Error: tried to read 524288 bytes at offset 0 212992.
InnoDB: Was only able to read 434176.
051006 21:28:30  InnoDB: Operating system error number 4 in a file operation.
InnoDB: Error number 4 means 'Interrupted system call'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/mysql/en/Operating_System_error_codes.html
InnoDB: File operation call: 'read'.
InnoDB: Cannot continue operation.

Number of processes running now: 0
051006 21:28:30  mysqld restarted
051006 21:28:30 [ERROR] Can't start server: Bind on TCP/IP port: Address already in use
051006 21:28:30 [ERROR] Do you already have another mysqld server running on port: 3306 ?
051006 21:28:30 [ERROR] Aborting

051006 21:28:30 [Note] /usr/local/mysql/bin/mysqld: Shutdown complete
051006 21:28:30  mysqld ended

论坛徽章:
0
2 [报告]
发表于 2005-10-07 14:49 |只看该作者

请问,mysql错误日志中这样的信息是什么含义?

可能是这个版本的有问题,换一个别的看看?
您需要登录后才可以回帖 登录 | 注册

本版积分规则 发表回复

  

北京盛拓优讯信息技术有限公司. 版权所有 京ICP备16024965号-6 北京市公安局海淀分局网监中心备案编号:11010802020122 niuxiaotong@pcpop.com 17352615567
未成年举报专区
中国互联网协会会员  联系我们:huangweiwei@itpub.net
感谢所有关心和支持过ChinaUnix的朋友们 转载本站内容请注明原作者名及出处

清除 Cookies - ChinaUnix - Archiver - WAP - TOP