XAMPP v3.2.1 - Error: MySQL shutdown unexpectedly - mysql

Hi and thanks for helping.
For some reason MySQL is not working on my XAMPP, I run it as administrator in Windows 10 and its not installed on the default "program files" folder. Here is the console error:
17:01:11 [mysql] Error: MySQL shutdown unexpectedly.
17:01:11 [mysql] This may be due to a blocked port, missing dependencies,
17:01:11 [mysql] improper privileges, a crash, or a shutdown by another method.
17:01:11 [mysql] Press the Logs button to view error logs and check
17:01:11 [mysql] the Windows Event Viewer for more clues
17:01:11 [mysql] If you need more help, copy and post this
17:01:11 [mysql] entire log window on the forums
And here is the log:
2015-11-04 17:01:06 25a4 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.
151104 17:01:06 [Note] InnoDB: Using mutexes to ref count buffer pool pages
151104 17:01:06 [Note] InnoDB: The InnoDB memory heap is disabled
151104 17:01:06 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
151104 17:01:06 [Note] InnoDB: Memory barrier is not used
151104 17:01:06 [Note] InnoDB: Compressed tables use zlib 1.2.3
151104 17:01:06 [Note] InnoDB: Not using CPU crc32 instructions
151104 17:01:06 [Note] InnoDB: Initializing buffer pool, size = 16.0M
151104 17:01:06 [Note] InnoDB: Completed initialization of buffer pool
151104 17:01:06 [Note] InnoDB: The first specified data file E:\xampp\mysql\data\ibdata1 did not exist: a new database to be created!
151104 17:01:06 [Note] InnoDB: Setting file E:\xampp\mysql\data\ibdata1 size to 10 MB
151104 17:01:06 [Note] InnoDB: Database physically writes the file full: wait...
151104 17:01:06 [ERROR] InnoDB: Cannot create E:\xampp\mysql\data\ib_logfile101
151104 17:01:06 [ERROR] Plugin 'InnoDB' init function returned error.
151104 17:01:06 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
151104 17:01:06 [Note] Plugin 'FEEDBACK' is disabled.
151104 17:01:06 [ERROR] Unknown/unsupported storage engine: InnoDB
151104 17:01:06 [ERROR] Aborting
151104 17:01:06 [Note] E:\xampp\mysql\bin\mysqld.exe: Shutdown complete
I would appreciate any help, thanks.

Related

XAMPP error with running MySQL

