Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Cannot Reproduce
-
10.3
-
None
-
Hots with Debian 10
Description
Sorry about my English
Today in the morning I noticed that my zabbix server was not working. Initially having a problem with the server, I tried to restart the server or even restart the service, but it did not return to operation.
Analyzing the log, something new came to me and I can't find the problem:
2020-02-24 13:18:12 0 [Note] InnoDB: Using Linux native AIO
|
2020-02-24 13:18:12 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
|
2020-02-24 13:18:12 0 [Note] InnoDB: Uses event mutexes
|
2020-02-24 13:18:12 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
|
2020-02-24 13:18:12 0 [Note] InnoDB: Number of pools: 1
|
2020-02-24 13:18:12 0 [Note] InnoDB: Using generic crc32 instructions
|
2020-02-24 13:18:12 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
|
2020-02-24 13:18:12 0 [Note] InnoDB: Completed initialization of buffer pool
|
2020-02-24 13:18:12 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
|
2020-02-24 13:18:12 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=644349686286
|
2020-02-24 13:18:12 0 [Note] InnoDB: 1 transaction(s) which must be rolled back or cleaned up in total 734 row operations to undo
|
2020-02-24 13:18:12 0 [Note] InnoDB: Trx id counter is 139251516
|
2020-02-24 13:18:12 0 [Note] InnoDB: Starting final batch to recover 2535 pages from redo log.
|
2020-02-24 13:18:12 0 [ERROR] [FATAL] InnoDB: is_short 1, info_and_status_bits 2, offset 99, o_offset 5, mismatch index 18446744073709551610, end_seg_len 19 parsed len 1
|
200224 13:18:12 [ERROR] mysqld got signal 6 ;
|
Alguem poderia me ajudar?
I have no backup of the bank.
Attachments
Issue Links
- relates to
-
-
- Closed
-