服务器停电mysql无法启动_服务器停电mysql无法启动

最新推荐文章于 2023-04-19 17:24:53 发布
最新推荐文章于 2023-04-19 17:24:53 发布
阅读量83 收藏
点赞数
文章标签： 服务器停电mysql无法启动
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/weixin_33708562/article/details/113293855
版权

130904 14:54:58 MySql: Got signal 11. Aborting!

130904 14:54:58 Aborting

130904 14:54:58  InnoDB: Warning: shutting down a not properly started

InnoDB: or created database!

130904 14:54:58 MySql: Shutdown Complete

InnoDB: Warning: an inconsistent page in the doublewrite buffer

InnoDB: space id 0 page number 38951, 8'th page in dblwr buf.

InnoDB: Warning: an inconsistent page in the doublewrite buffer

InnoDB: space id 0 page number 38956, 9'th page in dblwr buf.

InnoDB: Warning: an inconsistent page in the doublewrite buffer

InnoDB: space id 0 page number 39005, 10'th page in dblwr buf.

InnoDB: Warning: an inconsistent page in the doublewrite buffer

InnoDB: space id 0 page number 32769, 11'th page in dblwr buf.

InnoDB: Warning: an inconsistent page in the doublewrite buffer

InnoDB: space id 0 page number 40305, 12'th page in dblwr buf.

InnoDB: Warning: an inconsistent page in the doublewrite buffer

InnoDB: space id 0 page number 40301, 17'th page in dblwr buf.

InnoDB: Warning: an inconsistent page in the doublewrite buffer

InnoDB: space id 0 page number 40298, 26'th page in dblwr buf.

InnoDB: Warning: an inconsistent page in the doublewrite buffer

InnoDB: space id 0 page number 40294, 32'th page in dblwr buf.

InnoDB: Warning: an inconsistent page in the doublewrite buffer

InnoDB: space id 0 page number 40288, 34'th page in dblwr buf.

InnoDB: Warning: an inconsistent page in the doublewrite buffer

InnoDB: space id 0 page number 33111, 36'th page in dblwr buf.

InnoDB: Warning: an inconsistent page in the doublewrite buffer

InnoDB: space id 0 page number 33112, 37'th page in dblwr buf.

InnoDB: Warning: an inconsistent page in the doublewrite buffer

InnoDB: space id 0 page number 33113, 38'th page in dblwr buf.

InnoDB: Warning: an inconsistent page in the doublewrite buffer

InnoDB: space id 0 page number 33114, 39'th page in dblwr buf.

InnoDB: Warning: an inconsistent page in the doublewrite buffer

InnoDB: space id 0 page number 33115, 40'th page in dblwr buf.

InnoDB: Warning: an inconsistent page in the doublewrite buffer

InnoDB: space id 0 page number 33116, 41'th page in dblwr buf.

InnoDB: Warning: an inconsistent page in the doublewrite buffer

InnoDB: space id 0 page number 33117, 42'th page in dblwr buf.

InnoDB: Warning: an inconsistent page in the doublewrite buffer

InnoDB: space id 0 page number 40448, 44'th page in dblwr buf.

InnoDB: Warning: an inconsistent page in the doublewrite buffer

InnoDB: space id 0 page number 40736, 46'th page in dblwr buf.

InnoDB: Warning: an inconsistent page in the doublewrite buffer

InnoDB: space id 0 page number 40737, 47'th page in dblwr buf.

InnoDB: Warning: an inconsistent page in the doublewrite buffer

InnoDB: space id 0 page number 40738, 48'th page in dblwr buf.

InnoDB: Warning: an inconsistent page in the doublewrite buffer

InnoDB: space id 0 page number 40739, 49'th page in dblwr buf.

InnoDB: Warning: an inconsistent page in the doublewrite buffer

InnoDB: space id 0 page number 40740, 50'th page in dblwr buf.

InnoDB: Warning: an inconsistent page in the doublewrite buffer

InnoDB: space id 0 page number 40741, 51'th page in dblwr buf.

InnoDB: Warning: an inconsistent page in the doublewrite buffer

