MySQL

wfshjkg 2017-07-12 09:50:40
170711 18:08:30 [Warning] IP address '123.249.24.218' could not be resolved: 这是在主机名解析时通常出现的暂时错误,它意味着本地服务器没有从权威服务器上收到响应。
170711 18:22:57 [Warning] IP address '47.90.92.26' could not be resolved: 不知道这样的主机。
170711 18:57:43 [Warning] IP address '123.160.230.50' could not be resolved: 不知道这样的主机。
170711 19:17:19 [Warning] IP address '180.97.215.60' could not be resolved: 不知道这样的主机。
170711 19:17:20 [Warning] IP address '180.97.215.60' could not be resolved: 不知道这样的主机。
170711 21:51:48 [Note] Plugin 'FEDERATED' is disabled.
170711 21:51:48 InnoDB: The InnoDB memory heap is disabled
170711 21:51:48 InnoDB: Mutexes and rw_locks use Windows interlocked functions
170711 21:51:48 InnoDB: Compressed tables use zlib 1.2.3
170711 21:51:48 InnoDB: Initializing buffer pool, size = 18.0M
170711 21:51:48 InnoDB: Completed initialization of buffer pool
170711 21:51:48 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 12345876
170711 21:51: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...
InnoDB: Doing recovery: scanned up to log sequence number 12494170
170711 21:51:48 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 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
170711 21:51:49 InnoDB: Waiting for the background threads to start
170711 21:51:50 InnoDB: 5.5.37 started; log sequence number 12494170
170711 21:51:50 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
170711 21:51:50 [Note] - '0.0.0.0' resolves to '0.0.0.0';
170711 21:51:50 [Note] Server socket created on IP: '0.0.0.0'.
170711 21:51:50 [Note] Event Scheduler: Loaded 0 events
...全文
244 2 打赏 收藏 转发到动态 举报
写回复
用AI写文章
2 条回复
切换为时间正序
请发表友善的回复…
发表回复
LongRui888 2017-07-13
  • 打赏
  • 举报
回复
你贴的日志好像不全,里面并没有记录你的mysql关闭了,同时也没有任何的错误信息,只是记录了mysql启动后,innodb在应用批量的log,进行恢复。。。
wfshjkg 2017-07-12
  • 打赏
  • 举报
回复
我标题还没写完呢,MYSQL最近经常重启,看不懂错误日志是为什么,有看的懂的同学帮帮忙么?可以

56,685

社区成员

发帖
与我相关
我的任务
社区描述
MySQL相关内容讨论专区
社区管理员
  • MySQL
加入社区
  • 近7日
  • 近30日
  • 至今
社区公告
暂无公告

试试用AI创作助手写篇文章吧