MySQL Forums
Forum List  »  Newbie

cause and prevention way of MySQL Auto Stop
Posted by: JunHyeok Jung
Date: May 07, 2018 07:17PM

Hi, I'm using Windows 7 / MySQL Server 5.6.20.

Phenomenon
1. MySQL auto stop from time to time in Workstation and sometimes stop again even after Service is started
2. OS Error 1117 (or 1217) remains in Mysql Error Log and error occurred in ib_logfile0 or ib_logfile1
3. When service start fails, deletion of ib_logfile will result in normal starting

The hard disk was in sufficient capacity (about 100 GB out of 500 GB in use) and is configured for raid 1.

Out of about 30 PCs, five occurred once each.

MySQL Error Log on the most recent PC is :

2018-05-06 18:16:29 778 InnoDB: Operating system error number 1117 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
2018-05-06 18:16:29 3736 [ERROR] InnoDB: File .\ib_logfile1: 'Windows aio' returned OS error 1217. Cannot continue operation
2018-05-06 18:41:02 2092 [Note] Plugin 'FEDERATED' is disabled.
2018-05-06 18:41:03 2092 [Note] InnoDB: Using atomics to ref count buffer pool pages
2018-05-06 18:41:03 2092 [Note] InnoDB: The InnoDB memory heap is disabled
2018-05-06 18:41:03 2092 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-05-06 18:41:03 2092 [Note] InnoDB: Memory barrier is not used
2018-05-06 18:41:03 2092 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-05-06 18:41:04 2092 [Note] InnoDB: Not using CPU crc32 instructions
2018-05-06 18:41:04 2092 [Note] InnoDB: Initializing buffer pool, size = 326.0M
2018-05-06 18:41:05 2092 [Note] InnoDB: Completed initialization of buffer pool
2018-05-06 18:41:05 2092 [Note] InnoDB: Highest supported file format is Barracuda.
2018-05-06 18:41:05 2092 [Note] InnoDB: Log scan progressed past the checkpoint lsn 13635150730157
2018-05-06 18:41:05 2092 [Note] InnoDB: Database was not shutdown normally!
2018-05-06 18:41:05 2092 [Note] InnoDB: Starting crash recovery.
2018-05-06 18:41:05 2092 [Note] InnoDB: Reading tablespace information from the .ibd files...
2018-05-06 18:41:10 2092 [Note] InnoDB: Restoring possible half-written data pages
2018-05-06 18:41:10 2092 [Note] InnoDB: from the doublewrite buffer...

Log remains with the same error code on all PCs that experienced MySQL Auto Stop.

The workaround for MySQL Auto Stop is to delete ib_logfile.

I am inquiring about the cause and prevention of the error.

The attachment is an ib_logfile1 file with a recent PC error.


Thank you.

Options: ReplyQuote


Subject
Written By
Posted
cause and prevention way of MySQL Auto Stop
May 07, 2018 07:17PM


Sorry, only registered users may post in this forum.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.