mysql数据库未知原因故障，重新启动时报找不到pid的故障，之后备份删除了data目录下的ib_logfile0和ib_logfile1文件，重新启动依旧失败
首先,pid不存在的报错指的是,mysqld进程没有成功启动.
具体错误的原因,根据给出的日志看,最开始启动失败,Operating system error number 2 in a file operation这个错误,一般见于配置文件错误,没有指定对应的innodb数据目录导致的失败.或者数据文件权限错误等.
后来删除了innodb日志文件之后,就是纯粹的没有redo用于崩溃恢复导致数据库无法启动了.
如果确实需要启动数据库,可以设置innodb_force_recovery为6尝试重启拯救数据.
最糟糕的情况下,可能需要另外的数据抽取工具直接从数据文件抽取数据,而不能依赖innodb本身的机制.
评论
有用 0你好：
感谢您的回复，在阅读完您的建议后，我检查了一下数据库文件的权限配置，确认没有误修改过，之后我修改了innodb_force_recovery参数为6，但是依然启动mysql失败，错误信息还是pid不存在，mysql错误日志如下：
190319 15:10:46 mysqld_safe Starting mysqld daemon with databases from /var/local/mysql/data
2019-03-19 15:10:46 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2019-03-19 15:10:46 2952 [Note] Plugin 'FEDERATED' is disabled.
2019-03-19 15:10:46 2952 [Note] InnoDB: Started in read only mode
2019-03-19 15:10:46 2952 [Note] InnoDB: Using atomics to ref count buffer pool pages
2019-03-19 15:10:46 2952 [Note] InnoDB: The InnoDB memory heap is disabled
2019-03-19 15:10:46 2952 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-03-19 15:10:46 2952 [Note] InnoDB: Memory barrier is not used
2019-03-19 15:10:46 2952 [Note] InnoDB: Compressed tables use zlib 1.2.3
2019-03-19 15:10:46 2952 [Note] InnoDB: Using Linux native AIO
2019-03-19 15:10:46 2952 [Note] InnoDB: Using CPU crc32 instructions
2019-03-19 15:10:46 2952 [Note] InnoDB: Disabling background IO write threads.
2019-03-19 15:10:46 2952 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2019-03-19 15:10:46 2952 [Note] InnoDB: Completed initialization of buffer pool
2019-03-19 15:10:46 2952 [Note] InnoDB: Highest supported file format is Barracuda.
2019-03-19 15:10:46 2952 [Note] InnoDB: The user has set SRV_FORCE_NO_LOG_REDO on, skipping log redo
2019-03-19 15:10:46 2952 [ERROR] InnoDB: Change buffer must be empty when --innodb-read-only is set!
2019-03-19 15:10:46 2952 [ERROR] Plugin 'InnoDB' init function returned error.
2019-03-19 15:10:46 2952 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2019-03-19 15:10:46 2952 [ERROR] Unknown/unsupported storage engine: InnoDB
2019-03-19 15:10:46 2952 [ERROR] Aborting
2019-03-19 15:10:46 2952 [Note] Binlog end
2019-03-19 15:10:46 2952 [Note] Shutting down plugin 'partition'
2019-03-19 15:10:46 2952 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2019-03-19 15:10:46 2952 [Note] Shutting down plugin 'BLACKHOLE'
2019-03-19 15:10:46 2952 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2019-03-19 15:10:46 2952 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2019-03-19 15:10:46 2952 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2019-03-19 15:10:46 2952 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2019-03-19 15:10:46 2952 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2019-03-19 15:10:46 2952 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2019-03-19 15:10:46 2952 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2019-03-19 15:10:46 2952 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2019-03-19 15:10:46 2952 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2019-03-19 15:10:46 2952 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2019-03-19 15:10:46 2952 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2019-03-19 15:10:46 2952 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2019-03-19 15:10:46 2952 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2019-03-19 15:10:46 2952 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2019-03-19 15:10:46 2952 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2019-03-19 15:10:46 2952 [Note] Shutting down plugin 'INNODB_METRICS'
2019-03-19 15:10:46 2952 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2019-03-19 15:10:46 2952 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2019-03-19 15:10:46 2952 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2019-03-19 15:10:46 2952 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2019-03-19 15:10:46 2952 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2019-03-19 15:10:46 2952 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2019-03-19 15:10:46 2952 [Note] Shutting down plugin 'INNODB_CMPMEM'
2019-03-19 15:10:46 2952 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2019-03-19 15:10:46 2952 [Note] Shutting down plugin 'INNODB_CMP'
2019-03-19 15:10:46 2952 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2019-03-19 15:10:46 2952 [Note] Shutting down plugin 'INNODB_LOCKS'
2019-03-19 15:10:46 2952 [Note] Shutting down plugin 'INNODB_TRX'
2019-03-19 15:10:46 2952 [Note] Shutting down plugin 'ARCHIVE'
2019-03-19 15:10:46 2952 [Note] Shutting down plugin 'MyISAM'
2019-03-19 15:10:46 2952 [Note] Shutting down plugin 'CSV'
2019-03-19 15:10:46 2952 [Note] Shutting down plugin 'MRG_MYISAM'
2019-03-19 15:10:46 2952 [Note] Shutting down plugin 'MEMORY'
2019-03-19 15:10:46 2952 [Note] Shutting down plugin 'sha256_password'
2019-03-19 15:10:46 2952 [Note] Shutting down plugin 'mysql_old_password'
2019-03-19 15:10:46 2952 [Note] Shutting down plugin 'mysql_native_password'
2019-03-19 15:10:46 2952 [Note] Shutting down plugin 'binlog'
2019-03-19 15:10:46 2952 [Note] /var/local/mysql/bin/mysqld: Shutdown complete
190319 15:10:46 mysqld_safe mysqld from pid file /var/local/mysql/data/ZW-WEB01.pid ended
请问是否还有方法启动修复数据库，如不能修复，在目前情况下，是否可以直接拷贝数据文件进行异地恢复？
谢谢
评论 有用 0
墨值悬赏