bis dato hatte ich keine probleme mit Xampp & mysql.
Seit heute werden keine query mehr ausgeführt. beim Ausführen stürzt mysql ab. #2006 mysql server has gone away. + mysql.exe funktioniert nicht mehr.
auch über phpmyadmin ist die tabelle nicht ansprechbar bzw. stürzt ab wenn ich draufklicke.
Dies passiert nur bei einer bestimmten großen Tabelle. Sonst funktioniert alles einwandfrei.
habe Version 5.6.20 & Windows 7 prof 64bit
bei Version 5.6.3 (andere PC) funktioniert alles.
habe versucht in my.ini key_buffer usw. zu erhöhen... hat jedoch nichts bewirkt.
- Code: Select all
2016-08-11 17:41:12 4420 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2016-08-11 17:41:12 4420 [Note] InnoDB: The InnoDB memory heap is disabled
2016-08-11 17:41:12 4420 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2016-08-11 17:41:12 4420 [Note] InnoDB: Memory barrier is not used
2016-08-11 17:41:12 4420 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-08-11 17:41:12 4420 [Note] InnoDB: Using generic crc32 instructions
2016-08-11 17:41:12 4420 [Note] InnoDB: Initializing buffer pool, size = 512.0M
2016-08-11 17:41:12 4420 [Note] InnoDB: Completed initialization of buffer pool
2016-08-11 17:41:12 4420 [Note] InnoDB: Highest supported file format is Barracuda.
2016-08-11 17:41:12 4420 [Note] InnoDB: The log sequence numbers 101062102028 and 101062102028 in ibdata files do not match the log sequence number 101062109836 in the ib_logfiles!
2016-08-11 17:41:12 4420 [Note] InnoDB: Database was not shutdown normally!
2016-08-11 17:41:12 4420 [Note] InnoDB: Starting crash recovery.
2016-08-11 17:41:12 4420 [Note] InnoDB: Reading tablespace information from the .ibd files...
2016-08-11 17:41:12 4420 [Note] InnoDB: Restoring possible half-written data pages
2016-08-11 17:41:12 4420 [Note] InnoDB: from the doublewrite buffer...
2016-08-11 17:41:12 4420 [Note] InnoDB: 128 rollback segment(s) are active.
2016-08-11 17:41:12 4420 [Note] InnoDB: Waiting for purge to start
2016-08-11 17:41:12 4420 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.28-76.1 started; log sequence number 101062109836
2016-08-11 17:41:12 5772 [Note] InnoDB: Dumping buffer pool(s) not yet started
2016-08-11 17:41:12 4420 [Note] Plugin 'FEEDBACK' is disabled.
2016-08-11 17:41:12 4420 [Note] Server socket created on IP: '::'.
2016-08-11 17:41:12 4420 [ERROR] mysqld.exe: Table '.\mysql\db' is marked as crashed and should be repaired
2016-08-11 17:41:12 4420 [Warning] Checking table: '.\mysql\db'
2016-08-11 17:41:12 4420 [ERROR] mysql.db: 1 client is using or hasn't closed the table properly
2016-08-11 17:41:12 4420 [ERROR] mysqld.exe: Table '.\mysql\tables_priv' is marked as crashed and should be repaired
2016-08-11 17:41:12 4420 [Warning] Checking table: '.\mysql\tables_priv'
2016-08-11 17:41:12 4420 [ERROR] mysql.tables_priv: 1 client is using or hasn't closed the table properly
2016-08-11 17:41:12 4420 [ERROR] mysqld.exe: Table '.\mysql\columns_priv' is marked as crashed and should be repaired
2016-08-11 17:41:12 4420 [Warning] Checking table: '.\mysql\columns_priv'
2016-08-11 17:41:12 4420 [ERROR] mysql.columns_priv: 1 client is using or hasn't closed the table properly
2016-08-11 17:41:12 4420 [ERROR] mysqld.exe: Table '.\mysql\procs_priv' is marked as crashed and should be repaired
2016-08-11 17:41:12 4420 [Warning] Checking table: '.\mysql\procs_priv'
2016-08-11 17:41:12 4420 [ERROR] mysql.procs_priv: 1 client is using or hasn't closed the table properly
2016-08-11 17:41:12 4420 [Note] c:\xampp2\mysql\bin\mysqld.exe: ready for connections.
Version: '10.1.13-MariaDB' socket: '' port: 3306 mariadb.org binary distribution
InnoDB: Error: trying to access page number 700432 in space 226,
InnoDB: space name db/lac,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 16384, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.
2016-08-11 17:44:30 2324 InnoDB: Assertion failure in thread 8996 in file fil0fil.cc line 5866
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.
160811 17:44: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.