Help Please, MySql error shutdown unexpectedly

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

Help Please, MySql error shutdown unexpectedly

Postby robiejein » 04. January 2014 04:55

Hi I want to ask is there anybody knows how to fix this error:?

=======================================================================
11:44:30 AM [mysql] Error: MySQL shutdown unexpectedly.
11:44:30 AM [mysql] This may be due to a blocked port, missing dependencies,
11:44:30 AM [mysql] improper privileges, a crash, or a shutdown by another method.
=======================================================================
Pleas do let me know guys. Really appreciated for the help. I'm new to Localhost XAMPP and everytime there's an error I've always restart and reinstall my xampp =( hope anyone can help me on this.

Thank u in advance

[EDIT by Altrea: splitted from original topic because it is unrelated - one thread per unique user and issue rule]
robiejein
 
Posts: 4
Joined: 04. January 2014 04:47
Location: Kuala Belait, Brunei Darussalam
Operating System: Windows 7 Home Premium 64-bit

Re: Help Please, MySql error shutdown unexpectedly

Postby Altrea » 04. January 2014 06:06

Hi robiejein,

We need the entire contents of the XAMPP control panel log window and the mysql_error.log file.
Without information it is impossible to provide remote support.

best wishes,
Altrea
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: Help Please, MySql error shutdown unexpectedly

Postby robiejein » 04. January 2014 07:36

Hi Altrea, Thanks for the reply. Thank You. Here's the entire contents of the XAMPP control panel log window

2:36:50 PM [main] Initializing Control Panel
2:36:50 PM [main] Windows Version: Windows 7 Home Premium SP1 64-bit
2:36:50 PM [main] XAMPP Version: 1.8.3
2:36:50 PM [main] Control Panel Version: 3.2.1 [ Compiled: May 7th 2013 ]
2:36:50 PM [main] Running with Administrator rights - good!
2:36:50 PM [main] XAMPP Installation Directory: "c:\xampp\"
2:36:50 PM [main] Checking for prerequisites
2:36:50 PM [main] All prerequisites found
2:36:50 PM [main] Initializing Modules
2:36:50 PM [main] Starting Check-Timer
2:36:50 PM [main] Control Panel Ready
2:36:59 PM [mysql] Attempting to start MySQL app...
2:36:59 PM [mysql] Status change detected: running
2:36:59 PM [mysql] Status change detected: stopped
2:36:59 PM [mysql] Error: MySQL shutdown unexpectedly.
2:36:59 PM [mysql] This may be due to a blocked port, missing dependencies,
2:36:59 PM [mysql] improper privileges, a crash, or a shutdown by another method.
2:36:59 PM [mysql] Press the Logs button to view error logs and check
2:36:59 PM [mysql] the Windows Event Viewer for more clues
2:36:59 PM [mysql] If you need more help, copy and post this
2:36:59 PM [mysql] entire log window on the forums
Last edited by robiejein on 04. January 2014 07:45, edited 1 time in total.
robiejein
 
Posts: 4
Joined: 04. January 2014 04:47
Location: Kuala Belait, Brunei Darussalam
Operating System: Windows 7 Home Premium 64-bit

Re: Help Please, MySql error shutdown unexpectedly

Postby robiejein » 04. January 2014 07:40

as for the mysql_error.log file here's the content of that file.

