|
Задавайте вопросы, мы ответим
Вы не зашли.
Всем добрый день! Помогите с траблом. Не могу запустить сервер. Лог в ниже.
FROM WIN-IPPGO8J5P1F.err:
2018-05-21 09:43:23 7592 Note Plugin 'FEDERATED' is disabled.
2018-05-21 09:43:23 18f4 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2018-05-21 09:43:23 7592 Note InnoDB: Using atomics to ref count buffer pool pages
2018-05-21 09:43:23 7592 Note InnoDB: The InnoDB memory heap is disabled
2018-05-21 09:43:23 7592 Note InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-05-21 09:43:23 7592 Note InnoDB: Compressed tables use zlib 1.2.3
2018-05-21 09:43:23 7592 Note InnoDB: Not using CPU crc32 instructions
2018-05-21 09:43:23 7592 Note InnoDB: Initializing buffer pool, size = 2.0G
2018-05-21 09:43:23 7592 Note InnoDB: Completed initialization of buffer pool
2018-05-21 09:43:23 7592 Note InnoDB: Highest supported file format is Barracuda.
2018-05-21 09:43:23 7592 Note InnoDB: Log scan progressed past the checkpoint lsn 981754678036
2018-05-21 09:43:23 7592 Note InnoDB: Database was not shutdown normally!
2018-05-21 09:43:23 7592 Note InnoDB: Starting crash recovery.
2018-05-21 09:43:23 7592 Note InnoDB: Reading tablespace information from the .ibd files...
2018-05-21 09:43:23 7592 Note InnoDB: Restoring possible half-written data pages
2018-05-21 09:43:23 7592 Note InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 981754686793
2018-05-21 09:43:23 7592 Note InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 [truncated, 311 bytes total]
InnoDB: Original record (compact record)
InnoDB: on that page.
InnoDB: Cannot find the dir slot for record (compact record)
InnoDB: on that page!
2018-05-21 09:43:23 be4 InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex ef275e4c0000004d0000004cffffffff000000e4952391b745bf00000000000000000000018c00892eb882522b26017c2dce00050000023d00000000278b8ac30000000000000000032b0000000000000000000000000000000000000000010002001b696e66696d756d0002000b000073757072656d756d [truncated, 48.1 KB total]
InnoDB: End of page dump
2018-05-21 09:43:24 be4 InnoDB: uncompressed page, stored checksum in field1 4012334668, calculated checksums for field1: crc32 2918712404, innodb 520079298, none 3735928559, stored checksum in field2 228, calculated checksums for field2: crc32 2918712404, [truncated, 474 bytes total]
InnoDB: Page may be an index page where index id is 811
2018-05-21 09:43:24 be4 InnoDB: Assertion failure in thread 3044 in file page0page.cc line 154
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.6/en/ … overy.html
InnoDB: about forcing recovery.
2018-05-21 09:43:27 - Checking server status...
2018-05-21 09:43:27 - Trying to connect to MySQL...
2018-05-21 09:43:27 - Can't connect to MySQL server on '127.0.0.1' (10061) (2003)
2018-05-21 09:43:27 - Assuming server is not running
2018-05-21 09:43:31 - Checking server status...
2018-05-21 09:43:31 - Trying to connect to MySQL...
2018-05-21 09:43:31 - Can't connect to MySQL server on '127.0.0.1' (10061) (2003)
2018-05-21 09:43:31 - Assuming server is not running
Неактивен