InnoDB: space id 0 page number 40742, 52'th page in dblwr buf.

InnoDB: Warning: an inconsistent page in the doublewrite buffer

InnoDB: space id 0 page number 40743, 53'th page in dblwr buf.

InnoDB: Warning: an inconsistent page in the doublewrite buffer

InnoDB: space id 0 page number 40744, 54'th page in dblwr buf.

InnoDB: Warning: an inconsistent page in the doublewrite buffer

InnoDB: space id 0 page number 40745, 55'th page in dblwr buf.

InnoDB: Warning: an inconsistent page in the doublewrite buffer

InnoDB: space id 0 page number 40746, 56'th page in dblwr buf.

InnoDB: Warning: an inconsistent page in the doublewrite buffer

InnoDB: space id 0 page number 40747, 57'th page in dblwr buf.

InnoDB: Warning: an inconsistent page in the doublewrite buffer

InnoDB: space id 0 page number 40748, 58'th page in dblwr buf.

InnoDB: Warning: an inconsistent page in the doublewrite buffer

InnoDB: space id 0 page number 40749, 59'th page in dblwr buf.

InnoDB: Warning: an inconsistent page in the doublewrite buffer

InnoDB: space id 0 page number 40750, 60'th page in dblwr buf.

InnoDB: Warning: an inconsistent page in the doublewrite buffer

InnoDB: space id 0 page number 40751, 61'th page in dblwr buf.

InnoDB: Warning: an inconsistent page in the doublewrite buffer

InnoDB: space id 0 page number 40752, 62'th page in dblwr buf.

InnoDB: Warning: an inconsistent page in the doublewrite buffer

InnoDB: space id 0 page number 40753, 63'th page in dblwr buf.

InnoDB: Warning: an inconsistent page in the doublewrite buffer

InnoDB: space id 0 page number 40754, 64'th page in dblwr buf.

InnoDB: Warning: an inconsistent page in the doublewrite buffer

InnoDB: space id 0 page number 40755, 65'th page in dblwr buf.

InnoDB: Warning: an inconsistent page in the doublewrite buffer

InnoDB: space id 0 page number 40756, 66'th page in dblwr buf.

InnoDB: Warning: an inconsistent page in the doublewrite buffer

InnoDB: space id 0 page number 40757, 67'th page in dblwr buf.

InnoDB: Warning: an inconsistent page in the doublewrite buffer

InnoDB: space id 0 page number 40279, 68'th page in dblwr buf.

InnoDB: Warning: an inconsistent page in the doublewrite buffer

InnoDB: space id 0 page number 38892, 93'th page in dblwr buf.

InnoDB: Warning: an inconsistent page in the doublewrite buffer

InnoDB: space id 0 page number 38874, 97'th page in dblwr buf.

InnoDB: Warning: an inconsistent page in the doublewrite buffer

InnoDB: space id 0 page number 38878, 99'th page in dblwr buf.

InnoDB: Warning: an inconsistent page in the doublewrite buffer

InnoDB: space id 0 page number 38960, 100'th page in dblwr buf.

InnoDB: Warning: an inconsistent page in the doublewrite buffer

InnoDB: space id 0 page number 38927, 107'th page in dblwr buf.

InnoDB: Warning: an inconsistent page in the doublewrite buffer

InnoDB: space id 0 page number 38935, 108'th page in dblwr buf.

InnoDB: Warning: an inconsistent page in the doublewrite buffer

InnoDB: space id 0 page number 38936, 109'th page in dblwr buf.

InnoDB: Warning: an inconsistent page in the doublewrite buffer

InnoDB: space id 0 page number 33873, 121'th page in dblwr buf.

InnoDB: Warning: an inconsistent page in the doublewrite buffer

InnoDB: space id 0 page number 34525, 124'th page in dblwr buf.

InnoDB: Warning: an inconsistent page in the doublewrite buffer

InnoDB: space id 0 page number 34526, 125'th page in dblwr buf.

InnoDB: Warning: an inconsistent page in the doublewrite buffer