2013-12-29 11:22:27 4224 [Note] Plugin 'FEDERATED' is disabled.
2013-12-29 11:22:27 12a0 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.
2013-12-29 11:22:27 4224 [Note] InnoDB: The InnoDB memory heap is disabled
2013-12-29 11:22:27 4224 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-12-29 11:22:27 4224 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-12-29 11:22:27 4224 [Note] InnoDB: Not using CPU crc32 instructions
2013-12-29 11:22:27 4224 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-12-29 11:22:27 4224 [Note] InnoDB: Completed initialization of buffer pool
2013-12-29 11:22:27 4224 [Note] InnoDB: Highest supported file format is Barracuda.
2013-12-29 11:22:27 4224 [Note] InnoDB: The log sequence numbers 1625987 and 1625987 in ibdata files do not match the log sequence number 4125032 in the ib_logfiles!
2013-12-29 11:22:27 4224 [Note] InnoDB: Database was not shutdown normally!
2013-12-29 11:22:27 4224 [Note] InnoDB: Starting crash recovery.
2013-12-29 11:22:27 4224 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-12-29 11:22:28 4224 [Note] InnoDB: Restoring possible half-written data pages
2013-12-29 11:22:28 4224 [Note] InnoDB: from the doublewrite buffer...
2013-12-29 11:22:30 4224 [Note] InnoDB: 128 rollback segment(s) are active.
2013-12-29 11:22:30 4224 [Note] InnoDB: Waiting for purge to start
2013-12-29 11:22:30 4224 [Note] InnoDB: 5.6.14 started; log sequence number 4125032
2013-12-29 11:22:30 4224 [Note] Server hostname (bind-address): '*'; port: 3306
2013-12-29 11:22:30 4224 [Note] IPv6 is available.
2013-12-29 11:22:30 4224 [Note] - '::' resolves to '::';
2013-12-29 11:22:30 4224 [Note] Server socket created on IP: '::'.
2013-12-29 11:22:31 4224 [Note] Event Scheduler: Loaded 0 events
2013-12-29 11:22:31 4224 [Note] c:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '5.6.14' socket: '' port: 3306 MySQL Community Server (GPL)


2014-01-02 20:32:34 4060 [Note] Plugin 'FEDERATED' is disabled.
2014-01-02 20:32:34 f7c 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.
2014-01-02 20:32:34 4060 [Note] InnoDB: The InnoDB memory heap is disabled
2014-01-02 20:32:34 4060 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-01-02 20:32:34 4060 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-01-02 20:32:34 4060 [Note] InnoDB: Not using CPU crc32 instructions
2014-01-02 20:32:34 4060 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-01-02 20:32:34 4060 [Note] InnoDB: Completed initialization of buffer pool
2014-01-02 20:32:34 4060 [Note] InnoDB: Highest supported file format is Barracuda.
2014-01-02 20:32:35 4060 [Note] InnoDB: Log scan progressed past the checkpoint lsn 5354714
2014-01-02 20:32:35 4060 [Note] InnoDB: Database was not shutdown normally!
2014-01-02 20:32:35 4060 [Note] InnoDB: Starting crash recovery.
2014-01-02 20:32:35 4060 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-01-02 20:32:35 4060 [Note] InnoDB: Restoring possible half-written data pages
2014-01-02 20:32:35 4060 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 5354947
2014-01-02 20:32:36 f7c InnoDB: Error: page 193 log sequence number 5358542
InnoDB: is in the future! Current system log sequence number 5354947.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/ ... overy.html
InnoDB: for more information.
2014-01-02 20:32:36 f7c InnoDB: Error: page 211 log sequence number 5358669
InnoDB: is in the future! Current system log sequence number 5354947.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/ ... overy.html
InnoDB: for more information.
2014-01-02 20:32:36 f7c InnoDB: Error: page 212 log sequence number 5358780
InnoDB: is in the future! Current system log sequence number 5354947.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/ ... overy.html
InnoDB: for more information.
2014-01-02 20:32:36 f7c InnoDB: Error: page 219 log sequence number 5358891
InnoDB: is in the future! Current system log sequence number 5354947.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/ ... overy.html
InnoDB: for more information.
2014-01-02 20:32:36 f7c InnoDB: Error: page 522 log sequence number 5362467
InnoDB: is in the future! Current system log sequence number 5354947.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/ ... overy.html
InnoDB: for more information.
2014-01-02 20:32:36 f7c InnoDB: Error: page 439 log sequence number 5364168
InnoDB: is in the future! Current system log sequence number 5354947.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/ ... overy.html
InnoDB: for more information.
2014-01-02 20:32:36 f7c InnoDB: Error: page 375 log sequence number 5378887
InnoDB: is in the future! Current system log sequence number 5354947.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/ ... overy.html
InnoDB: for more information.
2014-01-02 20:32:36 f7c InnoDB: Error: page 376 log sequence number 5379257
InnoDB: is in the future! Current system log sequence number 5354947.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/ ... overy.html
InnoDB: for more information.
2014-01-02 20:32:36 f7c InnoDB: Error: page 457 log sequence number 5393076
InnoDB: is in the future! Current system log sequence number 5354947.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/ ... overy.html
InnoDB: for more information.
2014-01-02 20:32:36 4060 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
2014-01-02 20:32:37 4060 [Note] InnoDB: 128 rollback segment(s) are active.
2014-01-02 20:32:37 4060 [Note] InnoDB: Waiting for purge to start
2014-01-02 20:32:37 f7c InnoDB: Error: page 0 log sequence number 5393843
InnoDB: is in the future! Current system log sequence number 5359021.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/ ... overy.html
InnoDB: for more information.
2014-01-02 20:32:37 4060 [Note] InnoDB: 5.6.14 started; log sequence number 5354947
2014-01-02 20:32:37 4060 [Note] Server hostname (bind-address): '*'; port: 3306
2014-01-02 20:32:37 4060 [Note] IPv6 is available.
2014-01-02 20:32:37 4060 [Note] - '::' resolves to '::';
2014-01-02 20:32:37 4060 [Note] Server socket created on IP: '::'.
2014-01-02 20:32:39 4060 [Note] Event Scheduler: Loaded 0 events
2014-01-02 20:32:39 4060 [Note] c:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '5.6.14' socket: '' port: 3306 MySQL Community Server (GPL)
2014-01-02 20:38:26 e30 InnoDB: Assertion failure in thread 3632 in file trx0purge.cc line 699
InnoDB: Failing assertion: purge_sys->iter.trx_no <= purge_sys->rseg->last_trx_no
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/ ... overy.html
InnoDB: about forcing recovery.
12:38:26 UTC - mysqld got exception 0x80000003 ;
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.
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.