I have problem witch XAMPP. When I try to run MySQL, XAMPP shows this:
12:37:02 [mysql] Error: MySQL shutdown unexpectedly.
12:37:02 [mysql] This may be due to a blocked port, missing dependencies,
12:37:02 [mysql] improper privileges, a crash, or a shutdown by another method.
12:37:02 [mysql] Press the Logs button to view error logs and check
12:37:02 [mysql] the Windows Event Viewer for more clues
12:37:02 [mysql] If you need more help, copy and post this
12:37:02 [mysql] entire log window on the forums
I've changed ports to 3307 in
C:\xampp\mysql\bin\my.ini
and in C:\xampp\php\php.ini to mysql.default_port=3307
mysqli.default_port=3307.
I've also deleted ib_logfile1 in C:\xampp\mysql\data
, but it still doesn't work.
Error logs:
2017-08-17 12:27:00 2050 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.
2017-08-17 12:27:00 8272 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB. `
2017-08-17 12:27:00 8272 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-08-17 12:27:00 8272 [Note] InnoDB: The InnoDB memory heap is disabled
2017-08-17 12:27:00 8272 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-08-17 12:27:00 8272 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-08-17 12:27:00 8272 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-08-17 12:27:00 8272 [Note] InnoDB: Using generic crc32 instructions
2017-08-17 12:27:00 8272 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-08-17 12:27:00 8272 [Note] InnoDB: Completed initialization of buffer pool
2017-08-17 12:27:00 8272 [Note] InnoDB: The first specified data file C:\xampp\mysql\data\ibdata1 did not exist: a new database to be created!
2017-08-17 12:27:00 8272 [Note] InnoDB: Setting file C:\xampp\mysql\data\ibdata1 size to 10 MB
2017-08-17 12:27:00 8272 [ERROR] InnoDB: Cannot create C:\xampp\mysql\data\ib_logfile101
2017-08-17 12:27:00 8272 [ERROR] Plugin 'InnoDB' init function returned error.
2017-08-17 12:27:00 8272 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-08-17 12:27:00 8272 [Note] Plugin 'FEEDBACK' is disabled.
2017-08-17 12:27:00 8272 [ERROR] Unknown/unsupported storage engine: InnoDB
2017-08-17 12:27:00 8272 [ERROR] Aborting
Any help is appreciated. Thanks
MySQL is telling you exactly why it cannot start:
[ERROR] InnoDB: Cannot create C:\xampp\mysql\data\ib_logfile101
Hence I suggest the first thing you do is to check that c:\xampp\mysql\data exists and is writeable by the DBMS user.
First stop the service on the xampp control panel,
then click on the red cross on the left to install the service on your computer,
then the icon will become a green tick,
then start the service as administrator.
It should be working alright.
Open the XAMPP control panel and stop the actions.
Open services and go to MySql80.
Stop the service.
Start the service.

Error in Starting the MySQL from XAMPP 3.2.1

I am using XAMPP on my windows machine for PHP and MySQL. Whenever I attempted to the start the MySQL server from the XAMPP Control Panel V3.2.1. Only Apache server is starting and MySQL stops with the following error.
Error: MySQL shutdown unexpectedly.
11:41:12 AM [mysql] This may be due to a blocked port, missing dependencies,
11:41:12 AM [mysql] improper privileges, a crash, or a shutdown by another method.
11:41:12 AM [mysql] Press the Logs button to view error logs and check
11:41:12 AM [mysql] the Windows Event Viewer for more clues
11:41:12 AM [mysql] If you need more help, copy and post this
11:41:12 AM [mysql] entire log window on the forums
Also when I checked my log. I found the following error
2017-05-15 11:48:08 bc8 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.
170515 11:48:08 [Note] InnoDB: Using mutexes to ref count buffer pool pages
170515 11:48:08 [Note] InnoDB: The InnoDB memory heap is disabled
170515 11:48:08 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
170515 11:48:08 [Note] InnoDB: Memory barrier is not used
170515 11:48:08 [Note] InnoDB: Compressed tables use zlib 1.2.3
170515 11:48:08 [Note] InnoDB: Not using CPU crc32 instructions
170515 11:48:08 [Note] InnoDB: Initializing buffer pool, size = 16.0M
170515 11:48:08 [Note] InnoDB: Completed initialization of buffer pool
170515 11:48:08 [Note] InnoDB: Highest supported file format is Barracuda.
170515 11:48:08 [Note] InnoDB: Log scan progressed past the checkpoint lsn 12638736
170515 11:48:08 [Note] InnoDB: Database was not shutdown normally!
170515 11:48:08 [Note] InnoDB: Starting crash recovery.
170515 11:48:08 [Note] InnoDB: Reading tablespace information from the .ibd files...
170515 11:48:08 [Note] InnoDB: Restoring possible half-written data pages
170515 11:48:08 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 12638756
170515 11:48:09 [Note] InnoDB: 128 rollback segment(s) are active.
170515 11:48:09 [Note] InnoDB: Waiting for purge to start
170515 11:48:09 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.22-72.0 started; log sequence number 12638756
170515 11:48:09 [Note] Plugin 'FEEDBACK' is disabled.
170515 11:48:09 [Note] Server socket created on IP: '::'.

XAMPP MySQL crashing

Hopefully someone ca help me out there. Every time I open XAMPP version 3.2.2, MySQL attempts to start but fails and I am greeted with the following message.....
Attempting to start MySQL app...
12:22:43 [mysql] Status change detected: running 12:22:44 [mysql]
Status change detected: stopped 12:22:44 [mysql] Error: MySQL
shutdown unexpectedly. 12:22:44 [mysql] This may be due to a
blocked port, missing dependencies, 12:22:44 [mysql] improper
privileges, a crash, or a shutdown by another method. 12:22:44
[mysql] Press the Logs button to view error logs and check
12:22:44 [mysql] the Windows Event Viewer for more clues 12:22:44
[mysql] If you need more help, copy and post this 12:22:44 [mysql]
entire log window on the forums
Here is the error log for MySQL, I have searched online and have yet to find a solution
2017-02-28 12:16:46 1a28 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.
2017-02-28 12:16:46 6696 [Note] InnoDB:
innodb_empty_free_list_algorithm has been changed to legacy because of
small buffer pool size. In order to use backoff, increase buffer pool
at least up to 20MB.
2017-02-28 12:16:46 6696 [Note] InnoDB: Using mutexes to ref count
buffer pool pages 2017-02-28 12:16:46 6696 [Note] InnoDB: The
InnoDB memory heap is disabled 2017-02-28 12:16:46 6696 [Note]
InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-02-28 12:16:46 6696 [Note] InnoDB: _mm_lfence() and _mm_sfence()
are used for memory barrier 2017-02-28 12:16:46 6696 [Note]
InnoDB: Compressed tables use zlib 1.2.3 2017-02-28 12:16:46 6696
[Note] InnoDB: Using generic crc32 instructions 2017-02-28
12:16:46 6696 [Note] InnoDB: Initializing buffer pool, size =
16.0M 2017-02-28 12:16:46 6696 [Note] InnoDB: Completed initialization of buffer pool 2017-02-28 12:16:46 6696 [Note]
InnoDB: Restoring page 0 of tablespace 0 2017-02-28 12:16:46 6696
[Warning] InnoDB: Doublewrite does not have page_no=0 of space: 0
2017-02-28 12:16:46 6696 [ERROR] InnoDB: space header page consists of
zero bytes in data file C:\xampp\mysql\data\ibdata1 2017-02-28
12:16:46 6696 [ERROR] InnoDB: Could not open or create the system
tablespace. If you tried to add new data files to the system
tablespace, and it failed here, you should now edit
innodb_data_file_path in my.cnf back to what it was, and remove the
new ibdata files InnoDB created in this failed attempt. InnoDB only
wrote those files full of zeros, but did not yet use them in any way.
But be careful: do not remove old data files which contain your
precious data! 2017-02-28 12:16:46 6696 [ERROR] Plugin 'InnoDB'
init function returned error. 2017-02-28 12:16:46 6696 [ERROR]
Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-02-28 12:16:46 6696 [Note] Plugin 'FEEDBACK' is disabled.
2017-02-28 12:16:46 6696 [ERROR] Unknown/unsupported storage engine:
InnoDB 2017-02-28 12:16:46 6696 [ERROR] Aborting

mySQl in XAMPP wont start (tried changing ports)

So yesterday everything was working fine, but today when I wanted to continue mySQL wouldnt start. Also my laptop shutdown at night if that is relevant. I have tried changing the port to 3307 but it didnt work.
Anyway here is the log
2016-08-19 12:55:09 1b34 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.
160819 12:55:09 [Note] InnoDB: Using mutexes to ref count buffer pool pages
160819 12:55:09 [Note] InnoDB: The InnoDB memory heap is disabled
160819 12:55:09 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
160819 12:55:09 [Note] InnoDB: Memory barrier is not used
160819 12:55:09 [Note] InnoDB: Compressed tables use zlib 1.2.3
160819 12:55:09 [Note] InnoDB: Not using CPU crc32 instructions
160819 12:55:09 [Note] InnoDB: Initializing buffer pool, size = 16.0M
160819 12:55:09 [Note] InnoDB: Completed initialization of buffer pool
160819 12:55:09 [Note] InnoDB: Highest supported file format is Barracuda.
160819 12:55:09 [Note] InnoDB: The log sequence numbers 1665234 and 1665234 in ibdata files do not match the log sequence number 1778208 in the ib_logfiles!
160819 12:55:09 [Note] InnoDB: Database was not shutdown normally!
160819 12:55:09 [Note] InnoDB: Starting crash recovery.
160819 12:55:09 [Note] InnoDB: Reading tablespace information from the .ibd files...
160819 12:55:09 [Note] InnoDB: Restoring possible half-written data pages
160819 12:55:09 [Note] InnoDB: from the doublewrite buffer...
160819 12:55:09 [Note] InnoDB: 128 rollback segment(s) are active.
160819 12:55:09 [Note] InnoDB: Waiting for purge to start
160819 12:55:09 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.22-72.0 started; log sequence number 1778208
160819 12:55:09 [Note] Plugin 'FEEDBACK' is disabled.
160819 12:55:09 [Note] Server socket created on IP: '::'.
And this is what it said in when I tried connecting.
5:10:04 [mysql] Attempting to start MySQL app...
15:10:04 [mysql] Status change detected: running
15:10:04 [mysql] Status change detected: stopped
15:10:04 [mysql] Error: MySQL shutdown unexpectedly.
15:10:04 [mysql] This may be due to a blocked port, missing dependencies,
15:10:04 [mysql] improper privileges, a crash, or a shutdown by another method.
15:10:04 [mysql] Press the Logs button to view error logs and check
15:10:04 [mysql] the Windows Event Viewer for more clues
15:10:04 [mysql] If you need more help, copy and post this
15:10:04 [mysql] entire log window on the forums

Recover DB from ibdata1, ib_logfile0, ib_logfile1 and .frm files

Recently My production server was corrupted due to maintenance shutdown by digital ocean. When we trying to recover our database we couldn't access our droplet. Somehow we managed to recover these (ibdata1, ib_logfile0, ib_logfile1 and some .frm) files. When i copied this files to my new mysql server(in another machine), I could't start the mysql server. I got this output
sudo service mysql restart
mysql stop/waiting
start: Job failed to start
I checked the log file and i got this error,
151019 8:55:27 [Warning] Using unique option prefix myisam-recover instead of $
151019 8:55:27 [Note] Plugin 'FEDERATED' is disabled.
151019 8:55:27 InnoDB: The InnoDB memory heap is disabled
151019 8:55:27 InnoDB: Mutexes and rw_locks use GCC atomic builtins
151019 8:55:27 InnoDB: Compressed tables use zlib 1.2.8
151019 8:55:27 InnoDB: Using Linux native AIO
151019 8:55:27 InnoDB: Initializing buffer pool, size = 128.0M
151019 8:55:27 InnoDB: Completed initialization of buffer pool
InnoDB: Error: log file ./ib_logfile0 is of different size 0 50331648 bytes
InnoDB: than specified in the .cnf file 0 5242880 bytes!
151019 8:55:27 [ERROR] Plugin 'InnoDB' init function returned error.
151019 8:55:27 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
151019 8:55:27 [ERROR] Unknown/unsupported storage engine: InnoDB
151019 8:55:27 [ERROR] Aborting
151019 8:55:27 [Note] /usr/sbin/mysqld: Shutdown complete
151019 8:55:28 [Warning] Using unique option prefix myisam-recover instead of $
151019 8:55:28 [Note] Plugin 'FEDERATED' is disabled.
151019 8:55:28 InnoDB: The InnoDB memory heap is disabled
151019 8:55:28 InnoDB: Mutexes and rw_locks use GCC atomic builtins
151019 8:55:28 InnoDB: Compressed tables use zlib 1.2.8
151019 8:55:28 InnoDB: Using Linux native AIO
151019 8:55:28 InnoDB: Initializing buffer pool, size = 128.0M
151019 8:55:28 InnoDB: Completed initialization of buffer pool
InnoDB: Error: log file ./ib_logfile0 is of different size 0 50331648 bytes
InnoDB: than specified in the .cnf file 0 5242880 bytes!
151019 8:55:28 [ERROR] Plugin 'InnoDB' init function returned error.
151019 8:55:28 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
151019 8:55:28 [ERROR] Unknown/unsupported storage engine: InnoDB
151019 8:55:28 [ERROR] Aborting
151019 8:55:28 [Note] /usr/sbin/mysqld: Shutdown complete
151019 8:55:29 [Warning] Using unique option prefix myisam-recover instead of $
151019 8:55:29 [Note] Plugin 'FEDERATED' is disabled.
151019 8:55:29 InnoDB: The InnoDB memory heap is disabled
151019 8:55:29 InnoDB: Mutexes and rw_locks use GCC atomic builtins
151019 8:55:29 InnoDB: Compressed tables use zlib 1.2.8
151019 8:55:29 InnoDB: Using Linux native AIO
151019 8:55:29 InnoDB: Initializing buffer pool, size = 128.0M
151019 8:55:29 InnoDB: Completed initialization of buffer pool
InnoDB: Error: log file ./ib_logfile0 is of different size 0 50331648 bytes
InnoDB: than specified in the .cnf file 0 5242880 bytes!
151019 8:55:29 [ERROR] Plugin 'InnoDB' init function returned error.
151019 8:55:29 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
151019 8:55:29 [ERROR] Unknown/unsupported storage engine: InnoDB
151019 8:55:29 [ERROR] Aborting
151019 8:55:29 [Note] /usr/sbin/mysqld: Shutdown complete
I tried adding innodb_log_file_size= 50331648 as suggested by #akuzminsky
Then I got this error log.
151022 6:54:13 [Warning] Using unique option prefix myisam-recover instead of $
151022 6:54:13 [Note] Plugin 'FEDERATED' is disabled.
151022 6:54:13 InnoDB: The InnoDB memory heap is disabled
151022 6:54:13 InnoDB: Mutexes and rw_locks use GCC atomic builtins
151022 6:54:13 InnoDB: Compressed tables use zlib 1.2.8
151022 6:54:13 InnoDB: Using Linux native AIO
151022 6:54:13 InnoDB: Initializing buffer pool, size = 128.0M
151022 6:54:13 InnoDB: Completed initialization of buffer pool
151022 6:54:13 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 15379293
151022 6:54:13 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Error: space header page consists of zero bytes in file ./toucan/ormcli$
InnoDB: Error: space header page consists of zero bytes in file ./toucan/catego$
InnoDB: Error: space header page consists of zero bytes in file ./toucan/survey$
InnoDB: Error: space header page consists of zero bytes in file ./toucan/compla$
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 15382291
InnoDB: Page directory corruption: infimum not pointed to
151022 6:54:13 InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex 10cfd0d80000000000000000000000000000000000e9e915000800000000001$
InnoDB: End of page dump
151022 6:54:13 InnoDB: Page checksum 282054872, prior-to-4.0.14-form checksum$
InnoDB: stored checksum 282054872, prior-to-4.0.14-form stored checksum 3468306$
InnoDB: Page lsn 0 15329557, low 4 bytes of lsn at page end 15329557
InnoDB: Page number (if stored to page already) 0,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be a file space header page
10:54:13 UTC - mysqld got signal 11 ;
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=131072
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 = 346701 K $
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...
stack_bottom = 0 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x20)[0x7fa4d90e2f10]
/usr/sbin/mysqld(handle_fatal_signal+0x3d5)[0x7fa4d8fcd175]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x10340)[0x7fa4d7d5d340]
/usr/sbin/mysqld(+0x5f058a)[0x7fa4d91e258a]
/usr/sbin/mysqld(+0x56c44e)[0x7fa4d915e44e]
/usr/sbin/mysqld(+0x576137)[0x7fa4d9168137]
/usr/sbin/mysqld(+0x5a5632)[0x7fa4d9197632]
/usr/sbin/mysqld(+0x5a6699)[0x7fa4d9198699]
/usr/sbin/mysqld(+0x591ad3)[0x7fa4d9183ad3]
/usr/sbin/mysqld(+0x542a1a)[0x7fa4d9134a1a]
/usr/sbin/mysqld(+0x511d48)[0x7fa4d9103d48]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x41)[0x7fa4d8fcf$
/usr/sbin/mysqld(+0x302221)[0x7fa4d8ef4221]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0x92a)[0x7fa4d8ef821a]
/usr/sbin/mysqld(+0x28ac5b)[0x7fa4d8e7cc5b]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x45b)[0x7fa4d8e815db]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7fa4d739fec5]
/usr/sbin/mysqld(+0x286b18)[0x7fa4d8e78b18]
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.
Please help me to resolve this.
Thanks in advance.
Note lines in the error log:
InnoDB: Error: log file ./ib_logfile0 is of different size 0 50331648 bytes
InnoDB: than specified in the .cnf file 0 5242880 bytes!
The actual size of the redo log file differs from the size in MySQL config.
Add this line to my.cnf
innodb_log_file_size= 50331648
If the tablespace is corrupted you'll still have to heal it. But at least MySQL won't stop at this step.