InnoDB: space id 0 page number 34527, 126'th page in dblwr buf.

InnoDB: Warning: an inconsistent page in the doublewrite buffer

InnoDB: space id 0 page number 34177, 127'th page in dblwr buf.

InnoDB: Error: trying to access page number 6183 in space 0

InnoDB: which is outside the tablespace bounds.

InnoDB: Byte offset 0, len 16384, i/o type 10

130904 15:06:04InnoDB: Assertion failure in thread 1460 in file e:\mysqldev\build\mysql-4.0.26-build\mysql-4.0.26\innobase\fil\fil0fil.c line 1207

InnoDB: We intentionally generate a memory trap.

InnoDB: Submit a detailed bug report to http://bugs.mysql.com.

InnoDB: If you get repeated assertion failures or crashes, even

InnoDB: immediately after the mysqld startup, there may be

InnoDB: corruption in the InnoDB tablespace. Please refer to

InnoDB: http://dev.mysql.com/doc/mysql/en/Forcing_recovery.html

InnoDB: about forcing recovery.

130904 15:06:04 MySql: Got signal 11. Aborting!

130904 15:06:04 Aborting

130904 15:06:04  InnoDB: Warning: shutting down a not properly started

InnoDB: or created database!

130904 15:06:04 MySql: Shutdown Complete

2013年9月04日 15:33

