Apache Friends Support Forum

Hi,

Just updated to the xampp 1.8.3. Upon running xampp control panel, apache started while mysql won't. Error message as follows:

11:56:30 AM [mysql] Status change detected: running
11:56:31 AM [mysql] Status change detected: stopped
11:56:31 AM [mysql] Error: MySQL shutdown unexpectedly.
11:56:31 AM [mysql] This may be due to a blocked port, missing dependencies,
11:56:31 AM [mysql] improper privileges, a crash, or a shutdown by another method.
11:56:31 AM [mysql] Press the Logs button to view error logs and check
11:56:31 AM [mysql] the Windows Event Viewer for more clues
11:56:31 AM [mysql] If you need more help, copy and post this
11:56:31 AM [mysql] entire log window on the forums

I shutdown my firewall but still the same...

Thanks.

- Sean

Hi Sean,

=> [FGA] Insufficient debug information

Best wishes,
Altrea

Xampp version 1.8.3
OS - Windows 7 Ultimate 64 Bit

MySQL Log:

2014-02-26 10:49:36 8276 [Note] Plugin 'FEDERATED' is disabled.
2014-02-26 10:49:36 2208 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-02-26 10:49:36 8276 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-02-26 10:49:36 8276 [Note] InnoDB: The InnoDB memory heap is disabled
2014-02-26 10:49:36 8276 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-02-26 10:49:36 8276 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-02-26 10:49:36 8276 [Note] InnoDB: Not using CPU crc32 instructions
2014-02-26 10:49:36 8276 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-02-26 10:49:36 8276 [Note] InnoDB: Completed initialization of buffer pool
2014-02-26 10:49:36 8276 [Note] InnoDB: Highest supported file format is Barracuda.
2014-02-26 10:49:36 8276 [Warning] InnoDB: Resizing redo log from 2*3072 to 2*320 pages, LSN=1625987
2014-02-26 10:49:36 8276 [Warning] InnoDB: Starting to delete and rewrite log files.
2014-02-26 10:49:36 8276 [Note] InnoDB: Setting log file C:\xampp1\mysql\data\ib_logfile101 size to 5 MB
2014-02-26 10:49:37 8276 [Note] InnoDB: Setting log file C:\xampp1\mysql\data\ib_logfile1 size to 5 MB
2014-02-26 10:49:37 8276 [Note] InnoDB: Renaming log file C:\xampp1\mysql\data\ib_logfile101 to C:\xampp1\mysql\data\ib_logfile0
2014-02-26 10:49:37 2208 InnoDB: Operating system error number 183 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
2014-02-26 10:49:37 8276 [ERROR] InnoDB: File C:\xampp1\mysql\data\ib_logfile101: 'rename' returned OS error 283.
2014-02-26 10:49:37 2208 InnoDB: Assertion failure in thread 8712 in file srv0start.cc line 709
InnoDB: Failing assertion: success
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/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
02:49:37 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 = 133777 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...
15d8300 mysqld.exe!my_thread_name()
1811d3d mysqld.exe!my_mb_ctype_mb()
164fd32 mysqld.exe!murmur3_32()
160b97a mysqld.exe!murmur3_32()
1389e60 mysqld.exe!?ha_initialize_handlerton@@YAHPAUst_plugin_int@@@Z()
13c3f9e mysqld.exe!?plugin_lock_by_name@@YAPAUst_plugin_int@@PAVTHD@@PBUst_mysql_lex_string@@H@Z()
13c8624 mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
138156b mysqld.exe!?init_common_variables@@YAHXZ()
1382278 mysqld.exe!?win_main@@YAHHPAPAD@Z()
13827e7 mysqld.exe!?mysql_service@@YAHPAX@Z()
180c89a mysqld.exe!my_mb_ctype_mb()
77033677 kernel32.dll!BaseThreadInitThunk()
77ea9f42 ntdll.dll!RtlInitializeExceptionChain()
77ea9f15 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.