Hallo nach einem absturz meines servers startet mysql nicht mehr in den logs schreibt er mir folgendes:
werde leider nicht schlau daraus. was muss ich jetzt tun?
2015-11-25 11:06:29 5268 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2015-11-25 11:06:29 5268 [Note] InnoDB: The InnoDB memory heap is disabled
2015-11-25 11:06:29 5268 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-11-25 11:06:29 5268 [Note] InnoDB: Memory barrier is not used
2015-11-25 11:06:29 5268 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-11-25 11:06:29 5268 [Note] InnoDB: Not using CPU crc32 instructions
2015-11-25 11:06:29 5268 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-11-25 11:06:29 5268 [Note] InnoDB: Completed initialization of buffer pool
2015-11-25 11:06:29 5268 [Note] InnoDB: Highest supported file format is Barracuda.
2015-11-25 11:06:29 5268 [Note] InnoDB: The log sequence numbers 3494300 and 3494300 in ibdata files do not match the log sequence number 1401525696 in the ib_logfiles!
2015-11-25 11:06:29 5268 [Note] InnoDB: Database was not shutdown normally!
2015-11-25 11:06:29 5268 [Note] InnoDB: Starting crash recovery.
2015-11-25 11:06:29 5268 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-11-25 11:06:29 5268 [Note] InnoDB: Restoring possible half-written data pages
2015-11-25 11:06:29 5268 [Note] InnoDB: from the doublewrite buffer...
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 0 row operations to undo
InnoDB: Trx id counter is 20460032
2015-11-25 11:06:30 5268 [Note] InnoDB: 128 rollback segment(s) are active.
InnoDB: Starting in background the rollback of uncommitted transactions
2015-11-25 11:06:30 f4c InnoDB: Rolling back trx with id 20455329, 0 rows to undo
2015-11-25 11:06:30 5268 [Note] InnoDB: Waiting for purge to start
2015-11-25 11:06:30 f4c InnoDB: Assertion failure in thread 3916 in file fut0lst.ic line 83
InnoDB: Failing assertion: addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to MySQL Bugs.
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: MySQL :: MySQL 5.6 Reference Manual :: 14.18.2 Forcing InnoDB Recovery
InnoDB: about forcing recovery.
151125 11:06:30 [ERROR] 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.
To report this bug, see Reporting Bugs
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.
Server version: 10.1.8-MariaDB
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=1001
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 787099 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0x0
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...
2015-11-25 11:06:30 5268 [Note] InnoDB: Percona XtraDB (Percona – The Database Performance Experts) 5.6.26-74.0 started; log sequence number 1401525696
mysqld.exe!my_parameter_handler()
mysqld.exe!my_mb_ctype_mb()
mysqld.exe!??0Global_read_lock@@QAE@XZ()
mysqld.exe!?store_record_for_lookup@Stat_table@@IAEXXZ()
mysqld.exe!??0Global_read_lock@@QAE@XZ()
mysqld.exe!?store_record_for_lookup@Stat_table@@IAEXXZ()
mysqld.exe!?store_record_for_lookup@Stat_table@@IAEXXZ()
mysqld.exe!?store_record_for_lookup@Stat_table@@IAEXXZ()
mysqld.exe!??0Global_read_lock@@QAE@XZ()
mysqld.exe!??0Global_read_lock@@QAE@XZ()
mysqld.exe!??0Global_read_lock@@QAE@XZ()
mysqld.exe!??0Global_read_lock@@QAE@XZ()
ntdll.dll!RtlInitializeExceptionChain()
ntdll.dll!RtlInitializeExceptionChain()
The manual page at MySQL :: MySQL 5.7 Reference Manual :: B.5.4.2 What to Do If MySQL Keeps Crashing contains
information that should help you find out what is causing the crash.
2015-11-25 11:06:30 2556 [Note] InnoDB: Dumping buffer pool(s) not yet started
2015-11-25 11:06:30 5268 [Note] Plugin 'FEEDBACK' is disabled.
2015-11-25 11:06:30 5268 [Note] Recovering after a crash using tc.log
2015-11-25 11:06:30 5268 [Note] Starting crash recovery...
2015-11-25 11:06:30 5268 [Note] Crash recovery finished.
2015-11-25 11:06:30 5268 [Note] Server socket created on IP: '::'.
2015-11-25 11:06:31 5268 [Note] Event Scheduler: Loaded 0 events
2015-11-25 11:06:31 5268 [Note] d:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '10.1.8-MariaDB' socket: '' port: 3306 mariadb.org binary distribution
werde leider nicht schlau daraus. was muss ich jetzt tun?
2015-11-25 11:06:29 5268 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2015-11-25 11:06:29 5268 [Note] InnoDB: The InnoDB memory heap is disabled
2015-11-25 11:06:29 5268 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-11-25 11:06:29 5268 [Note] InnoDB: Memory barrier is not used
2015-11-25 11:06:29 5268 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-11-25 11:06:29 5268 [Note] InnoDB: Not using CPU crc32 instructions
2015-11-25 11:06:29 5268 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-11-25 11:06:29 5268 [Note] InnoDB: Completed initialization of buffer pool
2015-11-25 11:06:29 5268 [Note] InnoDB: Highest supported file format is Barracuda.
2015-11-25 11:06:29 5268 [Note] InnoDB: The log sequence numbers 3494300 and 3494300 in ibdata files do not match the log sequence number 1401525696 in the ib_logfiles!
2015-11-25 11:06:29 5268 [Note] InnoDB: Database was not shutdown normally!
2015-11-25 11:06:29 5268 [Note] InnoDB: Starting crash recovery.
2015-11-25 11:06:29 5268 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-11-25 11:06:29 5268 [Note] InnoDB: Restoring possible half-written data pages
2015-11-25 11:06:29 5268 [Note] InnoDB: from the doublewrite buffer...
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 0 row operations to undo
InnoDB: Trx id counter is 20460032
2015-11-25 11:06:30 5268 [Note] InnoDB: 128 rollback segment(s) are active.
InnoDB: Starting in background the rollback of uncommitted transactions
2015-11-25 11:06:30 f4c InnoDB: Rolling back trx with id 20455329, 0 rows to undo
2015-11-25 11:06:30 5268 [Note] InnoDB: Waiting for purge to start
2015-11-25 11:06:30 f4c InnoDB: Assertion failure in thread 3916 in file fut0lst.ic line 83
InnoDB: Failing assertion: addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to MySQL Bugs.
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: MySQL :: MySQL 5.6 Reference Manual :: 14.18.2 Forcing InnoDB Recovery
InnoDB: about forcing recovery.
151125 11:06:30 [ERROR] 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.
To report this bug, see Reporting Bugs
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.
Server version: 10.1.8-MariaDB
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=1001
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 787099 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0x0
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...
2015-11-25 11:06:30 5268 [Note] InnoDB: Percona XtraDB (Percona – The Database Performance Experts) 5.6.26-74.0 started; log sequence number 1401525696
mysqld.exe!my_parameter_handler()
mysqld.exe!my_mb_ctype_mb()
mysqld.exe!??0Global_read_lock@@QAE@XZ()
mysqld.exe!?store_record_for_lookup@Stat_table@@IAEXXZ()
mysqld.exe!??0Global_read_lock@@QAE@XZ()
mysqld.exe!?store_record_for_lookup@Stat_table@@IAEXXZ()
mysqld.exe!?store_record_for_lookup@Stat_table@@IAEXXZ()
mysqld.exe!?store_record_for_lookup@Stat_table@@IAEXXZ()
mysqld.exe!??0Global_read_lock@@QAE@XZ()
mysqld.exe!??0Global_read_lock@@QAE@XZ()
mysqld.exe!??0Global_read_lock@@QAE@XZ()
mysqld.exe!??0Global_read_lock@@QAE@XZ()
ntdll.dll!RtlInitializeExceptionChain()
ntdll.dll!RtlInitializeExceptionChain()
The manual page at MySQL :: MySQL 5.7 Reference Manual :: B.5.4.2 What to Do If MySQL Keeps Crashing contains
information that should help you find out what is causing the crash.
2015-11-25 11:06:30 2556 [Note] InnoDB: Dumping buffer pool(s) not yet started
2015-11-25 11:06:30 5268 [Note] Plugin 'FEEDBACK' is disabled.
2015-11-25 11:06:30 5268 [Note] Recovering after a crash using tc.log
2015-11-25 11:06:30 5268 [Note] Starting crash recovery...
2015-11-25 11:06:30 5268 [Note] Crash recovery finished.
2015-11-25 11:06:30 5268 [Note] Server socket created on IP: '::'.
2015-11-25 11:06:31 5268 [Note] Event Scheduler: Loaded 0 events
2015-11-25 11:06:31 5268 [Note] d:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '10.1.8-MariaDB' socket: '' port: 3306 mariadb.org binary distribution