孙靓
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
mysql got signal 11_求助 mysqld got signal 11 解决办法
weixin_29958123的博客
01-27 763
今天下午 mysql服务 非正常关闭，错误日志如下：不知道，那位大侠有遇到，我在网上查看了一下，有人重装mysql 貌似解决了这个问题，请高手指点啊。080325 15:46:14 [ERROR] /usr/local/mysql/libexec/mysqld: Sort abortedmysqld got signal 11;This could be because you hit a bug...
mysql 断电不能启动
11-15
### MySQL 断电后无法正常启动的问题分析与解决 #### 问题背景 ...通过以上步骤，可以逐步排查并解决因断电导致的MySQL无法启动的问题。需要注意的是，在处理这类问题时要格外小心，避免造成不可逆的数据丢失。
电脑断电导致的mysql启动失败解决方式
最新发布
sinat_36758246的博客
04-19 3321
1，修改my.ini文件，在mysqld下添加innodb_force_recovery = 2，其中数字2可以是1-6，可以挨个尝试。3, 使用navicat重连数据库，恢复了所有库和表数据。mysql版本：mysql-5.7.30-winx64。完整的my.ini文件如下。2，重新启动mysql。
断电MySQL起不来_急求mysql 断电后无法启动解决方法！！！！
weixin_39603908的博客
01-20 84
该楼层疑似违规已被系统折叠隐藏此楼查看此楼RT，平台是windows+xampp，断电后开机无法启动mysql。errorlog如下2014-08-14 08:01:35 2032 [Note] Plugin *FEDERATED* is disabled.2014-08-14 08:01:35 130 InnoDB: Warning: Using innodb_additional_mem_p...
mysql无法正常启动的原因之一
weixin_39037925的博客
07-16 2589
因为要在mysql中存储大文件，所以更改了my.ini中的max_allow_packet,改完以后发现mysql启动不起来，一直是start pending，也停不了。最后发现是不小心改了my.ini的编码，它的默认编码为ANSI，不小心被我弄成了utf8,只要改下编码问题就解决了。 ...
服务器断电后，mysql不能启动的解决方案
热门推荐
zhoulu001的专栏
04-12 1万+
公司的数据中心由于断电，服务器（服务器是ubuntu系统）重启后，mysql却无法启动，折腾了好久，现将解决方案记录如下：     1.mysql的日志位于ubuntu的/var/lib/mysql下面，我们可以看到ib_logfile0和ib_logfile1两个文件     2.将ib_logfile0和ib_logfile1两个文件删除 rm ib_logfile*   3.使
linux mysql 报错：MYSQL:The server quit without updating PID file
12-15
- 当MySQL无法写入PID文件时，可能是由于文件权限不足。检查 `/usr/local/mysql/data/rekfan.pid` 文件（或根据实际路径调整），确保MySQL用户（通常是`mysql`）对其有读写权限。可以使用以下命令修改权限： ``` ...
基于web的停电分析系统.rar
04-01
1. **数据收集与存储**：系统需要从电力设备、传感器或其他数据源实时收集停电信息，并将这些数据存储在数据库中，如MySQL或Oracle，以便后续分析。 2. **数据处理**：通过Java后端服务对收集到的数据进行清洗、...
MySQL高级（六）：事务的四大特性和使用
12-14
在日常生活中，有时我们需要进行银行转账，这个银行转账操作背后就是需要执行多个SQL语句，假如这些SQL执行到一半突然停电了，那么就会导致这个功能只完成了一半，这种情况是不允许出现，要想解决这个问题就需要通过...
物流配货网（javaweb+mysql）
04-02
物流配货网站具有以下功能。全面展示企业的形象。通过系统流程图，全面介绍企业的服务项目。实现对车辆来源的管理。...当受到外界环境（停电、网络病毒）干扰时，系统可以自动保护原始数据的安全。系统退出。
mysql5.7.21启动异常的修复方法
01-19
一同事反馈有一MySQL实例因为断电之后，启动不了。用了innodb_force_recovery=6也无效，于是前往查看。 排查过程： 最早的启动信息里面，没有任何报错，只有一行[ERROR] Aborting提示，如下： 接着同事用了innodb_force_recovery＝6的方式，才多出现了如下的错误提示，但仍无法启动成功，这个时候，我才决定去看个究竟。 过滤启动日志，grep ERROR /data/mysql/3306/mysql_run.err 可以看到，全部报错主要如下： MySQL大多数不能启动的原因，都是系统数据库的原因，看来这个也不例外。 尝试使用带–skip-g
linux重启后mysql始终无法启动
骑猪也能看夕阳
02-19 4141
网上看了一堆解决方案对我来说都没啥用，知道看到一篇博客上写着 wget -O sql-repair.sh http://download.bt.cn/install/sql-repair.sh && sh sql-repair.sh 具体什么意思不太清楚，但是结果ok了 ...
mysql的innodb中事务日志ib_logfile
congluoyang1647的博客
11-07 380
mysql的innodb中事务日志ib_logfile 事务日志或称redo日志，在mysql中默认以ib_logfile0,ib_logfile1名称存在,可以手工修改参数，调节 开启几组日志来服务于当前mysql数据库,...
MySQL运维｜服务器强制断电后导致mysql无法启动(终极方案)
qq_38200425的博客
12-14 6282
强制断电后导致mysql无法启动 1 强制InnoDB恢复 找到mysql的my.cnf文件,添加一下子两个参数: [mysqld] innodb_force_recovery=6(这个值越小越安全,最开始建议设置为1，如果也无法启动再改为2，以此内推) innodb_purge_thread=0 注意： 只有在紧急情况下才能设置innodb_force_recovery大于0，默认值是0，不进行强制恢复的正常启动。innodb_force_recovery一共有6个级别，举例说明
服务器断电后mysql无法启动_服务器断电后mysql无法启动
weixin_40000702的博客
01-18 372
因意外导致服务器断电，重启后发现mysql起不来了[root@cacti ~]# service mysqld restart停止 mysqld： [确定]MySQL Daemon failed to start.正在启动 mysqld： ...
linux服务器重启后mysql无法运行
ever_evil的博客
01-17 3853
遇到问题的情况是 我在阿里云购买了几个月一个linux云服务器 但是当我重启一次后 却打不开mysql数据库 报错如下ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/tmp 原因是mysql在重启后没有运行 就没有建立对数据库的连接 因此无法连接用代码service mysqld sta
麒麟服务器因停电故障排查与修复教程
本文档详细记录了一次麒麟服务器因停电导致无法正常启动的问题排查过程。当服务器在启动过程中显示麒麟软件LOGO后黑屏，并且只有光标闪烁但无响应时，表明系统可能遇到了硬件或配置问题。 首先，作者通过按下F1键...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值