Error: MySQL shutdown unexpectedly.

Problems with the Windows version of XAMPP, questions, comments, and anything related.

Error: MySQL shutdown unexpectedly.

Postby vishalp@lexcis.com » 09. May 2016 11:06

Hello,
I am getting following error when start the mysql. I am unable to solve this problem. :(
Please let me know how to fix it.
3:30:31 PM [mysql] Error: MySQL shutdown unexpectedly.
3:30:31 PM [mysql] This may be due to a blocked port, missing dependencies,
3:30:31 PM [mysql] improper privileges, a crash, or a shutdown by another method.
3:30:31 PM [mysql] Press the Logs button to view error logs and check
3:30:31 PM [mysql] the Windows Event Viewer for more clues
3:30:31 PM [mysql] If you need more help, copy and post this
3:30:31 PM [mysql] entire log window on the forums

Thanks in advance.
vishalp@lexcis.com
 
Posts: 9
Joined: 09. May 2016 09:42
XAMPP version: 3.2.1
Operating System: windows

Re: Error: MySQL shutdown unexpectedly.

Postby dDesign » 09. May 2016 11:49

Did you tried deleting the "ibdata1" file located in "\xampp\mysql\data" and restarting the XAMP app?
dDesign
 
Posts: 10
Joined: 09. May 2016 11:03
XAMPP version: v3.2.1
Operating System: Windows 10

Re: Error: MySQL shutdown unexpectedly.

Postby Altrea » 09. May 2016 15:16

Deleting ibdata1 may result in data loss of all innodb databases!!!
We don't provide any support via personal channels like PM, email, Skype, TeamViewer!

It's like porn for programmers 8)
User avatar
Altrea
AF Moderator
 
Posts: 8293
Joined: 17. August 2009 13:05
XAMPP version: several
Operating System: Windows 10 Pro x64

Re: Error: MySQL shutdown unexpectedly.

Postby vishalp@lexcis.com » 10. May 2016 05:19

thanks for answer dDesign,Altrea.
Yes i did that but if we delete "ibdata1" file, it deletes all databases. I don't want to delete databases. any alternative idea to retrieve database if we delete that file or without deleting that file how i can fix that error.
vishalp@lexcis.com
 
Posts: 9
Joined: 09. May 2016 09:42
XAMPP version: 3.2.1
Operating System: windows

Re: Error: MySQL shutdown unexpectedly.

Postby dDesign » 10. May 2016 07:47

Sorry! I didn't knew that will happen to the database! I feel like stupid because i have the same error and already did delete my ibdata1 file. Glad i can recover it from 27th April.
You may try add the following line below the [mysqld] section in the mysql config file (my.ini) and restart the apache web server and the mysql service afterwards.

[mysqld]
innodb_force_recovery = 4

Make sure u make a backup of the database, tables etc.
dDesign
 
Posts: 10
Joined: 09. May 2016 11:03
XAMPP version: v3.2.1
Operating System: Windows 10

Re: Error: MySQL shutdown unexpectedly.

Postby vishalp@lexcis.com » 10. May 2016 08:12

Yes i did that, below are the logs after edit this line.

2016-05-10 12:38:43 1208 [Note] InnoDB: Started in read only mode
2016-05-10 12:38:43 1208 [Note] InnoDB: Using atomics to ref count buffer pool pages
2016-05-10 12:38:43 1208 [Note] InnoDB: The InnoDB memory heap is disabled
2016-05-10 12:38:43 1208 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2016-05-10 12:38:43 1208 [Note] InnoDB: Memory barrier is not used
2016-05-10 12:38:43 1208 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-05-10 12:38:43 1208 [Note] InnoDB: Not using CPU crc32 instructions
2016-05-10 12:38:43 1208 [Note] InnoDB: Disabling background IO write threads.
2016-05-10 12:38:43 1208 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2016-05-10 12:38:43 1208 [Note] InnoDB: Completed initialization of buffer pool
2016-05-10 12:38:43 1208 [Note] InnoDB: Highest supported file format is Barracuda.
2016-05-10 12:38:43 1208 [Note] InnoDB: The log sequence numbers 1665234 and 1665234 in ibdata files do not match the log sequence number 1264883520 in the ib_logfiles!
2016-05-10 12:38:43 1208 [ERROR] InnoDB: Can't initiate database recovery, running in read-only-mode.
2016-05-10 12:38:43 1208 [ERROR] Plugin 'InnoDB' init function returned error.
2016-05-10 12:38:43 1208 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2016-05-10 12:38:43 1208 [ERROR] Unknown/unsupported storage engine: InnoDB
2016-05-10 12:38:43 1208 [ERROR] Aborting

2016-05-10 12:38:43 1208 [Note] Binlog end
2016-05-10 12:38:43 1208 [Note] Shutting down plugin 'partition'
2016-05-10 12:38:43 1208 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2016-05-10 12:38:43 1208 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2016-05-10 12:38:43 1208 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2016-05-10 12:38:43 1208 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2016-05-10 12:38:43 1208 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2016-05-10 12:38:43 1208 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2016-05-10 12:38:43 1208 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2016-05-10 12:38:43 1208 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2016-05-10 12:38:43 1208 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2016-05-10 12:38:43 1208 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2016-05-10 12:38:43 1208 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2016-05-10 12:38:43 1208 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2016-05-10 12:38:43 1208 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2016-05-10 12:38:43 1208 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2016-05-10 12:38:43 1208 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2016-05-10 12:38:43 1208 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2016-05-10 12:38:43 1208 [Note] Shutting down plugin 'INNODB_METRICS'
2016-05-10 12:38:43 1208 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2016-05-10 12:38:43 1208 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2016-05-10 12:38:43 1208 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2016-05-10 12:38:43 1208 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2016-05-10 12:38:43 1208 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2016-05-10 12:38:43 1208 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2016-05-10 12:38:43 1208 [Note] Shutting down plugin 'INNODB_CMPMEM'
2016-05-10 12:38:43 1208 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2016-05-10 12:38:43 1208 [Note] Shutting down plugin 'INNODB_CMP'
2016-05-10 12:38:43 1208 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2016-05-10 12:38:43 1208 [Note] Shutting down plugin 'INNODB_LOCKS'
2016-05-10 12:38:43 1208 [Note] Shutting down plugin 'INNODB_TRX'
2016-05-10 12:38:43 1208 [Note] Shutting down plugin 'BLACKHOLE'
2016-05-10 12:38:43 1208 [Note] Shutting down plugin 'ARCHIVE'
2016-05-10 12:38:43 1208 [Note] Shutting down plugin 'MRG_MYISAM'
2016-05-10 12:38:43 1208 [Note] Shutting down plugin 'MyISAM'
2016-05-10 12:38:43 1208 [Note] Shutting down plugin 'MEMORY'
2016-05-10 12:38:43 1208 [Note] Shutting down plugin 'CSV'
2016-05-10 12:38:43 1208 [Note] Shutting down plugin 'sha256_password'
2016-05-10 12:38:43 1208 [Note] Shutting down plugin 'mysql_old_password'
2016-05-10 12:38:43 1208 [Note] Shutting down plugin 'mysql_native_password'
2016-05-10 12:38:43 1208 [Note] Shutting down plugin 'binlog'
2016-05-10 12:38:43 1208 [Note] c:\xampp\mysql\bin\mysqld.exe: Shutdown complete
vishalp@lexcis.com
 
Posts: 9
Joined: 09. May 2016 09:42
XAMPP version: 3.2.1
Operating System: windows

Re: Error: MySQL shutdown unexpectedly.

Postby dDesign » 10. May 2016 08:21

Did you try to run it as Administrator? I further have no clue. The reason i think u have to start it as administrator is of the first line:

2016-05-10 12:38:43 1208 [Note] InnoDB: Started in read only mode

"ready only mode"
dDesign
 
Posts: 10
Joined: 09. May 2016 11:03
XAMPP version: v3.2.1
Operating System: Windows 10

Re: Error: MySQL shutdown unexpectedly.

Postby vishalp@lexcis.com » 10. May 2016 08:43

Thanks for your reply; I appreciate your help.

I tried with administrator rights as well:

1:09:18 PM [main] Initializing Control Panel
1:09:18 PM [main] Windows Version: Windows 8 Pro 64-bit
1:09:18 PM [main] XAMPP Version: 1.8.3
1:09:18 PM [main] Control Panel Version: 3.2.1 [ Compiled: May 7th 2013 ]
1:09:18 PM [main] Running with Administrator rights - good!
1:09:18 PM [main] XAMPP Installation Directory: "c:\xampp\"
1:09:18 PM [main] Checking for prerequisites
1:09:18 PM [main] All prerequisites found
1:09:18 PM [main] Initializing Modules
1:09:18 PM [main] Starting Check-Timer
1:09:18 PM [main] Control Panel Ready
1:09:20 PM [mysql] Attempting to start MySQL app...
1:09:20 PM [mysql] Status change detected: running
1:09:21 PM [mysql] Status change detected: stopped
1:09:21 PM [mysql] Error: MySQL shutdown unexpectedly.
1:09:21 PM [mysql] This may be due to a blocked port, missing dependencies,
1:09:21 PM [mysql] improper privileges, a crash, or a shutdown by another method.
1:09:21 PM [mysql] Press the Logs button to view error logs and check
1:09:21 PM [mysql] the Windows Event Viewer for more clues
1:09:21 PM [mysql] If you need more help, copy and post this
1:09:21 PM [mysql] entire log window on the forums


Following is the error log:

2016-05-10 13:09:21 4744 [Note] Plugin 'FEDERATED' is disabled.
2016-05-10 13:09:21 914 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.
2016-05-10 13:09:21 4744 [Note] InnoDB: Started in read only mode
2016-05-10 13:09:21 4744 [Note] InnoDB: Using atomics to ref count buffer pool pages
2016-05-10 13:09:21 4744 [Note] InnoDB: The InnoDB memory heap is disabled
2016-05-10 13:09:21 4744 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2016-05-10 13:09:21 4744 [Note] InnoDB: Memory barrier is not used
2016-05-10 13:09:21 4744 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-05-10 13:09:21 4744 [Note] InnoDB: Not using CPU crc32 instructions
2016-05-10 13:09:21 4744 [Note] InnoDB: Disabling background IO write threads.
2016-05-10 13:09:21 4744 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2016-05-10 13:09:21 4744 [Note] InnoDB: Completed initialization of buffer pool
2016-05-10 13:09:21 4744 [ERROR] InnoDB: Cannot create log files in read-only mode
2016-05-10 13:09:21 4744 [ERROR] Plugin 'InnoDB' init function returned error.
2016-05-10 13:09:21 4744 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2016-05-10 13:09:21 4744 [ERROR] Unknown/unsupported storage engine: InnoDB
2016-05-10 13:09:21 4744 [ERROR] Aborting

2016-05-10 13:09:21 4744 [Note] Binlog end
2016-05-10 13:09:21 4744 [Note] Shutting down plugin 'partition'
2016-05-10 13:09:21 4744 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2016-05-10 13:09:21 4744 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2016-05-10 13:09:21 4744 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2016-05-10 13:09:21 4744 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2016-05-10 13:09:21 4744 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2016-05-10 13:09:21 4744 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2016-05-10 13:09:21 4744 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2016-05-10 13:09:21 4744 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2016-05-10 13:09:21 4744 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2016-05-10 13:09:21 4744 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2016-05-10 13:09:21 4744 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2016-05-10 13:09:21 4744 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2016-05-10 13:09:21 4744 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2016-05-10 13:09:21 4744 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2016-05-10 13:09:21 4744 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2016-05-10 13:09:21 4744 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2016-05-10 13:09:21 4744 [Note] Shutting down plugin 'INNODB_METRICS'
2016-05-10 13:09:21 4744 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2016-05-10 13:09:21 4744 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2016-05-10 13:09:21 4744 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2016-05-10 13:09:21 4744 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2016-05-10 13:09:21 4744 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2016-05-10 13:09:21 4744 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2016-05-10 13:09:21 4744 [Note] Shutting down plugin 'INNODB_CMPMEM'
2016-05-10 13:09:21 4744 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2016-05-10 13:09:21 4744 [Note] Shutting down plugin 'INNODB_CMP'
2016-05-10 13:09:21 4744 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2016-05-10 13:09:21 4744 [Note] Shutting down plugin 'INNODB_LOCKS'
2016-05-10 13:09:21 4744 [Note] Shutting down plugin 'INNODB_TRX'
2016-05-10 13:09:21 4744 [Note] Shutting down plugin 'BLACKHOLE'
2016-05-10 13:09:21 4744 [Note] Shutting down plugin 'ARCHIVE'
2016-05-10 13:09:21 4744 [Note] Shutting down plugin 'MRG_MYISAM'
2016-05-10 13:09:21 4744 [Note] Shutting down plugin 'MyISAM'
2016-05-10 13:09:21 4744 [Note] Shutting down plugin 'MEMORY'
2016-05-10 13:09:21 4744 [Note] Shutting down plugin 'CSV'
2016-05-10 13:09:21 4744 [Note] Shutting down plugin 'sha256_password'
2016-05-10 13:09:21 4744 [Note] Shutting down plugin 'mysql_old_password'
2016-05-10 13:09:21 4744 [Note] Shutting down plugin 'mysql_native_password'
2016-05-10 13:09:21 4744 [Note] Shutting down plugin 'binlog'
2016-05-10 13:09:21 4744 [Note] c:\xampp\mysql\bin\mysqld.exe: Shutdown complete
vishalp@lexcis.com
 
Posts: 9
Joined: 09. May 2016 09:42
XAMPP version: 3.2.1
Operating System: windows

Re: Error: MySQL shutdown unexpectedly.

Postby dDesign » 10. May 2016 10:04

How about the permissions? Folder permission etc.

edit:

2016-05-10 13:09:21 4744 [ERROR] InnoDB: Cannot create log files in read-only mode

Right click on the XAMPP folder and uncheck the Readonly, if this not works. Try to uncheck the read only in folder settings from folder mysql
dDesign
 
Posts: 10
Joined: 09. May 2016 11:03
XAMPP version: v3.2.1
Operating System: Windows 10

Re: Error: MySQL shutdown unexpectedly.

Postby Altrea » 10. May 2016 10:15

dDesign wrote:[mysqld]
innodb_force_recovery = 4

THIS forces InnoDB to start in read-only mode, not any file/folder permission.
We don't provide any support via personal channels like PM, email, Skype, TeamViewer!

It's like porn for programmers 8)
User avatar
Altrea
AF Moderator
 
Posts: 8293
Joined: 17. August 2009 13:05
XAMPP version: several
Operating System: Windows 10 Pro x64

Re: Error: MySQL shutdown unexpectedly.

Postby vishalp@lexcis.com » 10. May 2016 11:08

Nothing works.
I have removed the read-only attribute as well. Have also tried to remove log files and use innodb_force_recovery = 6, still the same error.
vishalp@lexcis.com
 
Posts: 9
Joined: 09. May 2016 09:42
XAMPP version: 3.2.1
Operating System: windows

Re: Error: MySQL shutdown unexpectedly.

Postby dDesign » 10. May 2016 11:51

Aah allright, well i tried, sorry!
dDesign
 
Posts: 10
Joined: 09. May 2016 11:03
XAMPP version: v3.2.1
Operating System: Windows 10

Re: Error: MySQL shutdown unexpectedly.

Postby Altrea » 10. May 2016 12:13

vishalp@lexcis.com wrote:and use innodb_force_recovery = 6, still the same error.

set innodb_force_recovery to 0 and try to start MySQL and show us a fresh log with this setting please.
We don't provide any support via personal channels like PM, email, Skype, TeamViewer!

It's like porn for programmers 8)
User avatar
Altrea
AF Moderator
 
Posts: 8293
Joined: 17. August 2009 13:05
XAMPP version: several
Operating System: Windows 10 Pro x64

Re: Error: MySQL shutdown unexpectedly.

Postby vishalp@lexcis.com » 10. May 2016 15:28

Below are the fresh logs:-

2016-05-10 19:55:31 3476 [Note] Plugin 'FEDERATED' is disabled.
2016-05-10 19:55:31 13b4 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.
2016-05-10 19:55:31 3476 [Note] InnoDB: Using atomics to ref count buffer pool pages
2016-05-10 19:55:31 3476 [Note] InnoDB: The InnoDB memory heap is disabled
2016-05-10 19:55:31 3476 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2016-05-10 19:55:31 3476 [Note] InnoDB: Memory barrier is not used
2016-05-10 19:55:31 3476 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-05-10 19:55:31 3476 [Note] InnoDB: Not using CPU crc32 instructions
2016-05-10 19:55:31 3476 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2016-05-10 19:55:31 3476 [Note] InnoDB: Completed initialization of buffer pool
2016-05-10 19:55:31 3476 [Note] InnoDB: Highest supported file format is Barracuda.
2016-05-10 19:55:31 3476 [Note] InnoDB: The log sequence numbers 1665234 and 1665234 in ibdata files do not match the log sequence number 1665548 in the ib_logfiles!
2016-05-10 19:55:31 3476 [Note] InnoDB: Database was not shutdown normally!
2016-05-10 19:55:31 3476 [Note] InnoDB: Starting crash recovery.
2016-05-10 19:55:31 3476 [Note] InnoDB: Reading tablespace information from the .ibd files...
2016-05-10 19:55:31 3476 [ERROR] InnoDB: checksum mismatch in tablespace .\wp2\wp_comments.ibd (table wp2/wp_comments)
2016-05-10 19:55:31 3476 [Note] InnoDB: Page size:1024 Pages to analyze:64
2016-05-10 19:55:31 3476 [Note] InnoDB: Page size: 1024, Possible space_id count:0
2016-05-10 19:55:31 3476 [Note] InnoDB: Page size:2048 Pages to analyze:64
2016-05-10 19:55:31 3476 [Note] InnoDB: Page size: 2048, Possible space_id count:0
2016-05-10 19:55:31 3476 [Note] InnoDB: Page size:4096 Pages to analyze:44
2016-05-10 19:55:31 3476 [Note] InnoDB: Page size: 4096, Possible space_id count:0
2016-05-10 19:55:31 3476 [Note] InnoDB: Page size:8192 Pages to analyze:22
2016-05-10 19:55:31 3476 [Note] InnoDB: Page size: 8192, Possible space_id count:0
2016-05-10 19:55:31 3476 [Note] InnoDB: Page size:16384 Pages to analyze:11
2016-05-10 19:55:31 3476 [Note] InnoDB: VALID: space:766 page_no:1 page_size:16384
2016-05-10 19:55:31 3476 [Note] InnoDB: VALID: space:766 page_no:2 page_size:16384
2016-05-10 19:55:31 3476 [Note] InnoDB: VALID: space:766 page_no:3 page_size:16384
2016-05-10 19:55:31 3476 [Note] InnoDB: VALID: space:766 page_no:4 page_size:16384
2016-05-10 19:55:31 3476 [Note] InnoDB: VALID: space:766 page_no:5 page_size:16384
2016-05-10 19:55:31 3476 [Note] InnoDB: VALID: space:766 page_no:6 page_size:16384
2016-05-10 19:55:31 3476 [Note] InnoDB: VALID: space:766 page_no:7 page_size:16384
2016-05-10 19:55:31 3476 [Note] InnoDB: VALID: space:766 page_no:8 page_size:16384
2016-05-10 19:55:31 3476 [Note] InnoDB: Page size: 16384, Possible space_id count:1
2016-05-10 19:55:31 3476 [Note] InnoDB: space_id:766, Number of pages matched: 8/8 (16384)
2016-05-10 19:55:31 3476 [Note] InnoDB: Chosen space:766

2016-05-10 19:55:31 3476 [Note] InnoDB: Restoring page 0 of tablespace 766
2016-05-10 19:55:31 3476 [Warning] InnoDB: Doublewrite does not have page_no=0 of space: 766
InnoDB: Error: could not open single-table tablespace file .\wp2\wp_comments.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.
vishalp@lexcis.com
 
Posts: 9
Joined: 09. May 2016 09:42
XAMPP version: 3.2.1
Operating System: windows

Re: Error: MySQL shutdown unexpectedly.

Postby vishalp@lexcis.com » 10. May 2016 15:31

Thanks much for your quick support dDesign.
I appreciate your support.
vishalp@lexcis.com
 
Posts: 9
Joined: 09. May 2016 09:42
XAMPP version: 3.2.1
Operating System: windows

Next

Return to XAMPP for Windows

Who is online

Users browsing this forum: No registered users and 90 guests