使用Innodb jira和confluence重启后报错，请问如何解决

最新推荐文章于 2024-05-06 11:07:47 发布

齊藤杏树

最新推荐文章于 2024-05-06 11:07:47 发布

阅读量182

点赞数

文章标签： jira 数据库 mysql

本文链接：https://blog.csdn.net/Anjuftgugyj/article/details/128728915

版权

//报错信息

230116 17:49:07  InnoDB: Page checksum 72007674 (32bit_calc: 2004547944), prior-to-4.0.14-form checksum 2573639188
InnoDB: stored checksum 4034186223, prior-to-4.0.14-form stored checksum 1842853433
InnoDB: Page lsn 1875706145 1978240991, low 4 bytes of lsn at page end 869465433
InnoDB: Page number (if stored to page already) 5943950,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 4214413127
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 81928.
InnoDB: You may have to recover from a backup.
InnoDB: It is also possible that your operating
InnoDB: system has corrupted its own file cache
InnoDB: and rebooting your computer removes the
InnoDB: error.
InnoDB: If the corrupt page is an index page
InnoDB: you can also try to fix the corruption
InnoDB: by dumping, dropping, and reimporting
InnoDB: the corrupt table. You can use CHECK
InnoDB: TABLE to scan your table for corruption.
InnoDB: See also http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
InnoDB: Ending processing because of a corrupt database page.
230116 17:49:07  InnoDB: Assertion failure in thread 140042661705792 in file buf0buf.c line 4028
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/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
230116 17:49:07 [ERROR] mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.

To report this bug, see http://kb.askmonty.org/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed, 
something is definitely wrong and this may fail.

Server version: 5.5.56-MariaDB
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=0
max_threads=153
thread_count=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 466711 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0x0 thread_stack 0x48000
/usr/libexec/mysqld(my_print_stacktrace+0x3d)[0x55c7a3aef96d]
/usr/libexec/mysqld(handle_fatal_signal+0x515)[0x55c7a3705285]
/lib64/libpthread.so.0(+0xf5e0)[0x7f5e38da55e0]
/lib64/libc.so.6(gsignal+0x37)[0x7f5e374d81f7]
/lib64/libc.so.6(abort+0x148)[0x7f5e374d98e8]
/usr/libexec/mysqld(+0x6920d5)[0x55c7a38f50d5]
/usr/libexec/mysqld(+0x6a38b7)[0x55c7a39068b7]
/usr/libexec/mysqld(+0x68ca17)[0x55c7a38efa17]
/usr/libexec/mysqld(+0x65e0ca)[0x55c7a38c10ca]
/usr/libexec/mysqld(+0x650ed3)[0x55c7a38b3ed3]
/usr/libexec/mysqld(+0x651d3c)[0x55c7a38b4d3c]
/usr/libexec/mysqld(+0x65449e)[0x55c7a38b749e]
/usr/libexec/mysqld(+0x63d7f5)[0x55c7a38a07f5]
/usr/libexec/mysqld(+0x5f4634)[0x55c7a3857634]
/usr/libexec/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x48)[0x55c7a3707308]
/usr/libexec/mysqld(+0x37e38a)[0x55c7a35e138a]
/usr/libexec/mysqld(_Z11plugin_initPiPPci+0x551)[0x55c7a35e6911]
/usr/libexec/mysqld(+0x2efcca)[0x55c7a3552cca]
/usr/libexec/mysqld(_Z11mysqld_mainiPPc+0x5c2)[0x55c7a3555e62]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x7f5e374c4c05]
/usr/libexec/mysqld(+0x2e9e6d)[0x55c7a354ce6d]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
230116 17:49:07 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended
230116 18:27:49 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
230116 18:27:51 [Note] /usr/libexec/mysqld (mysqld 5.5.56-MariaDB) starting as process 1759 ...
230116 18:27:53 InnoDB: The InnoDB memory heap is disabled
230116 18:27:53 InnoDB: Mutexes and rw_locks use GCC atomic builtins
230116 18:27:53 InnoDB: Compressed tables use zlib 1.2.7
230116 18:27:53 InnoDB: Using Linux native AIO
230116 18:27:53 InnoDB: Initializing buffer pool, size = 128.0M
230116 18:27:53 InnoDB: Completed initialization of buffer pool
230116 18:27:53 InnoDB: highest supported file format is Barracuda.
230116 18:27:56  InnoDB: Error: space id and page n:o stored in the page
InnoDB: read in are 4214413127:5943950, should be 0:81928!
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 81928.
InnoDB: You may have to recover from a backup.
230116 18:27:56  InnoDB: Page dump in ascii and hex (16384 bytes):
 len 16384; hex 
//然后是很多行的英文乱码，不是中文乱码
//然后是一行
InnoDB: End of page dump

然后尝试直接新建数据库，把jira每天自动生成的备份文件导入，但是报错了，并且这个备份zip文件不能用rar直接打开。

报错信息：

