前提・実現したいこと
ただいま作成しているbatファイルのなかでMySQLをセットアップする過程があります。
その中で、一度MySQLを普通にインストールし、一度サービスを止めて
C:\ProgramData\MySQL\MySQL Server 5.7 下の
my.iniをリネームし、編集済みのmy.iniを入れて
サービスを起動します。
するとサービスの起動がうまくいきません。
気になるのは、windows8.1 x64で行った場合特に問題が起きず
windows7 x86で行うとエラーが起きるということです。
発生している問題・エラーメッセージ
以下エラーログになります
2019-05-08T05:51:56.310790Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details). 2019-05-08T05:51:56.310790Z 0 [Warning] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release. 2019-05-08T05:51:56.320805Z 0 [Note] C:\Program Files\MySQL\MySQL Server 5.7\bin\mysqld.exe (mysqld 5.7.25-log) starting as process 2856 ... 2019-05-08T05:51:56.330819Z 0 [Warning] option 'innodb-autoextend-increment': unsigned value 67108864 adjusted to 1000 2019-05-08T05:51:56.330819Z 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 2019-05-08T05:51:56.330819Z 0 [Note] InnoDB: Uses event mutexes 2019-05-08T05:51:56.330819Z 0 [Note] InnoDB: Memory barrier is not used 2019-05-08T05:51:56.330819Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2019-05-08T05:51:56.330819Z 0 [Note] InnoDB: Number of pools: 1 2019-05-08T05:51:56.330819Z 0 [Note] InnoDB: Not using CPU crc32 instructions 2019-05-08T05:51:56.330819Z 0 [Note] InnoDB: Initializing buffer pool, total size = 0M, instances = 8, chunk size = 128M 2019-05-08T05:51:56.340834Z 0 [Note] InnoDB: Completed initialization of buffer pool 05:51:56 UTC - mysqld got exception 0xc0000005 ; 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. Attempting to collect some information that could help diagnose the problem. As this is a crash and something is definitely wrong, the information collection process might fail. key_buffer_size=8388608 read_buffer_size=65536 max_used_connections=0 max_threads=100 thread_count=0 connection_count=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 66689 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... 10cc88d mysqld.exe!?reserve@?$vector@EV?$allocator@E@std@@@std@@QAEXI@Z() 111915f mysqld.exe!?reserve@?$vector@EV?$allocator@E@std@@@std@@QAEXI@Z() fd2397 mysqld.exe!?reserve@?$vector@EV?$allocator@E@std@@@std@@QAEXI@Z() fcefee mysqld.exe!?reserve@?$vector@EV?$allocator@E@std@@@std@@QAEXI@Z() f2afe2 mysqld.exe!?reserve@?$vector@EV?$allocator@E@std@@@std@@QAEXI@Z() 9052c5 mysqld.exe!?ha_initialize_handlerton@@YAHPAUst_plugin_int@@@Z() 9e793a mysqld.exe!?plugin_foreach_with_mask@@YA_NPAVTHD@@PAP6AD0PAUst_plugin_int@@PAX@ZHI2@Z() 9e8e5c mysqld.exe!?plugin_register_builtin_and_init_core_se@@YA_NPAHPAPAD@Z() 8c983c mysqld.exe!?init_connection_acceptor@?$Connection_acceptor@VShared_mem_listener@@@@QAE_NXZ() 8ce219 mysqld.exe!?win_main@@YAHHPAPAD@Z() 8cbd8e mysqld.exe!?mysql_service@@YAHPAX@Z() 71c5c9fd MSVCR120.dll!_endthread() 76d6ef3c kernel32.dll!BaseThreadInitThunk() 772c3618 ntdll.dll!RtlInitializeExceptionChain() 772c35eb ntdll.dll!RtlInitializeExceptionChain() 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.
試したこと
・my.iniにinnodb_force_recovery=1 を追加。
・my.iniアクセス権限Network Serviceをフルコントロールに。
補足情報(FW/ツールのバージョンなど)
mysqlインストーラ:5.7.25.0
回答1件
あなたの回答
tips
プレビュー