MySQL Crash 5.0.2


#1

Windows 10 OS
Upgraded from 4.2.2 to 5.0.2 and ran fine for three days. On day four10-10-2018 the back up ( Using “Backup & Recovery In Windows Using Batch Routine Files” by Holzer) would not run and the system froze. (I have been using this same back up for prior versions and for version 5.0.2 for three days without problems.)
A forced shutdown was required. On 10/11/18 MySQL would not start properly since. Any way to get MySQL to start and run normally or is it necessary to roll back to the last backup? The MySQL error log for the time around the above incidents is below.
Thanks for any thoughts.

2018-10-10 19:07:51 2044 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-10-10 19:07:51 8260 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-10-10 19:07:51 8260 [Note] InnoDB: The InnoDB memory heap is disabled
2018-10-10 19:07:51 8260 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-10-10 19:07:51 8260 [Note] InnoDB: Memory barrier is not used
2018-10-10 19:07:51 8260 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-10-10 19:07:51 8260 [Note] InnoDB: Using generic crc32 instructions
2018-10-10 19:07:51 8260 [Note] InnoDB: Initializing buffer pool, size = 512.0M
2018-10-10 19:07:51 8260 [Note] InnoDB: Completed initialization of buffer pool
2018-10-10 19:07:51 8260 [Note] InnoDB: Highest supported file format is Barracuda.
2018-10-10 19:07:51 8260 [Note] InnoDB: 128 rollback segment(s) are active.
2018-10-10 19:07:51 8260 [Note] InnoDB: Waiting for purge to start
2018-10-10 19:07:51 8260 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.28-76.1 started; log sequence number 985773830
2018-10-10 19:07:51 11960 [Note] InnoDB: Dumping buffer pool(s) not yet started
2018-10-10 19:07:51 8260 [Note] Plugin ‘FEEDBACK’ is disabled.
2018-10-10 19:07:51 8260 [Note] Server socket created on IP: ‘::’.
2018-10-10 19:07:51 8260 [Note] C:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: ‘10.1.13-MariaDB’ socket: ‘’ port: 3306 mariadb.org binary distribution
2018-10-10 19:12:18 10696 [Note] C:\xampp\mysql\bin\mysqld.exe: Normal shutdown

2018-10-10 19:12:18 10696 [Note] Event Scheduler: Purging the queue. 0 events
2018-10-10 19:12:18 9704 [Note] InnoDB: FTS optimize thread exiting.
2018-10-10 19:12:18 10696 [Note] InnoDB: Starting shutdown…
2018-10-10 19:12:20 10696 [Note] InnoDB: Shutdown completed; log sequence number 985773840
2018-10-10 19:12:20 10696 [Note] C:\xampp\mysql\bin\mysqld.exe: Shutdown complete

2018-10-10 19:12:26 2a4c 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-10-10 19:12:26 10828 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-10-10 19:12:26 10828 [Note] InnoDB: The InnoDB memory heap is disabled
2018-10-10 19:12:26 10828 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-10-10 19:12:26 10828 [Note] InnoDB: Memory barrier is not used
2018-10-10 19:12:26 10828 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-10-10 19:12:26 10828 [Note] InnoDB: Using generic crc32 instructions
2018-10-10 19:12:26 10828 [Note] InnoDB: Initializing buffer pool, size = 512.0M
2018-10-10 19:12:26 10828 [Note] InnoDB: Completed initialization of buffer pool
2018-10-10 19:12:26 10828 [Note] InnoDB: Highest supported file format is Barracuda.
2018-10-10 19:12:26 10828 [Note] InnoDB: 128 rollback segment(s) are active.
2018-10-10 19:12:26 10828 [Note] InnoDB: Waiting for purge to start
2018-10-10 19:12:26 10828 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.28-76.1 started; log sequence number 985773840
2018-10-10 19:12:26 7940 [Note] InnoDB: Dumping buffer pool(s) not yet started
2018-10-10 19:12:26 10828 [Note] Plugin ‘FEEDBACK’ is disabled.
2018-10-10 19:12:26 10828 [Note] Server socket created on IP: ‘::’.
2018-10-10 19:12:26 10828 [Note] C:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: ‘10.1.13-MariaDB’ socket: ‘’ port: 3306 mariadb.org binary distribution
2018-10-11 07:19:50 1404 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-10-11 7:19:50 5124 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-10-11 7:19:50 5124 [Note] InnoDB: The InnoDB memory heap is disabled
2018-10-11 7:19:50 5124 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-10-11 7:19:50 5124 [Note] InnoDB: Memory barrier is not used
2018-10-11 7:19:50 5124 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-10-11 7:19:50 5124 [Note] InnoDB: Using generic crc32 instructions
2018-10-11 7:19:51 5124 [Note] InnoDB: Initializing buffer pool, size = 512.0M
2018-10-11 7:19:51 5124 [Note] InnoDB: Completed initialization of buffer pool
2018-10-11 7:19:55 5124 [Note] InnoDB: Highest supported file format is Barracuda.
2018-10-11 7:19:55 5124 [Note] InnoDB: The log sequence numbers 985773840 and 985773840 in ibdata files do not match the log sequence number 985773850 in the ib_logfiles!
2018-10-11 7:19:55 5124 [Note] InnoDB: Database was not shutdown normally!
2018-10-11 7:19:55 5124 [Note] InnoDB: Starting crash recovery.
2018-10-11 7:19:55 5124 [Note] InnoDB: Reading tablespace information from the .ibd files…
2018-10-11 7:20:05 5124 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace openemr/form_care_plan uses space ID: 352 at filepath: .\openemr\form_care_plan.ibd. Cannot open tablespace openemr/form_taskman which uses space ID: 352 at filepath: .\openemr\form_taskman.ibd
InnoDB: Error: could not open single-table tablespace file .\openemr\form_taskman.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.


(Asher Densmore-Lynn) #2

I’d recommend you make a full system backup, if possible – or at least the MySQL directory – and then consider taking InnoDB’s advice and forcing it to attempt recovery, if you don’t hear a better idea. The log delta looks really narrow, I don’t think you’d lose much (if anything)…