设为首页收藏本站
切换到宽版

全球主机交流论坛

 找回密码
 注册

QQ登录

只需一步，快速开始

全球主机交流论坛»论坛 › 主机综合交流 › 美国VPS综合讨论 › 求大佬帮我看看为啥mysql老是停止运行
CeraNetworks网络延迟测速工具IP归属甄别会员请立即修改密码
返回列表 发新帖
查看: 678|回复: 5
打印 上一主题 下一主题

求大佬帮我看看为啥mysql老是停止运行

[复制链接]
之南
跳转到指定楼层
1#
发表于 2023-7-15 23:29:43 | 只看该作者 回帖奖励 |倒序浏览 |阅读模式
  1. 2023-07-15 20:20:40 24448 [Note] Plugin 'FEDERATED' is disabled.
  2. 2023-07-15 20:20:40 24448 [Note] InnoDB: Using atomics to ref count buffer pool pages
  3. 2023-07-15 20:20:40 24448 [Note] InnoDB: The InnoDB memory heap is disabled
  4. 2023-07-15 20:20:40 24448 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
  5. 2023-07-15 20:20:40 24448 [Note] InnoDB: Memory barrier is not used
  6. 2023-07-15 20:20:40 24448 [Note] InnoDB: Compressed tables use zlib 1.2.11
  7. 2023-07-15 20:20:40 24448 [Note] InnoDB: Using Linux native AIO
  8. 2023-07-15 20:20:40 24448 [Note] InnoDB: Using CPU crc32 instructions
  9. 2023-07-15 20:20:40 24448 [Note] InnoDB: Initializing buffer pool, size = 16.0M
  10. 2023-07-15 20:20:40 24448 [Note] InnoDB: Completed initialization of buffer pool
  11. 2023-07-15 20:20:40 24448 [Note] InnoDB: Highest supported file format is Barracuda.
  12. 2023-07-15 20:20:40 24448 [Note] InnoDB: The log sequence numbers 1626004 and 1626004 in ibdata files do not match the log sequence number 788234804 in the ib_logfiles!
  13. 2023-07-15 20:20:40 24448 [Note] InnoDB: Database was not shutdown normally!
  14. 2023-07-15 20:20:40 24448 [Note] InnoDB: Starting crash recovery.
  15. 2023-07-15 20:20:40 24448 [Note] InnoDB: Reading tablespace information from the .ibd files...
  16. 2023-07-15 20:20:42 24448 [Note] InnoDB: Restoring possible half-written data pages
  17. 2023-07-15 20:20:42 24448 [Note] InnoDB: from the doublewrite buffer...
  18. InnoDB: Last MySQL binlog file position 0 36093755, file name mysql-bin.000012
  19. 2023-07-15 20:20:44 24448 [Note] InnoDB: 128 rollback segment(s) are active.
  20. 2023-07-15 20:20:44 24448 [Note] InnoDB: Waiting for purge to start
  21. 2023-07-15 20:20:44 24448 [Note] InnoDB: 5.6.50 started; log sequence number 788234804
  22. 2023-07-15 20:20:44 24448 [Note] Recovering after a crash using mysql-bin
  23. 2023-07-15 20:20:45 24448 [Note] Starting crash recovery...
  24. 2023-07-15 20:20:45 24448 [Note] Crash recovery finished.
  25. 2023-07-15 20:20:45 24448 [Note] RSA private key file not found: /www/server/data//private_key.pem. Some authentication plugins will not work.
  26. 2023-07-15 20:20:45 24448 [Note] RSA public key file not found: /www/server/data//public_key.pem. Some authentication plugins will not work.
  27. 2023-07-15 20:20:45 24448 [Note] Server hostname (bind-address): '*'; port: 3306
  28. 2023-07-15 20:20:45 24448 [Note] IPv6 is available.
  29. 2023-07-15 20:20:45 24448 [Note]   - '::' resolves to '::';
  30. 2023-07-15 20:20:45 24448 [Note] Server socket created on IP: '::'.
  31. 2023-07-15 20:20:45 24448 [Note] Event Scheduler: Loaded 0 events
  32. 2023-07-15 20:20:45 24448 [Note] /www/server/mysql/bin/mysqld: ready for connections.
  33. Version: '5.6.50-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
  34. 2023-07-15 20:33:20 24560 [Note] Plugin 'FEDERATED' is disabled.
  35. 2023-07-15 20:33:21 24560 [Note] InnoDB: Using atomics to ref count buffer pool pages
  36. 2023-07-15 20:33:21 24560 [Note] InnoDB: The InnoDB memory heap is disabled
  37. 2023-07-15 20:33:21 24560 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
  38. 2023-07-15 20:33:21 24560 [Note] InnoDB: Memory barrier is not used
  39. 2023-07-15 20:33:21 24560 [Note] InnoDB: Compressed tables use zlib 1.2.11
  40. 2023-07-15 20:33:21 24560 [Note] InnoDB: Using Linux native AIO
  41. 2023-07-15 20:33:21 24560 [Note] InnoDB: Using CPU crc32 instructions
  42. 2023-07-15 21:29:48 26376 [Note] Plugin 'FEDERATED' is disabled.
  43. 2023-07-15 21:29:48 26376 [Note] InnoDB: Using atomics to ref count buffer pool pages
  44. 2023-07-15 21:29:48 26376 [Note] InnoDB: The InnoDB memory heap is disabled
  45. 2023-07-15 21:29:48 26376 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
  46. 2023-07-15 21:29:48 26376 [Note] InnoDB: Memory barrier is not used
  47. 2023-07-15 21:29:48 26376 [Note] InnoDB: Compressed tables use zlib 1.2.11
  48. 2023-07-15 21:29:48 26376 [Note] InnoDB: Using Linux native AIO
  49. 2023-07-15 21:29:48 26376 [Note] InnoDB: Using CPU crc32 instructions
  50. 2023-07-15 21:29:48 26376 [Note] InnoDB: Initializing buffer pool, size = 16.0M
  51. 2023-07-15 21:29:48 26376 [Note] InnoDB: Completed initialization of buffer pool
  52. 2023-07-15 21:29:48 26376 [Note] InnoDB: Highest supported file format is Barracuda.
  53. 2023-07-15 21:29:48 26376 [Note] InnoDB: The log sequence numbers 1626004 and 1626004 in ibdata files do not match the log sequence number 788247601 in the ib_logfiles!
  54. 2023-07-15 21:29:48 26376 [Note] InnoDB: Database was not shutdown normally!
  55. 2023-07-15 21:29:48 26376 [Note] InnoDB: Starting crash recovery.
  56. 2023-07-15 21:29:48 26376 [Note] InnoDB: Reading tablespace information from the .ibd files...
  57. 2023-07-15 21:29:49 26376 [Note] InnoDB: Restoring possible half-written data pages
  58. 2023-07-15 21:29:49 26376 [Note] InnoDB: from the doublewrite buffer...
  59. InnoDB: Last MySQL binlog file position 0 6864, file name mysql-bin.000013
  60. 2023-07-15 21:29:49 26376 [Note] InnoDB: 128 rollback segment(s) are active.
  61. 2023-07-15 21:29:49 26376 [Note] InnoDB: Waiting for purge to start
  62. 2023-07-15 21:29:49 26376 [Note] InnoDB: 5.6.50 started; log sequence number 788247601
  63. 2023-07-15 21:29:49 26376 [Note] Recovering after a crash using mysql-bin
  64. 2023-07-15 21:29:49 26376 [Note] Starting crash recovery...
  65. 2023-07-15 21:29:49 26376 [Note] Crash recovery finished.
  66. 2023-07-15 21:29:49 26376 [Note] RSA private key file not found: /www/server/data//private_key.pem. Some authentication plugins will not work.
  67. 2023-07-15 21:29:49 26376 [Note] RSA public key file not found: /www/server/data//public_key.pem. Some authentication plugins will not work.
  68. 2023-07-15 21:29:49 26376 [Note] Server hostname (bind-address): '*'; port: 3306
  69. 2023-07-15 21:29:49 26376 [Note] IPv6 is available.
  70. 2023-07-15 21:29:49 26376 [Note]   - '::' resolves to '::';
  71. 2023-07-15 21:29:49 26376 [Note] Server socket created on IP: '::'.
  72. 2023-07-15 21:29:49 26376 [Note] Event Scheduler: Loaded 0 events
  73. 2023-07-15 21:29:49 26376 [Note] /www/server/mysql/bin/mysqld: ready for connections.
  74. Version: '5.6.50-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