key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=2
max_threads=151
thread_count=1
connection_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 133774 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...
1116da0 mysqld.exe!my_thread_name()
134fc7d mysqld.exe!my_mb_ctype_mb()
117d59c mysqld.exe!xor_string()
117d977 mysqld.exe!xor_string()
117e447 mysqld.exe!xor_string()
117e6f6 mysqld.exe!xor_string()
115a847 mysqld.exe!xor_string()
115aa62 mysqld.exe!xor_string()
75c4336a kernel32.dll!BaseThreadInitThunk()
77219f72 ntdll.dll!RtlInitializeExceptionChain()
77219f45 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.


2014-01-02 20:43:47 2848 [Note] Plugin 'FEDERATED' is disabled.
2014-01-02 20:43:47 c24 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.
2014-01-02 20:43:47 2848 [Note] InnoDB: The InnoDB memory heap is disabled
2014-01-02 20:43:47 2848 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-01-02 20:43:47 2848 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-01-02 20:43:47 2848 [Note] InnoDB: Not using CPU crc32 instructions
2014-01-02 20:43:47 2848 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-01-02 20:43:47 2848 [Note] InnoDB: Completed initialization of buffer pool
2014-01-02 20:43:47 2848 [Note] InnoDB: Highest supported file format is Barracuda.
2014-01-02 20:43:47 2848 [Note] InnoDB: Log scan progressed past the checkpoint lsn 5416498
2014-01-02 20:43:47 2848 [Note] InnoDB: Database was not shutdown normally!
2014-01-02 20:43:47 2848 [Note] InnoDB: Starting crash recovery.
2014-01-02 20:43:47 2848 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-01-02 20:43:47 2880 [Note] Plugin 'FEDERATED' is disabled.
2014-01-02 20:43:47 cf8 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.
2014-01-02 20:43:47 2880 [Note] InnoDB: The InnoDB memory heap is disabled
2014-01-02 20:43:47 2880 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-01-02 20:43:47 2880 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-01-02 20:43:47 2880 [Note] InnoDB: Not using CPU crc32 instructions
2014-01-02 20:43:47 2880 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-01-02 20:43:47 2880 [Note] InnoDB: Completed initialization of buffer pool
2014-01-02 20:43:47 2880 [ERROR] InnoDB: C:\xampp\mysql\data\ibdata1 can't be opened in read-write mode
2014-01-02 20:43:47 2880 [ERROR] InnoDB: The system tablespace must be writable!
2014-01-02 20:43:47 2880 [ERROR] Plugin 'InnoDB' init function returned error.
2014-01-02 20:43:47 2880 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2014-01-02 20:43:47 2880 [ERROR] Unknown/unsupported storage engine: InnoDB
2014-01-02 20:43:47 2880 [ERROR] Aborting

