hiroshi hatake
cosmo****@gmail*****
2015年 1月 5日 (月) 23:13:17 JST
畑ケです。 Windows版のMroonga 4.09のリリースが遅れていてすいません。。 Windows版Mroongaをビルドして次のようにMroongaをインストールしようとした ところ、 次のような症状がでてしまい、Mroongaのインストールが完了しません。 * mysqld.exeを起動させる * Mroongaをインストールするsqlをmysqlに読み込ませる。 * MySQL Clientがserverのコネクションを失う。 --- cmd> start .\bin\mysqld.exe cmd> .\bin\mysql -u root < .\share\mroonga\install.sql cmd>.\bin\mysql -u root < .\share\mroonga\install.sql ERROR 2013 (HY000) at line 3: Lost connection to MySQL server during query --- EventLogを追うとAPPCRASHと見えます。 --- PS> Get-EventLog Application -Newest 5 | export-csv mysqld_crash_log.csv -Encoding UTF8 --- --- ... "1001","WIN-NIMGKBEE6A0","System.Byte[]","47141"," (0)","0","Information","障害バケット 73781820030、種類 1 イベント名: APPCRASH 応答: 使用不可 Cab ID: 0 問題の署名: P1: mysqld.exe P2: 10.0.15.0 P3: 54aa8353 P4: mysqld.exe P5: 10.0.15.0 P6: 54aa8353 P7: c0000005 P8: 0001e938 P9: P10: ... --- 他にログがでていないか調べたところ、 mysqldがエラーログ([HOSTNAME].err)をdataディレクトリに出していました。 --- 150105 22:35:15 [Note] Event Scheduler: Loaded 0 events 150105 22:35:15 [Note] bin\mysqld: ready for connections. Version: '10.0.15-MariaDB' socket: '' port: 3306 Source distribution 150105 22:35:57 [ERROR] 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. 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: 10.0.15-MariaDB key_buffer_size=134217728 read_buffer_size=131072 max_used_connections=1 max_threads=501 thread_count=1 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1223302 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0x1d79ce98 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... mysqld.exe!test_plugin_options()[sql_plugin.cc:3968] mysqld.exe!plugin_initialize()[sql_plugin.cc:1356] mysqld.exe!finalize_install()[sql_plugin.cc:2039] mysqld.exe!mysql_install_plugin()[sql_plugin.cc:2140] mysqld.exe!mysql_execute_command()[sql_parse.cc:4984] mysqld.exe!mysql_parse()[sql_parse.cc:6407] mysqld.exe!dispatch_command()[sql_parse.cc:1299] mysqld.exe!do_command()[sql_parse.cc:996] mysqld.exe!threadpool_process_request()[threadpool_common.cc:233] mysqld.exe!io_completion_callback()[threadpool_win.cc:568] KERNEL32.DLL!GetSystemDefaultLangID() ntdll.dll!TpStartAsyncIoOperation() ntdll.dll!TpReleaseWork() KERNEL32.DLL!BaseThreadInitThunk() ntdll.dll!RtlInitializeExceptionChain() ntdll.dll!RtlInitializeExceptionChain() Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x1d691c28): INSTALL PLUGIN Mroonga SONAME 'ha_mroonga.dll' Connection ID (thread ID): 11 Status: NOT_KILLED --- Mroongaを登録しようとしているところでmysqldが異常終了しているようです。。。 この問題を解決するのに他に必要そうな情報はありますか？ -------------- next part -------------- 150105 21:50:02 [Note] InnoDB: Using mutexes to ref count buffer pool pages 150105 21:50:02 [Note] InnoDB: The InnoDB memory heap is disabled 150105 21:50:02 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 150105 21:50:02 [Note] InnoDB: Memory barrier is not used 150105 21:50:02 [Note] InnoDB: Compressed tables use zlib 1.2.3 150105 21:50:02 [Note] InnoDB: Not using CPU crc32 instructions 150105 21:50:02 [Note] InnoDB: Initializing buffer pool, size = 128.0M 150105 21:50:02 [Note] InnoDB: Completed initialization of buffer pool 150105 21:50:02 [Note] InnoDB: Highest supported file format is Barracuda. 150105 21:50:02 [Note] InnoDB: 128 rollback segment(s) are active. 150105 21:50:02 [Note] InnoDB: Waiting for purge to start 150105 21:50:02 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.21-70.0 started; log sequence number 1616697 150105 21:50:02 [Note] Plugin 'FEEDBACK' is disabled. 150105 21:50:02 [Note] Server socket created on IP: '::'. 150105 21:52:13 [Note] InnoDB: Using mutexes to ref count buffer pool pages 150105 21:52:13 [Note] InnoDB: The InnoDB memory heap is disabled 150105 21:52:13 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 150105 21:52:13 [Note] InnoDB: Memory barrier is not used 150105 21:52:13 [Note] InnoDB: Compressed tables use zlib 1.2.3 150105 21:52:13 [Note] InnoDB: Not using CPU crc32 instructions 150105 21:52:13 [Note] InnoDB: Initializing buffer pool, size = 128.0M 150105 21:52:13 [Note] InnoDB: Completed initialization of buffer pool 150105 21:52:13 [Note] InnoDB: Highest supported file format is Barracuda. 150105 21:52:13 [Note] InnoDB: 128 rollback segment(s) are active. 150105 21:52:13 [Note] InnoDB: Waiting for purge to start 150105 21:52:13 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.21-70.0 started; log sequence number 1616697 150105 21:52:13 [Note] Plugin 'FEEDBACK' is disabled. 150105 21:52:13 [Note] Server socket created on IP: '::'. 150105 21:54:41 [Note] InnoDB: Using mutexes to ref count buffer pool pages 150105 21:54:41 [Note] InnoDB: The InnoDB memory heap is disabled 150105 21:54:41 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 150105 21:54:41 [Note] InnoDB: Memory barrier is not used 150105 21:54:41 [Note] InnoDB: Compressed tables use zlib 1.2.3 150105 21:54:41 [Note] InnoDB: Not using CPU crc32 instructions 150105 21:54:41 [Note] InnoDB: Initializing buffer pool, size = 128.0M 150105 21:54:41 [Note] InnoDB: Completed initialization of buffer pool 150105 21:54:41 [Note] InnoDB: Highest supported file format is Barracuda. 150105 21:54:41 [Note] InnoDB: The log sequence numbers 1616697 and 1616697 in ibdata files do not match the log sequence number 1616707 in the ib_logfiles! 150105 21:54:41 [Note] InnoDB: Database was not shutdown normally! 150105 21:54:41 [Note] InnoDB: Starting crash recovery. 150105 21:54:41 [Note] InnoDB: Reading tablespace information from the .ibd files... 150105 21:54:41 [Note] InnoDB: Restoring possible half-written data pages 150105 21:54:41 [Note] InnoDB: from the doublewrite buffer... 150105 21:54:41 [Note] InnoDB: 128 rollback segment(s) are active. 150105 21:54:41 [Note] InnoDB: Waiting for purge to start 150105 21:54:41 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.21-70.0 started; log sequence number 1616707 150105 21:54:41 [Note] Plugin 'FEEDBACK' is disabled. 150105 21:54:41 [Note] Server socket created on IP: '::'. 150105 21:54:58 [Note] InnoDB: Using mutexes to ref count buffer pool pages 150105 21:54:58 [Note] InnoDB: The InnoDB memory heap is disabled 150105 21:54:58 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 150105 21:54:58 [Note] InnoDB: Memory barrier is not used 150105 21:54:58 [Note] InnoDB: Compressed tables use zlib 1.2.3 150105 21:54:58 [Note] InnoDB: Not using CPU crc32 instructions 150105 21:54:58 [Note] InnoDB: Initializing buffer pool, size = 128.0M 150105 21:54:58 [Note] InnoDB: Completed initialization of buffer pool 150105 21:54:58 [Note] InnoDB: Highest supported file format is Barracuda. 150105 21:54:58 [Note] InnoDB: The log sequence numbers 1616697 and 1616697 in ibdata files do not match the log sequence number 1616717 in the ib_logfiles! 150105 21:54:58 [Note] InnoDB: Database was not shutdown normally! 150105 21:54:58 [Note] InnoDB: Starting crash recovery. 150105 21:54:58 [Note] InnoDB: Reading tablespace information from the .ibd files... 150105 21:54:58 [Note] InnoDB: Restoring possible half-written data pages 150105 21:54:58 [Note] InnoDB: from the doublewrite buffer... 150105 21:54:58 [Note] InnoDB: 128 rollback segment(s) are active. 150105 21:54:58 [Note] InnoDB: Waiting for purge to start 150105 21:54:58 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.21-70.0 started; log sequence number 1616717 150105 21:54:58 [Note] Plugin 'FEEDBACK' is disabled. 150105 21:54:58 [Note] Server socket created on IP: '::'. 150105 21:55:55 [Note] InnoDB: Using mutexes to ref count buffer pool pages 150105 21:55:55 [Note] InnoDB: The InnoDB memory heap is disabled 150105 21:55:55 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 150105 21:55:55 [Note] InnoDB: Memory barrier is not used 150105 21:55:55 [Note] InnoDB: Compressed tables use zlib 1.2.3 150105 21:55:55 [Note] InnoDB: Not using CPU crc32 instructions 150105 21:55:55 [Note] InnoDB: Initializing buffer pool, size = 128.0M 150105 21:55:55 [Note] InnoDB: Completed initialization of buffer pool 150105 21:55:55 [Note] InnoDB: Highest supported file format is Barracuda. 150105 21:55:55 [Note] InnoDB: The log sequence numbers 1616697 and 1616697 in ibdata files do not match the log sequence number 1616727 in the ib_logfiles! 150105 21:55:55 [Note] InnoDB: Database was not shutdown normally! 150105 21:55:55 [Note] InnoDB: Starting crash recovery. 150105 21:55:55 [Note] InnoDB: Reading tablespace information from the .ibd files... 150105 21:55:55 [Note] InnoDB: Restoring possible half-written data pages 150105 21:55:55 [Note] InnoDB: from the doublewrite buffer... 150105 21:55:55 [Note] InnoDB: 128 rollback segment(s) are active. 150105 21:55:55 [Note] InnoDB: Waiting for purge to start 150105 21:55:55 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.21-70.0 started; log sequence number 1616727 150105 21:55:55 [Note] Plugin 'FEEDBACK' is disabled. 150105 21:55:55 [Note] Server socket created on IP: '::'. 150105 21:56:02 [Note] InnoDB: Using mutexes to ref count buffer pool pages 150105 21:56:02 [Note] InnoDB: The InnoDB memory heap is disabled 150105 21:56:02 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 150105 21:56:02 [Note] InnoDB: Memory barrier is not used 150105 21:56:02 [Note] InnoDB: Compressed tables use zlib 1.2.3 150105 21:56:02 [Note] InnoDB: Not using CPU crc32 instructions 150105 21:56:02 [Note] InnoDB: Initializing buffer pool, size = 128.0M 150105 21:56:02 [Note] InnoDB: Completed initialization of buffer pool 150105 21:56:02 [Note] InnoDB: Highest supported file format is Barracuda. 150105 21:56:02 [Note] InnoDB: The log sequence numbers 1616697 and 1616697 in ibdata files do not match the log sequence number 1616737 in the ib_logfiles! 150105 21:56:02 [Note] InnoDB: Database was not shutdown normally! 150105 21:56:02 [Note] InnoDB: Starting crash recovery. 150105 21:56:02 [Note] InnoDB: Reading tablespace information from the .ibd files... 150105 21:56:02 [Note] InnoDB: Restoring possible half-written data pages 150105 21:56:02 [Note] InnoDB: from the doublewrite buffer... 150105 21:56:02 [Note] InnoDB: 128 rollback segment(s) are active. 150105 21:56:02 [Note] InnoDB: Waiting for purge to start 150105 21:56:02 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.21-70.0 started; log sequence number 1616737 150105 21:56:02 [Note] Plugin 'FEEDBACK' is disabled. 150105 21:56:02 [Note] Server socket created on IP: '::'. 150105 21:56:09 [Note] InnoDB: Using mutexes to ref count buffer pool pages 150105 21:56:09 [Note] InnoDB: The InnoDB memory heap is disabled 150105 21:56:09 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 150105 21:56:09 [Note] InnoDB: Memory barrier is not used 150105 21:56:09 [Note] InnoDB: Compressed tables use zlib 1.2.3 150105 21:56:09 [Note] InnoDB: Not using CPU crc32 instructions 150105 21:56:09 [Note] InnoDB: Initializing buffer pool, size = 128.0M 150105 21:56:09 [Note] InnoDB: Completed initialization of buffer pool 150105 21:56:09 [Note] InnoDB: Highest supported file format is Barracuda. 150105 21:56:09 [Note] InnoDB: The log sequence numbers 1616697 and 1616697 in ibdata files do not match the log sequence number 1616747 in the ib_logfiles! 150105 21:56:09 [Note] InnoDB: Database was not shutdown normally! 150105 21:56:09 [Note] InnoDB: Starting crash recovery. 150105 21:56:09 [Note] InnoDB: Reading tablespace information from the .ibd files... 150105 21:56:09 [Note] InnoDB: Restoring possible half-written data pages 150105 21:56:09 [Note] InnoDB: from the doublewrite buffer... 150105 21:56:10 [Note] InnoDB: 128 rollback segment(s) are active. 150105 21:56:10 [Note] InnoDB: Waiting for purge to start 150105 21:56:10 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.21-70.0 started; log sequence number 1616747 150105 21:56:10 [Note] Plugin 'FEEDBACK' is disabled. 150105 21:56:10 [Note] Server socket created on IP: '::'. 150105 21:56:31 [Note] InnoDB: Using mutexes to ref count buffer pool pages 150105 21:56:31 [Note] InnoDB: The InnoDB memory heap is disabled 150105 21:56:31 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 150105 21:56:31 [Note] InnoDB: Memory barrier is not used 150105 21:56:31 [Note] InnoDB: Compressed tables use zlib 1.2.3 150105 21:56:31 [Note] InnoDB: Not using CPU crc32 instructions 150105 21:56:31 [Note] InnoDB: Initializing buffer pool, size = 128.0M 150105 21:56:31 [Note] InnoDB: Completed initialization of buffer pool 150105 21:56:31 [ERROR] InnoDB: .\ibdata1 can't be opened in read-write mode 150105 21:56:31 [ERROR] InnoDB: The system tablespace must be writable! 150105 21:56:31 [ERROR] Plugin 'InnoDB' init function returned error. 150105 21:56:31 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 150105 21:56:31 [Note] Plugin 'FEEDBACK' is disabled. 150105 21:56:31 [ERROR] Unknown/unsupported storage engine: InnoDB 150105 21:56:31 [ERROR] Aborting 150105 21:56:31 [Note] mysqld: Shutdown complete 150105 21:56:40 [Note] InnoDB: Using mutexes to ref count buffer pool pages 150105 21:56:40 [Note] InnoDB: The InnoDB memory heap is disabled 150105 21:56:40 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 150105 21:56:40 [Note] InnoDB: Memory barrier is not used 150105 21:56:40 [Note] InnoDB: Compressed tables use zlib 1.2.3 150105 21:56:40 [Note] InnoDB: Not using CPU crc32 instructions 150105 21:56:40 [Note] InnoDB: Initializing buffer pool, size = 128.0M 150105 21:56:40 [Note] InnoDB: Completed initialization of buffer pool 150105 21:56:40 [Note] InnoDB: Highest supported file format is Barracuda. 150105 21:56:40 [Note] InnoDB: The log sequence numbers 1616697 and 1616697 in ibdata files do not match the log sequence number 1616757 in the ib_logfiles! 150105 21:56:40 [Note] InnoDB: Database was not shutdown normally! 150105 21:56:40 [Note] InnoDB: Starting crash recovery. 150105 21:56:40 [Note] InnoDB: Reading tablespace information from the .ibd files... 150105 21:56:40 [Note] InnoDB: Restoring possible half-written data pages 150105 21:56:40 [Note] InnoDB: from the doublewrite buffer... 150105 21:56:40 [Note] InnoDB: 128 rollback segment(s) are active. 150105 21:56:40 [Note] InnoDB: Waiting for purge to start 150105 21:56:40 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.21-70.0 started; log sequence number 1616757 150105 21:56:40 [Note] Plugin 'FEEDBACK' is disabled. 150105 21:56:40 [Note] Server socket created on IP: '::'. 150105 21:56:45 [Note] InnoDB: Using mutexes to ref count buffer pool pages 150105 21:56:45 [Note] InnoDB: The InnoDB memory heap is disabled 150105 21:56:45 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 150105 21:56:45 [Note] InnoDB: Memory barrier is not used 150105 21:56:45 [Note] InnoDB: Compressed tables use zlib 1.2.3 150105 21:56:45 [Note] InnoDB: Not using CPU crc32 instructions 150105 21:56:45 [Note] InnoDB: Initializing buffer pool, size = 128.0M 150105 21:56:45 [Note] InnoDB: Completed initialization of buffer pool 150105 21:56:45 [Note] InnoDB: Highest supported file format is Barracuda. 150105 21:56:45 [Note] InnoDB: The log sequence numbers 1616697 and 1616697 in ibdata files do not match the log sequence number 1616767 in the ib_logfiles! 150105 21:56:45 [Note] InnoDB: Database was not shutdown normally! 150105 21:56:45 [Note] InnoDB: Starting crash recovery. 150105 21:56:45 [Note] InnoDB: Reading tablespace information from the .ibd files... 150105 21:56:45 [Note] InnoDB: Restoring possible half-written data pages 150105 21:56:45 [Note] InnoDB: from the doublewrite buffer... 150105 21:56:45 [Note] InnoDB: 128 rollback segment(s) are active. 150105 21:56:45 [Note] InnoDB: Waiting for purge to start 150105 21:56:45 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.21-70.0 started; log sequence number 1616767 150105 21:56:45 [Note] Plugin 'FEEDBACK' is disabled. 150105 21:56:45 [Note] Server socket created on IP: '::'. 150105 21:58:03 [Note] InnoDB: Using mutexes to ref count buffer pool pages 150105 21:58:03 [Note] InnoDB: The InnoDB memory heap is disabled 150105 21:58:03 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 150105 21:58:03 [Note] InnoDB: Memory barrier is not used 150105 21:58:03 [Note] InnoDB: Compressed tables use zlib 1.2.3 150105 21:58:03 [Note] InnoDB: Not using CPU crc32 instructions 150105 21:58:03 [Note] InnoDB: Initializing buffer pool, size = 128.0M 150105 21:58:03 [Note] InnoDB: Completed initialization of buffer pool 150105 21:58:03 [ERROR] InnoDB: .\ibdata1 can't be opened in read-write mode 150105 21:58:03 [ERROR] InnoDB: The system tablespace must be writable! 150105 21:58:03 [ERROR] Plugin 'InnoDB' init function returned error. 150105 21:58:03 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 150105 21:58:03 [Note] Plugin 'FEEDBACK' is disabled. 150105 21:58:03 [ERROR] Unknown/unsupported storage engine: InnoDB 150105 21:58:03 [ERROR] Aborting 150105 21:58:03 [Note] mysqld: Shutdown complete 150105 22:04:07 [Note] InnoDB: Using mutexes to ref count buffer pool pages 150105 22:04:07 [Note] InnoDB: The InnoDB memory heap is disabled 150105 22:04:07 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 150105 22:04:07 [Note] InnoDB: Memory barrier is not used 150105 22:04:07 [Note] InnoDB: Compressed tables use zlib 1.2.3 150105 22:04:07 [Note] InnoDB: Not using CPU crc32 instructions 150105 22:04:07 [Note] InnoDB: Initializing buffer pool, size = 128.0M 150105 22:04:07 [Note] InnoDB: Completed initialization of buffer pool 150105 22:04:07 [Note] InnoDB: Highest supported file format is Barracuda. 150105 22:04:07 [Note] InnoDB: The log sequence numbers 1616697 and 1616697 in ibdata files do not match the log sequence number 1616777 in the ib_logfiles! 150105 22:04:07 [Note] InnoDB: Database was not shutdown normally! 150105 22:04:07 [Note] InnoDB: Starting crash recovery. 150105 22:04:07 [Note] InnoDB: Reading tablespace information from the .ibd files... 150105 22:04:07 [Note] InnoDB: Restoring possible half-written data pages 150105 22:04:07 [Note] InnoDB: from the doublewrite buffer... 150105 22:04:08 [Note] InnoDB: 128 rollback segment(s) are active. 150105 22:04:08 [Note] InnoDB: Waiting for purge to start 150105 22:04:08 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.21-70.0 started; log sequence number 1616777 150105 22:04:08 [Note] Plugin 'FEEDBACK' is disabled. 150105 22:04:08 [Note] Server socket created on IP: '::'. 150105 22:04:46 [Note] InnoDB: Using mutexes to ref count buffer pool pages 150105 22:04:46 [Note] InnoDB: The InnoDB memory heap is disabled 150105 22:04:46 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 150105 22:04:46 [Note] InnoDB: Memory barrier is not used 150105 22:04:46 [Note] InnoDB: Compressed tables use zlib 1.2.3 150105 22:04:46 [Note] InnoDB: Not using CPU crc32 instructions 150105 22:04:46 [Note] InnoDB: Initializing buffer pool, size = 128.0M 150105 22:04:46 [Note] InnoDB: Completed initialization of buffer pool 150105 22:04:46 [Note] InnoDB: Highest supported file format is Barracuda. 150105 22:04:46 [Note] InnoDB: The log sequence numbers 1616697 and 1616697 in ibdata files do not match the log sequence number 1616787 in the ib_logfiles! 150105 22:04:46 [Note] InnoDB: Database was not shutdown normally! 150105 22:04:46 [Note] InnoDB: Starting crash recovery. 150105 22:04:46 [Note] InnoDB: Reading tablespace information from the .ibd files... 150105 22:04:46 [Note] InnoDB: Restoring possible half-written data pages 150105 22:04:46 [Note] InnoDB: from the doublewrite buffer... 150105 22:04:46 [Note] InnoDB: 128 rollback segment(s) are active. 150105 22:04:46 [Note] InnoDB: Waiting for purge to start 150105 22:04:46 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.21-70.0 started; log sequence number 1616787 150105 22:04:46 [Note] Plugin 'FEEDBACK' is disabled. 150105 22:04:46 [Note] Server socket created on IP: '::'. 150105 22:31:17 [Note] InnoDB: Using mutexes to ref count buffer pool pages 150105 22:31:17 [Note] InnoDB: The InnoDB memory heap is disabled 150105 22:31:17 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 150105 22:31:17 [Note] InnoDB: Memory barrier is not used 150105 22:31:17 [Note] InnoDB: Compressed tables use zlib 1.2.3 150105 22:31:17 [Note] InnoDB: Not using CPU crc32 instructions 150105 22:31:17 [Note] InnoDB: Initializing buffer pool, size = 128.0M 150105 22:31:17 [Note] InnoDB: Completed initialization of buffer pool 150105 22:31:17 [Note] InnoDB: Highest supported file format is Barracuda. 150105 22:31:17 [Note] InnoDB: The log sequence numbers 1616697 and 1616697 in ibdata files do not match the log sequence number 1616797 in the ib_logfiles! 150105 22:31:17 [Note] InnoDB: Database was not shutdown normally! 150105 22:31:17 [Note] InnoDB: Starting crash recovery. 150105 22:31:17 [Note] InnoDB: Reading tablespace information from the .ibd files... 150105 22:31:17 [Note] InnoDB: Restoring possible half-written data pages 150105 22:31:17 [Note] InnoDB: from the doublewrite buffer... 150105 22:31:17 [Note] InnoDB: 128 rollback segment(s) are active. 150105 22:31:17 [Note] InnoDB: Waiting for purge to start 150105 22:31:17 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.21-70.0 started; log sequence number 1616797 150105 22:31:17 [Note] Plugin 'FEEDBACK' is disabled. 150105 22:31:17 [Note] Server socket created on IP: '::'. 150105 22:32:02 [Note] InnoDB: Using mutexes to ref count buffer pool pages 150105 22:32:02 [Note] InnoDB: The InnoDB memory heap is disabled 150105 22:32:02 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 150105 22:32:02 [Note] InnoDB: Memory barrier is not used 150105 22:32:02 [Note] InnoDB: Compressed tables use zlib 1.2.3 150105 22:32:02 [Note] InnoDB: Not using CPU crc32 instructions 150105 22:32:02 [Note] InnoDB: Initializing buffer pool, size = 128.0M 150105 22:32:02 [Note] InnoDB: Completed initialization of buffer pool 150105 22:32:02 [Note] InnoDB: Highest supported file format is Barracuda. 150105 22:32:02 [Note] InnoDB: The log sequence numbers 1616697 and 1616697 in ibdata files do not match the log sequence number 1616807 in the ib_logfiles! 150105 22:32:02 [Note] InnoDB: Database was not shutdown normally! 150105 22:32:02 [Note] InnoDB: Starting crash recovery. 150105 22:32:02 [Note] InnoDB: Reading tablespace information from the .ibd files... 150105 22:32:02 [Note] InnoDB: Restoring possible half-written data pages 150105 22:32:02 [Note] InnoDB: from the doublewrite buffer... 150105 22:32:02 [Note] InnoDB: 128 rollback segment(s) are active. 150105 22:32:02 [Note] InnoDB: Waiting for purge to start 150105 22:32:02 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.21-70.0 started; log sequence number 1616807 150105 22:32:02 [Note] Plugin 'FEEDBACK' is disabled. 150105 22:32:02 [Note] Server socket created on IP: '::'. 150105 22:32:02 [Note] Event Scheduler: Loaded 0 events 150105 22:32:02 [Note] mysqld: ready for connections. Version: '10.0.15-MariaDB' socket: '' port: 3306 Source distribution 150105 22:32:09 [ERROR] 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. 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: 10.0.15-MariaDB key_buffer_size=134217728 read_buffer_size=131072 max_used_connections=1 max_threads=501 thread_count=1 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1223302 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0x1de90dd0 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... mysqld.exe!test_plugin_options()[sql_plugin.cc:3968] mysqld.exe!plugin_initialize()[sql_plugin.cc:1356] mysqld.exe!finalize_install()[sql_plugin.cc:2039] mysqld.exe!mysql_install_plugin()[sql_plugin.cc:2140] mysqld.exe!mysql_execute_command()[sql_parse.cc:4984] mysqld.exe!mysql_parse()[sql_parse.cc:6407] mysqld.exe!dispatch_command()[sql_parse.cc:1299] mysqld.exe!do_command()[sql_parse.cc:996] mysqld.exe!threadpool_process_request()[threadpool_common.cc:233] mysqld.exe!io_completion_callback()[threadpool_win.cc:568] KERNEL32.DLL!GetSystemDefaultLangID() ntdll.dll!TpStartAsyncIoOperation() ntdll.dll!TpReleaseWork() KERNEL32.DLL!BaseThreadInitThunk() ntdll.dll!RtlInitializeExceptionChain() ntdll.dll!RtlInitializeExceptionChain() Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x1dea9420): INSTALL PLUGIN Mroonga SONAME 'ha_mroonga.dll' Connection ID (thread ID): 2 Status: NOT_KILLED Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on 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. 150105 22:32:14 [Note] InnoDB: Using mutexes to ref count buffer pool pages 150105 22:32:14 [Note] InnoDB: The InnoDB memory heap is disabled 150105 22:32:14 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 150105 22:32:14 [Note] InnoDB: Memory barrier is not used 150105 22:32:14 [Note] InnoDB: Compressed tables use zlib 1.2.3 150105 22:32:14 [Note] InnoDB: Not using CPU crc32 instructions 150105 22:32:14 [Note] InnoDB: Initializing buffer pool, size = 128.0M 150105 22:32:14 [Note] InnoDB: Completed initialization of buffer pool 150105 22:32:14 [Note] InnoDB: Highest supported file format is Barracuda. 150105 22:32:14 [Note] InnoDB: The log sequence numbers 1616697 and 1616697 in ibdata files do not match the log sequence number 1616817 in the ib_logfiles! 150105 22:32:14 [Note] InnoDB: Database was not shutdown normally! 150105 22:32:14 [Note] InnoDB: Starting crash recovery. 150105 22:32:14 [Note] InnoDB: Reading tablespace information from the .ibd files... 150105 22:32:14 [Note] InnoDB: Restoring possible half-written data pages 150105 22:32:14 [Note] InnoDB: from the doublewrite buffer... 150105 22:32:14 [Note] InnoDB: 128 rollback segment(s) are active. 150105 22:32:14 [Note] InnoDB: Waiting for purge to start 150105 22:32:14 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.21-70.0 started; log sequence number 1616817 150105 22:32:14 [Note] Plugin 'FEEDBACK' is disabled. 150105 22:32:14 [Note] Server socket created on IP: '::'. 150105 22:32:14 [ERROR] mysqld: Table '.\mysql\func' is marked as crashed and should be repaired 150105 22:32:14 [Warning] Checking table: '.\mysql\func' 150105 22:32:14 [ERROR] mysql.func: 1 client is using or hasn't closed the table properly 150105 22:32:14 [Note] Event Scheduler: Loaded 0 events 150105 22:32:14 [Note] mysqld: ready for connections. Version: '10.0.15-MariaDB' socket: '' port: 3306 Source distribution 150105 22:34:33 [ERROR] 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. 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: 10.0.15-MariaDB key_buffer_size=134217728 read_buffer_size=131072 max_used_connections=1 max_threads=501 thread_count=1 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1223302 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0x1e788ed0 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... mysqld.exe!test_plugin_options()[sql_plugin.cc:3968] mysqld.exe!plugin_initialize()[sql_plugin.cc:1356] mysqld.exe!finalize_install()[sql_plugin.cc:2039] mysqld.exe!mysql_install_plugin()[sql_plugin.cc:2140] mysqld.exe!mysql_execute_command()[sql_parse.cc:4984] mysqld.exe!mysql_parse()[sql_parse.cc:6407] mysqld.exe!dispatch_command()[sql_parse.cc:1299] mysqld.exe!do_command()[sql_parse.cc:996] mysqld.exe!threadpool_process_request()[threadpool_common.cc:233] mysqld.exe!io_completion_callback()[threadpool_win.cc:568] KERNEL32.DLL!GetSystemDefaultLangID() ntdll.dll!TpStartAsyncIoOperation() ntdll.dll!TpReleaseWork() KERNEL32.DLL!BaseThreadInitThunk() ntdll.dll!RtlInitializeExceptionChain() ntdll.dll!RtlInitializeExceptionChain() Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x1e799700): INSTALL PLUGIN Mroonga SONAME 'ha_mroonga.dll' Connection ID (thread ID): 2 Status: NOT_KILLED Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on 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. 150105 22:35:15 [Note] InnoDB: Using mutexes to ref count buffer pool pages 150105 22:35:15 [Note] InnoDB: The InnoDB memory heap is disabled 150105 22:35:15 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 150105 22:35:15 [Note] InnoDB: Memory barrier is not used 150105 22:35:15 [Note] InnoDB: Compressed tables use zlib 1.2.3 150105 22:35:15 [Note] InnoDB: Not using CPU crc32 instructions 150105 22:35:15 [Note] InnoDB: Initializing buffer pool, size = 128.0M 150105 22:35:15 [Note] InnoDB: Completed initialization of buffer pool 150105 22:35:15 [Note] InnoDB: Highest supported file format is Barracuda. 150105 22:35:15 [Note] InnoDB: The log sequence numbers 1616697 and 1616697 in ibdata files do not match the log sequence number 1616827 in the ib_logfiles! 150105 22:35:15 [Note] InnoDB: Database was not shutdown normally! 150105 22:35:15 [Note] InnoDB: Starting crash recovery. 150105 22:35:15 [Note] InnoDB: Reading tablespace information from the .ibd files... 150105 22:35:15 [Note] InnoDB: Restoring possible half-written data pages 150105 22:35:15 [Note] InnoDB: from the doublewrite buffer... 150105 22:35:15 [Note] InnoDB: 128 rollback segment(s) are active. 150105 22:35:15 [Note] InnoDB: Waiting for purge to start 150105 22:35:15 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.21-70.0 started; log sequence number 1616827 150105 22:35:15 [Note] Plugin 'FEEDBACK' is disabled. 150105 22:35:15 [Note] Server socket created on IP: '::'. 150105 22:35:15 [ERROR] mysqld: Table '.\mysql\func' is marked as crashed and should be repaired 150105 22:35:15 [Warning] Checking table: '.\mysql\func' 150105 22:35:15 [ERROR] mysql.func: 1 client is using or hasn't closed the table properly 150105 22:35:15 [Note] Event Scheduler: Loaded 0 events 150105 22:35:15 [Note] bin\mysqld: ready for connections. Version: '10.0.15-MariaDB' socket: '' port: 3306 Source distribution 150105 22:35:57 [ERROR] 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. 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: 10.0.15-MariaDB key_buffer_size=134217728 read_buffer_size=131072 max_used_connections=1 max_threads=501 thread_count=1 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1223302 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0x1d79ce98 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... mysqld.exe!test_plugin_options()[sql_plugin.cc:3968] mysqld.exe!plugin_initialize()[sql_plugin.cc:1356] mysqld.exe!finalize_install()[sql_plugin.cc:2039] mysqld.exe!mysql_install_plugin()[sql_plugin.cc:2140] mysqld.exe!mysql_execute_command()[sql_parse.cc:4984] mysqld.exe!mysql_parse()[sql_parse.cc:6407] mysqld.exe!dispatch_command()[sql_parse.cc:1299] mysqld.exe!do_command()[sql_parse.cc:996] mysqld.exe!threadpool_process_request()[threadpool_common.cc:233] mysqld.exe!io_completion_callback()[threadpool_win.cc:568] KERNEL32.DLL!GetSystemDefaultLangID() ntdll.dll!TpStartAsyncIoOperation() ntdll.dll!TpReleaseWork() KERNEL32.DLL!BaseThreadInitThunk() ntdll.dll!RtlInitializeExceptionChain() ntdll.dll!RtlInitializeExceptionChain() Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x1d691c28): INSTALL PLUGIN Mroonga SONAME 'ha_mroonga.dll' Connection ID (thread ID): 11 Status: NOT_KILLED Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on 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.