复制代码



宝塔面板里的mysql老是停止运行
回复

举报

BackDoor
2#
发表于 2023-7-15 23:41:02 | 只看该作者
提示: 作者被禁止或删除 内容自动屏蔽
回复 支持 反对

举报

虎谷
3#
发表于 2023-7-16 12:59:17 | 只看该作者
日志全是 Note ，看个屁啊
回复 支持 反对

举报

yanzhiling2002
5#
发表于 2023-7-16 13:25:05 来自手机 | 只看该作者
我问了一下chatgpt
回复 支持 反对

举报

yanzhiling2002
6#
发表于 2023-7-16 13:26:11 来自手机 | 只看该作者
我问了一下chatgpt 他说日志中没有提供具体的错误消息，因此很难确定错误的确切原因。但是，日志中有一些注释可能指示潜在的问题：  InnoDB 内存堆被禁用。 ibdata 文件中的日志序列号与 ib_logfiles 中的日志序列号不匹配。 数据库没有正常关闭。 这些注释表明可能出现了 MySQL 服务器的崩溃或异常关闭，这可能导致数据损坏或其他问题。InnoDB 内存堆被禁用也可能影响性能。  要确定错误的确切原因，需要检查日志中提供的错误消息。
回复 支持 反对

举报

返回列表 发新帖
高级模式
B Color Image Link Quote Code Smilies
您需要登录后才可以回帖 登录 | 注册

本版积分规则

Archiver|手机版|小黑屋|全球主机交流论坛

GMT+8, 2024-6-25 08:38 , Processed in 0.059825 second(s), 10 queries , Gzip On, MemCache On.

Powered by Discuz! X3.4

© 2001-2023 Discuz! Team.

快速回复 返回顶部 返回列表