Страница 1 из 1

Mysql здыхает

Добавлено: 19 июн 2014, 11:27
KRIK73
Блин не знаю в чем проблема но после установки обновы mysql здыхает
[spoiler] Имя события проблемы: APPCRASH
Имя приложения: mysqld.exe
Версия приложения: 5.6.19.0
Отметка времени приложения: 5368c239
Имя модуля с ошибкой: StackHash_0221
Версия модуля с ошибкой: 6.1.7601.18247
Отметка времени модуля с ошибкой: 521ea8e7
Код исключения: c0000374
Смещение исключения: 000ce753
Версия ОС: 6.1.7601.2.1.0.272.7
Код языка: 1049
Дополнительные сведения 1: 0221
Дополнительные сведения 2: 02210127c788b88c5c259d0c2a068fd1
Дополнительные сведения 3: 6ca7
Дополнительные сведения 4: 6ca7b21c5c6a18fc653810d16b744177[/spoiler]


И после этого фиг запусти приходиться ереустанавливать

[spoiler]2014-06-19 12:25:01 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2014-06-19 12:25:01 876 [Note] Plugin 'FEDERATED' is disabled.
2014-06-19 12:25:01 1160 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.
2014-06-19 12:25:01 876 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-06-19 12:25:01 876 [Note] InnoDB: The InnoDB memory heap is disabled
2014-06-19 12:25:01 876 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-06-19 12:25:01 876 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-06-19 12:25:01 876 [Note] InnoDB: Not using CPU crc32 instructions
2014-06-19 12:25:01 876 [Note] InnoDB: Initializing buffer pool, size = 20.0M
2014-06-19 12:25:01 876 [Note] InnoDB: Completed initialization of buffer pool
2014-06-19 12:25:02 876 [Note] InnoDB: Highest supported file format is Barracuda.
2014-06-19 12:25:02 876 [Note] InnoDB: Log scan progressed past the checkpoint lsn 1622471
2014-06-19 12:25:02 876 [Note] InnoDB: Database was not shutdown normally!
2014-06-19 12:25:02 876 [Note] InnoDB: Starting crash recovery.
2014-06-19 12:25:02 876 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-06-19 12:25:02 876 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace cstrike/superban uses space ID: 19 at filepath: .\cstrike\superban.ibd. Cannot open tablespace gameap/gameap_settings which uses space ID: 19 at filepath: .\gameap\gameap_settings.ibd
InnoDB: Error: could not open single-table tablespace file .\gameap\gameap_settings.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.[/spoiler]

Добавлено: 19 июн 2014, 11:54
nick
Все же написано:

Attempted to open a previously opened tablespace. Previous tablespace cstrike/superban uses space ID: 19 at filepath: .\cstrike\superban.ibd. Cannot open tablespace gameap/gameap_settings which uses space ID: 19 at filepath: .\gameap\gameap_settings.ibd[/code]

Ну и решение предлагается:
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
Чо непонятно?