InnoDB: The first specified data file ./ibdata1 did not exist:
InnoDB: a new database to be created!
230116 18:54:30  InnoDB: Setting file ./ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
230116 18:54:30  InnoDB: Log file ./ib_logfile0 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile0 size to 5 MB
InnoDB: Database physically writes the file full: wait...
230116 18:54:30  InnoDB: Log file ./ib_logfile1 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile1 size to 5 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: 127 rollback segment(s) active.
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
230116 18:54:30  InnoDB: Waiting for the background threads to start
230116 18:54:31 Percona XtraDB (http://www.percona.com) 5.5.52-MariaDB-38.3 started; log sequence number 0
230116 18:54:31 [Note] Plugin 'FEEDBACK' is disabled.
230116 18:54:31 [Note] Server socket created on IP: '0.0.0.0'.
230116 18:54:31 [Note] Event Scheduler: Loaded 0 events
230116 18:54:31 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.5.56-MariaDB'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MariaDB Server
230116 18:57:37 [Note] /usr/libexec/mysqld: Normal shutdown

230116 18:57:37 [Note] Event Scheduler: Purging the queue. 0 events
230116 18:57:37  InnoDB: Starting shutdown...
230116 18:57:40  InnoDB: Shutdown completed; log sequence number 1597945
230116 18:57:40 [Note] /usr/libexec/mysqld: Shutdown complete

230116 18:57:40 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended
230116 18:57:40 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
230116 18:57:40 [Note] /usr/libexec/mysqld (mysqld 5.5.56-MariaDB) starting as process 7370 ...
230116 18:57:40 InnoDB: The InnoDB memory heap is disabled
230116 18:57:40 InnoDB: Mutexes and rw_locks use GCC atomic builtins
230116 18:57:40 InnoDB: Compressed tables use zlib 1.2.7
230116 18:57:40 InnoDB: Using Linux native AIO
230116 18:57:40 InnoDB: Initializing buffer pool, size = 128.0M
230116 18:57:40 InnoDB: Completed initialization of buffer pool
230116 18:57:40 InnoDB: highest supported file format is Barracuda.
230116 18:57:41  InnoDB: Waiting for the background threads to start
230116 18:57:42 Percona XtraDB (http://www.percona.com) 5.5.52-MariaDB-38.3 started; log sequence number 1597945
230116 18:57:42 [Note] Plugin 'FEEDBACK' is disabled.
230116 18:57:42 [Note] Server socket created on IP: '0.0.0.0'.
230116 18:57:42 [Note] Event Scheduler: Loaded 0 events
230116 18:57:42 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.5.56-MariaDB'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MariaDB Server
230116 19:02:19 [Note] /usr/libexec/mysqld: Normal shutdown

230116 19:02:19 [Note] Event Scheduler: Purging the queue. 0 events
230116 19:02:19  InnoDB: Starting shutdown...
230116 19:02:21  InnoDB: Shutdown completed; log sequence number 1597945
230116 19:02:21 [Note] /usr/libexec/mysqld: Shutdown complete

230116 19:02:21 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended
230116 19:04:53 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
230116 19:04:53 [Note] /usr/libexec/mysqld (mysqld 5.5.56-MariaDB) starting as process 9308 ...
230116 19:04:53 InnoDB: The InnoDB memory heap is disabled
230116 19:04:53 InnoDB: Mutexes and rw_locks use GCC atomic builtins
230116 19:04:53 InnoDB: Compressed tables use zlib 1.2.7
230116 19:04:53 InnoDB: Using Linux native AIO
230116 19:04:53 InnoDB: Initializing buffer pool, size = 128.0M
230116 19:04:53 InnoDB: Completed initialization of buffer pool
230116 19:04:53 InnoDB: highest supported file format is Barracuda.
230116 19:04:53  InnoDB: Waiting for the background threads to start
230116 19:04:54 Percona XtraDB (http://www.percona.com) 5.5.52-MariaDB-38.3 started; log sequence number 1597945
230116 19:04:54 [Note] Plugin 'FEEDBACK' is disabled.
230116 19:04:54 [Note] Server socket created on IP: '0.0.0.0'.
230116 19:04:54 [Note] Event Scheduler: Loaded 0 events
230116 19:04:54 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.5.56-MariaDB'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MariaDB Server
230116 19:14:47 [Note] /usr/libexec/mysqld: Normal shutdown

230116 19:14:47 [Note] Event Scheduler: Purging the queue. 0 events
230116 19:14:47  InnoDB: Starting shutdown...
230116 19:14:48  InnoDB: Shutdown completed; log sequence number 1597945
230116 19:14:48 [Note] /usr/libexec/mysqld: Shutdown complete

230116 19:14:48 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended
230116 19:20:07 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
230116 19:20:07 [Note] /usr/libexec/mysqld (mysqld 5.5.56-MariaDB) starting as process 5062 ...
230116 19:20:07 InnoDB: The InnoDB memory heap is disabled
230116 19:20:07 InnoDB: Mutexes and rw_locks use GCC atomic builtins
230116 19:20:07 InnoDB: Compressed tables use zlib 1.2.7
230116 19:20:07 InnoDB: Using Linux native AIO
230116 19:20:07 InnoDB: Initializing buffer pool, size = 128.0M
230116 19:20:07 InnoDB: Completed initialization of buffer pool
230116 19:20:07 InnoDB: highest supported file format is Barracuda.
230116 19:20:07  InnoDB: Waiting for the background threads to start
230116 19:20:08 Percona XtraDB (http://www.percona.com) 5.5.52-MariaDB-38.3 started; log sequence number 1597945
230116 19:20:08 [Note] Plugin 'FEEDBACK' is disabled.
230116 19:20:08 [Note] Server socket created on IP: '0.0.0.0'.
230116 19:20:08 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.5.56-MariaDB'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MariaDB Server
230116 19:23:08 [ERROR] Cannot find or open table jira/AO_0456E7_BAD_CALENDAR_DI from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

之后它直接显示了几乎是几十几百个下面这个信息：

[ERROR] Cannot find or open table jira/upgradetaskhistory from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.