2014-01-02 20:43:47 2880 [Note] Binlog end
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'partition'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'INNODB_METRICS'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'INNODB_CMPMEM'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'INNODB_CMP'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'INNODB_LOCKS'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'INNODB_TRX'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'BLACKHOLE'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'ARCHIVE'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'MRG_MYISAM'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'MyISAM'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'MEMORY'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'CSV'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'sha256_password'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'mysql_old_password'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'mysql_native_password'
2014-01-02 20:43:47 2880 [Note] Shutting down plugin 'binlog'
2014-01-02 20:43:47 2880 [Note] c:\xampp\mysql\bin\mysqld.exe: Shutdown complete

2014-01-02 20:43:48 2848 [Note] InnoDB: Restoring possible half-written data pages
2014-01-02 20:43:48 2848 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 5440549
2014-01-02 20:43:48 2848 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
2014-01-02 20:43:48 2848 [Note] InnoDB: 128 rollback segment(s) are active.
2014-01-02 20:43:48 2848 [Note] InnoDB: Waiting for purge to start
2014-01-02 20:43:48 1648 InnoDB: Assertion failure in thread 5704 in file trx0purge.cc line 699
InnoDB: Failing assertion: purge_sys->iter.trx_no <= purge_sys->rseg->last_trx_no
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/ ... overy.html
InnoDB: about forcing recovery.
12:43:48 UTC - mysqld got exception 0x80000003 ;
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.
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.

key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=151
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 = 133774 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...
2014-01-02 20:43:48 2848 [Note] InnoDB: 5.6.14 started; log sequence number 5440549
2014-01-02 20:43:48 2848 [Note] Server hostname (bind-address): '*'; port: 3306
2014-01-02 20:43:48 2848 [Note] IPv6 is available.
2014-01-02 20:43:48 2848 [Note] - '::' resolves to '::';
2014-01-02 20:43:48 2848 [Note] Server socket created on IP: '::'.
be6da0 mysqld.exe!my_thread_name()
e1fc7d mysqld.exe!my_mb_ctype_mb()
c4d59c mysqld.exe!xor_string()
c4d977 mysqld.exe!xor_string()
c4e447 mysqld.exe!xor_string()
c4e6f6 mysqld.exe!xor_string()
c2a86d mysqld.exe!xor_string()
c2aa62 mysqld.exe!xor_string()
7553336a kernel32.dll!BaseThreadInitThunk()
775e9f72 ntdll.dll!RtlInitializeExceptionChain()
775e9f45 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.
2014-01-02 20:43:48 2848 [Note] Event Scheduler: Loaded 0 events
2014-01-02 20:43:48 2848 [Note] c:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '5.6.14' socket: '' port: 3306 MySQL Community Server (GPL)


[EDIT by Altrea: shortened the log file contents to the essential parts]
robiejein
 
Posts: 4
Joined: 04. January 2014 04:47
Location: Kuala Belait, Brunei Darussalam
Operating System: Windows 7 Home Premium 64-bit

Re: Help Please, MySql error shutdown unexpectedly

Postby Altrea » 04. January 2014 20:41

Okay, so what i can see is that your problem startet at the 2nd January.
Maybe because of a system crash your database was forced to do a crash recovery which wasn't successful.
Badly there is no easy fix for it, so the strategy will be to uninstall and reinstall XAMPP.

If you want to do a database backup first there is maybe a possibility to temporary get your database up for it:
  • open your \xampp\mysql\bin\my.ini
  • search for the line
    Code: Select all
    [mysqld]
  • add the following line line somewhere inside this [mysql] Block
    Code: Select all
    innodb_force_recovery = 4

    (value 4 is recommend, if this will not work try value 6)
  • If MySQL starts successful and the data could be restored, immediately do a database dump.
This setting is NOT for bringing up your database to continue working with it, just for backup purposes!

More to read: http://dev.mysql.com/doc/refman/5.6/en/ ... overy.html
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: Help Please, MySql error shutdown unexpectedly

Postby robiejein » 05. January 2014 05:07

Thanks for the help! Altrea.
robiejein
 
Posts: 4
Joined: 04. January 2014 04:47
Location: Kuala Belait, Brunei Darussalam
Operating System: Windows 7 Home Premium 64-bit

Re: Help Please, MySql error shutdown unexpectedly

Postby Altrea » 05. January 2014 05:11

You are welcome :)
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


Return to XAMPP for Windows

Who is online

Users browsing this forum: DrSeussFreak and 67 guests