10:01:04 PM [mysql] Error: MySQL shutdown unexpectedly.
10:01:04 PM [mysql] This may be due to a blocked port, missing dependencies,
10:01:04 PM [mysql] improper privileges, a crash, or a shutdown by another method.
10:01:04 PM [mysql] Press the Logs button to view error logs and check
10:01:04 PM [mysql] the Windows Event Viewer for more clues
10:01:04 PM [mysql] If you need more help, copy and post this
10:01:04 PM [mysql] entire log window on the forums
I get this error when trying to start MySQL in xampp. Here is the mysql_error.log file:
31127 21:56:14 [Note] Plugin 'FEDERATED' is disabled.
131127 21:56:14 InnoDB: The InnoDB memory heap is disabled
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
131127 21:56:15 InnoDB: Waiting for the background threads to start
131127 21:56:16 InnoDB: 5.5.32 started; log sequence number 22856689
131127 21:56:16 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
131127 21:56:16 [Note] - '0.0.0.0' resolves to '0.0.0.0';
131127 21:56:16 [Note] Server socket created on IP: '0.0.0.0'.
Thanks!
It may be the port that MySQL is trying to listen to is already used. You can try going to the command prompt and run netstat to see what programs are using which ports.
C:\> netstat -a -b
Related
When I start xampp it gives me an error in mysql. I'm using windows 10.
Here is the contents of error log:
2015-11-10 15:26:56 10fc 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.
2015-11-10 15:26:56 4348 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2015-11-10 15:26:56 4348 [Note] InnoDB: The InnoDB memory heap is disabled
2015-11-10 15:26:56 4348 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-11-10 15:26:56 4348 [Note] InnoDB: Memory barrier is not used
2015-11-10 15:26:56 4348 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-11-10 15:26:56 4348 [Note] InnoDB: Not using CPU crc32 instructions
2015-11-10 15:26:56 4348 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-11-10 15:26:56 4348 [Note] InnoDB: Completed initialization of buffer pool
2015-11-10 15:26:56 4348 [Note] InnoDB: Highest supported file format is Barracuda.
2015-11-10 15:26:57 4348 [Note] InnoDB: 128 rollback segment(s) are active.
2015-11-10 15:26:57 4348 [Note] InnoDB: Waiting for purge to start
2015-11-10 15:26:57 4348 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.26-74.0 started; log sequence number 1835027
2015-11-10 15:26:57 6140 [Note] InnoDB: Dumping buffer pool(s) not yet started
2015-11-10 15:26:57 4348 [Note] Plugin 'FEEDBACK' is disabled.
2015-11-10 15:26:57 4348 [Note] Server socket created on IP: '::'.
2015-11-10 15:26:57 4348 [Note] Event Scheduler: Loaded 0 events
2015-11-10 15:26:57 4348 [Note] C:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '10.1.8-MariaDB' socket: '' port: 3306 mariadb.org binary distribution
2015-11-10 15:27:11 5152 [Note] C:\xampp\mysql\bin\mysqld.exe: Normal shutdown
When I opened XAMPP and click start MySQL button it gives me an error.
9:12:53 PM [mysql] Error: MySQL shutdown unexpectedly.
9:12:53 PM [mysql] This may be due to a blocked port, missing dependencies,
9:12:53 PM [mysql] improper privileges, a crash, or a shutdown by another method.
9:12:53 PM [mysql] Press the Logs button to view error logs and check
9:12:53 PM [mysql] the Windows Event Viewer for more clues
9:12:53 PM [mysql] If you need more help, copy and post this
9:12:53 PM [mysql] entire log window on the forums
UPDATE
Here is the screenshot:
First: Close Xampp.
Second: Go to \xampp\mysql\backup.
Third: Copy all files in directory except ibdata1.
Fourth: Go to \xampp\mysql\data.
Fifth: Paste the files that you copied from \xampp\mysql\ backup
(Replace the files when asked).
Sixth: Start Xampp.
Follow these steps properly and carefully.
This error is caused because there is already MySQL installed (of different version) which is using port 3306.
On the xampp control panel you will find 'MySQL' and several options like Start, Config, etc beside that.
Select Config and open the file named 'my.ini'. It should open in a notepad. Press Ctrl + F and Find '3306' and change it to 3308 and Save the file.
NOTE: YOU WILL FIND 5 INSTANCES OF 3306. CHANGE ALL OF THEM TO 3308.
Now Open the Config which is located on the top-right of the Xampp control panel. A window should appear. Find 'Service and Port setting'. Click the button and once again a window should appear.
5.On the MySQL tab type '3308'. And Save the changes.
6.Search 'services.msc' on Windows search. A Window should popup. Scroll down until you find 'MySQL'.
Right click on MySQL and select STOP.
Now Run Command Prompt as administrator and type the following command.
sc delete mysql
This will successfully delete previously installed mysql.
Quit the xampp control panel completely and start a new fresh one.
Now your MySQL should be up and running.
Probably your 3306 or whatever you use is being used by other applications. May be you don't know that XAMPP usually has problems with apps like Skype. If you are running Skype try to close it and open XAMPP. You can also change default ports for HTTP and MySQL.
To Edit Apache ports open apache.conf and restart the server.
To Edit MySql ports open my.cnf and restart the service.
You may also take a look to this post. May be you need to delete your DB files due corruption but it may be not the reason if you just installed fresh Xampp instance.
XAMPP - MySQL shutdown unexpectedly
UPDATE
Here you have a good screenshot of how to change ports on Skype if you prefer.
https://stackoverflow.com/a/16351807/3518053
The problem is that you have two instances of mysql installed in your computer. Check if the process mysqld.exe is already running via task manager and terminate it if present. Then open services.msc via run and remove all instances of mysql if any(terminate it before removing), reboot your machine and run XAMPP again. This will solve your problem.
I came across a similar problem, you can try this here
Remember to backup your data first!
Using cmd as administrator uninstall
xampp
all mysql database
mysql service
then remove the service using sc delete and remove all directory of XAMPP. Then reinstall it again.
7:23:46 PM [main] Initializing Control Panel
7:23:46 PM [main] Windows Version: Windows 8 64-bit
7:23:46 PM [main] XAMPP Version: 5.6.11
7:23:46 PM [main] Control Panel Version: 3.2.1 [ Compiled: May 7th 2013 ]
7:23:46 PM [main] You are not running with administrator rights! This will work for
7:23:46 PM [main] most application stuff but whenever you do something with services
7:23:46 PM [main] there will be a security dialogue or things will break! So think
7:23:46 PM [main] about running this application with administrator rights!
7:23:46 PM [main] XAMPP Installation Directory: "e:\xampp\"
7:23:46 PM [main] Checking for prerequisites
7:23:46 PM [main] All prerequisites found
7:23:46 PM [main] The Apache module is disabled
7:23:46 PM [main] The FileZilla module is disabled
7:23:46 PM [main] The Mercury module is disabled
7:23:46 PM [main] The Tomcat module is disabled
7:23:46 PM [main] Enabling autostart for module "MySQL"
7:23:46 PM [main] Starting Check-Timer
7:23:46 PM [main] Control Panel Ready
7:23:47 PM [mysql] Autostart active: starting...
7:23:47 PM [mysql] Attempting to start MySQL app...
7:23:47 PM [mysql] Status change detected: running
7:23:48 PM [mysql] Status change detected: stopped
7:23:48 PM [mysql] Error: MySQL shutdown unexpectedly.
7:23:48 PM [mysql] This may be due to a blocked port, missing dependencies,
7:23:48 PM [mysql] improper privileges, a crash, or a shutdown by another method.
7:23:48 PM [mysql] Press the Logs button to view error logs and check
7:23:48 PM [mysql] the Windows Event Viewer for more clues
7:23:48 PM [mysql] If you need more help, copy and post this
7:23:48 PM [mysql] entire log window on the forums
I had everything working yesterday, but for some reason I can't get it to work now. I tried deleting and reinstalling the xampp file. It says I'm not running admin rights, but I'm the only user and admin. I've tried a few suggestions already posted on here, but I cannot get it to work. Any ideas?
2015-08-18 21:07:18 4436 [Note] Plugin 'FEDERATED' is disabled.
2015-08-18 21:07:18 2988 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.
2015-08-18 21:07:18 4436 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-08-18 21:07:18 4436 [Note] InnoDB: The InnoDB memory heap is disabled
2015-08-18 21:07:18 4436 [Note] InnoDB: Mutexes and rw_locks use Windows
interlocked functions
2015-08-18 21:07:18 4436 [Note] InnoDB: Memory barrier is not used
2015-08-18 21:07:18 4436 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-08-18 21:07:18 4436 [Note] InnoDB: Not using CPU crc32 instructions
2015-08-18 21:07:18 4436 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-08-18 21:07:18 4436 [Note] InnoDB: Completed initialization of buffer pool
2015-08-18 21:07:19 4436 [Note] InnoDB: Highest supported file format is
Barracuda.
2015-08-18 21:07:23 4436 [Note] InnoDB: 128 rollback segment(s) are active.
2015-08-18 21:07:23 4436 [Note] InnoDB: Waiting for purge to start
2015-08-18 21:07:23 4436 [Note] InnoDB: 5.6.25 started; log sequence number 1665234
2015-08-18 21:07:23 4436 [Note] Server hostname (bind-address): '*'; port: 3306
2015-08-18 21:07:23 4436 [Note] IPv6 is available.
2015-08-18 21:07:23 4436 [Note] - '::' resolves to '::';
2015-08-18 21:07:23 4436 [Note] Server socket created on IP: '::'.
2015-08-18 21:07:25 4436 [Note] Event Scheduler: Loaded 0 events
2015-08-18 21:07:25 4436 [Note] mysql\bin\mysqld.exe: ready for connections.
Version: '5.6.25' socket: '' port: 3306 MySQL Community Server (GPL)
I restarted my computer and noticed that there was an update available. Once I did the update and restarted, completely deleted xampp and reinstalled, MySQL is functioning correctly again. Perhaps because there was an update available, it wasn't letting it run?
TL;DR: Check for updates, restart computer, reinstall xampp. MySQL should work.
I have WAMP server version 2.2. Previously, MySQL Server running normally.
I don't know why when I tried to start, it cannot start anymore.
Here are the content of MySQL.log:
140502 21:04:46 [Note] Plugin 'FEDERATED' is disabled.
140502 21:04:47 InnoDB: The InnoDB memory heap is disabled
140502 21:04:47 InnoDB: Mutexes and rw_locks use Windows interlocked functions
140502 21:04:47 InnoDB: Compressed tables use zlib 1.2.3
140502 21:04:47 InnoDB: Initializing buffer pool, size = 128.0M
140502 21:04:47 InnoDB: Completed initialization of buffer pool
140502 21:04:47 InnoDB: highest supported file format is Barracuda.
140502 21:04:47 InnoDB: Waiting for the background threads to start
140502 21:04:48 InnoDB: 1.1.8 started; log sequence number 1595675
140502 21:04:48 [Note] Server hostname (bind-address): '(null)'; port: 3306
140502 21:04:48 [Note] - '(null)' resolves to '::';
140502 21:04:48 [Note] - '(null)' resolves to '0.0.0.0';
140502 21:04:48 [Note] Server socket created on IP: '0.0.0.0'.
140502 21:04:48 [ERROR] Can't start server: Bind on TCP/IP port: No such file or directory
140502 21:04:48 [ERROR] Do you already have another mysqld server running on port: 3306 ?
140502 21:04:48 [ERROR] Aborting
140502 21:04:48 InnoDB: Starting shutdown...
140502 21:04:49 InnoDB: Shutdown completed; log sequence number 1595675
140502 21:04:49 [Note] wampmysqld: Shutdown complete
I had already tried to reinstall WAMP server but appear the same error.
Can someone help me, please...
It's possible that the port is trying to be opened by another storage engine than InnoDB. Refer to this article for some commands that can help you identify what's happening.
For instance, netstat -an | findstr "3306"
danielschneller.com/2007/10/cant-start-server-bind-on-tcpip-port-no.html
Something is already working on that port. In administrator CMD console write
netstat -abn
and find port 3306, then you will know what is blocking the port (what is already running on it and blocks your mysql).
If that doesnt help you then check my.ini settings
In that file search for
socket = /something
and change that to
socket = c:/something
I had the same problem with Windows 7 32-bit.
Cause
Some filenames are reserved by Windows, such as ${machinename}.pid, ${machinename}.err, etc.
MySQL uses some of these filenames by default.
Solution
After the installation is complete, during the configuration phase, there's an Advanced option using which you can change these filenames. You can change the log file names but not the pid file name.
You need to step through the configuration wizard to the "starting service" step, and then it will throw an error/warning message. Leave the wizard paused (do not stop/cancel the wizard).
By now, your my.ini file has been created. You can add the following variable
pid_file=/path/to/pid/file.pid
Then go to Windows Services and start the service.
N.B. DO NOT STOP/CANCEL THE WIZARD.
Once the service is started, the wizard will continue, and will configure MySQL properly.
setting file my.ini :
innodb_flush_method=normal
Everytime when I start my Mysql database I see this in the error_log:
131015 12:07:06 [Note] Plugin 'FEDERATED' is disabled. 131015 12:07:06
InnoDB: The InnoDB memory heap is disabled 131015 12:07:06 InnoDB:
Mutexes and rw_locks use Windows interlocked functions 131015 12:07:06
InnoDB: Compressed tables use zlib 1.2.3 131015 12:07:06 InnoDB:
Initializing buffer pool, size = 16.0M 131015 12:07:06 InnoDB:
Completed initialization of buffer pool 131015 12:07:06 InnoDB:
highest supported file format is Barracuda. InnoDB: The log sequence
number in ibdata files does not match InnoDB: the log sequence number
in the ib_logfiles! 131015 12:07:06 InnoDB: Database was not shut
down normally! InnoDB: Starting crash recovery. InnoDB: Reading
tablespace information from the .ibd files... InnoDB: Restoring
possible half-written data pages from the doublewrite InnoDB:
buffer... 131015 12:07:07 InnoDB: Waiting for the background threads
to start 131015 12:07:08 InnoDB: 5.5.32 started; log sequence number
1595695 131015 12:07:08 [Note] Server hostname (bind-address):
'0.0.0.0'; port: 3306 131015 12:07:08 [Note] - '0.0.0.0' resolves to
'0.0.0.0'; 131015 12:07:08 [Note] Server socket created on IP:
'0.0.0.0'.
I've tried mysqlcheck -u root -p --repair -A in order to repair the database. This reports that all tables are a-ok.
I've also tried setting innodb_force_recovery to 4
I've tried SET GLOBAL innodb_fast_shutdown = 1; and shutdown the DB.
None of these make the errors go away.
How do I repair the InnoDB tables in my database?
I resolve my problem by removing some files in "Xampp\mysql\data":
ib_logfile0
ib_logfile1
ibdata1
** Be Sure to Backup your DBs by :
[mysqld]
innodb_force_recovery = 2
(This command will help you to start Mysql in Read-only mode.)
LSN (log sequence number) may not match if MySQL crashed.
But if the crash recovery process finished you should be fine. If any transaction modifies data in a page, new LSN will be written to the page header.
I would investigate why MySQL crashes every time you restart it. To my knowledge /etc/init.d/mysql stop may take long time, so if you restart the server OS may just kill mysqld. In that case you should manually stop MySQL before reboot the whole server.
I had the same issue.
In my case, I was running MySQL on windows via XAMPP and using the XAMPP controls to start/stop the server.
It appears the XAMPP shutdown control was killing the MySQL server, rather than requesting a shutdown.
Solution
(optional) In my.ini set innodb_fast_shutdown=0 to configure mysqld to perform a full showdown
Create a .bat file, with contents mysqladmin --user=[user] --password=[password] shutdown replacing [user] and [password] with your root user details
When you wish to shutdown the MySQL server, just run the .bat file. The shutdown is detected by XAMPP control panel so you can restart using the XAMPP control.
If you now take a look at your logs, you'll see the errors have gone away
Or better yet, just install mysql as a windows service.
References:
innodb_fast_shutdown http://dev.mysql.com/doc/refman/5.7/en/innodb-parameters.html#sysvar_innodb_fast_shutdown
mysqladmin shutdown - http://dev.mysql.com/doc/refman/5.7/en/server-shutdown.html
the mysql in my VPS hosting has connection problem. I think it was due to my server drive has fail and my hosting has replace and rebuild a new drive. So I thought that my MySQL installation may have been corrupted, so I upgrade the mysql but the problem persist. How to fix this ? Thank you
root#user [~]# mysql -u root -p
Enter password:
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 1
Server version: 5.1.68-cll MySQL Community Server (GPL)
Copyright (c) 2000, 2013, Oracle and/or its affiliates. All rights reserved.
Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
mysql> use testdb
No connection. Trying to reconnect...
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
ERROR:
Can't connect to the server
mysql>
Here is the error log generated in /var/lib/mysql/domain.err
Version: '5.1.68-cll' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL)
130303 17:28:49 InnoDB: Assertion failure in thread 2965224304 in file fsp/fsp0fsp.c line 3341
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.1/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
09:28:49 UTC - mysqld got signal 6 ;
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=8384512
read_buffer_size=131072
max_used_connections=0
max_threads=500
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 = 1099543 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...
stack_bottom = 0 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x25)[0x848d5e5]
/usr/sbin/mysqld(handle_fatal_signal+0x42a)[0x82dd84a]
[0xb775c500]
/lib/libc.so.6(abort+0x17a)[0xb75513da]
/usr/sbin/mysqld(fseg_free_step_not_header+0x1a1)[0x83afab1]
/usr/sbin/mysqld[0x8409078]
/usr/sbin/mysqld[0x84094d0]
/usr/sbin/mysqld(trx_purge_fetch_next_rec+0x7a)[0x840960a]
/usr/sbin/mysqld(row_purge_step+0x37)[0x83eefb7]
/usr/sbin/mysqld(que_run_threads+0x4f7)[0x83de467]
/usr/sbin/mysqld(trx_purge+0x32f)[0x840787f]
/usr/sbin/mysqld(srv_master_thread+0x417)[0x8400267]
/lib/libpthread.so.0(+0x6a49)[0xb773ca49]
/lib/libc.so.6(clone+0x5e)[0xb760763e]
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.
130303 17:28:49 mysqld_safe Number of processes running now: 0
130303 17:28:49 mysqld_safe mysqld restarted
130303 17:28:49 [Warning] '--log_slow_queries' is deprecated and will be removed in a future release. Please use ''--slow_query_log'/'--slow_query_log_file'' instead.
130303 17:28:49 [Warning] '--safe-show-database' is deprecated and will be removed in a future release. Please use 'GRANT SHOW DATABASES' instead.
130303 17:28:49 [Warning] '--log' is deprecated and will be removed in a future release. Please use ''--general_log'/'--general_log_file'' instead.
130303 17:28:49 [Note] Plugin 'FEDERATED' is disabled.
130303 17:28:49 InnoDB: Initializing buffer pool, size = 8.0M
130303 17:28:49 InnoDB: Completed initialization of buffer pool
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
130303 17:28:49 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
130303 17:28:49 InnoDB: Started; log sequence number 0 1605434197
130303 17:28:49 [Warning] 'user' entry 'root#s1.replace.com' ignored in --skip-name-resolve mode.
130303 17:28:49 [Warning] 'user' entry 'root#xx1.no-ip.org' ignored in --skip-name-resolve mode.
130303 17:28:49 [Note] Event Scheduler: Loaded 0 events
130303 17:28:49 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.68-cll' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL)
130303 17:28:50 InnoDB: Assertion failure in thread 2965224304 in file fsp/fsp0fsp.c line 3341
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.1/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
Computer info
root#user [~]# uname -a
Linux domain.com 2.6.32-042stab072.10 #1 SMP Wed Jan 16 18:54:05 MSK 2013 i686 i686 i386 GNU/Linux
root#user [~]# free -m
total used free shared buffers cached
Mem: 2560 1323 1236 0 0 826
-/+ buffers/cache: 497 2062
Swap: 0 0 0
root#user [~]# cat /etc/my.cnf
[mysqld]
max_connections=500
log-slow-queries
log-error
safe-show-database
bind-address=xx.x.xx.xxx
skip-name-resolve
connect_timeout= 10
log=1
log_warnings = 2
max_allowed_packet = 64M
Your MySQL server process either isn't running or the InnoDB assertion right after MySQL started listening for connections has hung the process. Note these lines:
130303 17:28:49 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.68-cll' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL)
130303 17:28:50 InnoDB: Assertion failure in thread 2965224304 in file fsp/fsp0fsp.c line 3341
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.1/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
Go to the InnoDB Recovery page listed in that output and follow the instructions for forcing an InnoDB recovery. It looks like you have a corrupt InnoDB database.