InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 070228 14:37:46 InnoDB: Error: page 2 log sequence number 97 3455791755 InnoDB: is in the future! Current system log sequence number 96 2586379276. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 070228 14:37:46 InnoDB: Error: page 4 log sequence number 97 1192394058 InnoDB: is in the future! Current system log sequence number 96 2586379276. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 070228 14:37:46 InnoDB: Error: page 11 log sequence number 97 3455791755 InnoDB: is in the future! Current system log sequence number 96 2586379276. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 070228 14:37:46 InnoDB: Error: page 586 log sequence number 97 1565731395 InnoDB: is in the future! Current system log sequence number 96 2586379276. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 070228 14:37:47 InnoDB: Error: page 5 log sequence number 97 3438843326 InnoDB: is in the future! Current system log sequence number 96 2586379276. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 070228 14:37:47 InnoDB: Error: page 6 log sequence number 97 3531479118 InnoDB: is in the future! Current system log sequence number 96 2586379276. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 070228 14:37:47 InnoDB: Error: page 59 log sequence number 97 3518299624 InnoDB: is in the future! Current system log sequence number 96 2586379276. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 070228 14:37:47 InnoDB: Error: page 51 log sequence number 97 3531650486 InnoDB: is in the future! Current system log sequence number 96 2586379276. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 070228 14:37:47 InnoDB: Error: page 10817 log sequence number 97 2770640850 InnoDB: is in the future! Current system log sequence number 96 2586379276. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. InnoDB: 1 transaction(s) which must be rolled back or cleaned up InnoDB: in total 39 row operations to undo InnoDB: Trx id counter is 0 10887680 070228 14:37:47 InnoDB: Error: page 4135 log sequence number 97 3598393336 InnoDB: is in the future! Current system log sequence number 96 2586379276. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 070228 14:37:47 InnoDB: Error: page 4130 log sequence number 97 3597418681 InnoDB: is in the future! Current system log sequence number 96 2586379276. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 070228 14:37:47 InnoDB: Error: page 91178 log sequence number 97 3518277871 InnoDB: is in the future! Current system log sequence number 96 2586379276. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 070228 14:37:47 InnoDB: Error: page 81921 log sequence number 97 3438661758 InnoDB: is in the future! Current system log sequence number 96 2586379276. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 070228 14:37:47 InnoDB: Error: page 4758 log sequence number 97 3438904961 InnoDB: is in the future! Current system log sequence number 96 2586379276. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 070228 14:37:47 InnoDB: Error: page 0 log sequence number 97 3531761598 InnoDB: is in the future! Current system log sequence number 96 2586379276. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 070228 14:37:47 InnoDB: Error: page 9 log sequence number 97 1899122123 InnoDB: is in the future! Current system log sequence number 96 2586379276. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 070228 14:37:47 InnoDB: Error: page 10 log sequence number 97 3455785245 InnoDB: is in the future! Current system log sequence number 96 2586379276. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 070228 14:37:47 InnoDB: Error: page 12 log sequence number 97 3455805247 InnoDB: is in the future! Current system log sequence number 96 2586379276. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. InnoDB: Starting in background the rollback of uncommitted transactions 070228 14:37:47 InnoDB: Rolling back trx with id 0 10887273, 39 rows to undo 070228 14:37:47 InnoDB: Error: page 39804 log sequence number 97 1899122123 InnoDB: is in the future! Current system log sequence number 96 2586379276. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 070228 14:37:47 InnoDB: Error: page 5134 log sequence number 97 1430619336 InnoDB: is in the future! Current system log sequence number 96 2586379276. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 070228 14:37:47 InnoDB: Error: page 32769 log sequence number 97 3599773205 InnoDB: is in the future! Current system log sequence number 96 2586379276. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 070228 14:37:47 InnoDB: Error: page 4108 log sequence number 97 1899122050 InnoDB: is in the future! Current system log sequence number 96 2586379276. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 070228 14:37:52 InnoDB: Error: page 38266 log sequence number 97 2119937115 InnoDB: is in the future! Current system log sequence number 96 2586379276. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 070228 14:37:57 InnoDB: Error: page 38257 log sequence number 97 2119937138 InnoDB: is in the future! Current system log sequence number 96 2586379276. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: for more information. 070228 14:38:02 InnoDB: Started; log sequence number 96 2586379276 mysqld: Table 'mysql.plugin' doesn't exist 070228 14:38:07 [ERROR] Can't open the mysql.plugin table. Please run the mysql_ upgrade script to create it. 070228 14:38:39 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist 070228 14:38:39 [Note] mysqld: ready for connections. Version: '5.2.3-falcon-alpha-community' socket: '' port: 3306 MySQL Community Server (GPL) 070228 14:38:39 [ERROR] Column count of mysql.db is wrong. Expected 22, found 20 . Created with MySQL 50021, now running 50203. Please use scripts/mysql_fix_priv ilege_tables 070228 14:38:39 [ERROR] mysql.user has no `Event_priv` column at position 29 070228 14:38:39 [ERROR] SCHEDULER: The system tables are damaged. The scheduler subsystem will be unusable during this run. InnoDB: Warning: a long semaphore wait: --Thread 3028 has waited at .\trx\trx0purge.c line 730 for 241.00 seconds the se maphore: Wait array cell state 1 Mutex at 02F9C284 created file .\trx\trx0rseg.c line 151, lock var 1 waiters flag 1 InnoDB: ###### Starts InnoDB Monitor for 30 secs to print diagnostic info: InnoDB: Pending preads 0, pwrites 0 ===================================== 070228 14:42:19 INNODB MONITOR OUTPUT ===================================== Per second averages calculated from the last 25 seconds ---------- SEMAPHORES ---------- OS WAIT ARRAY INFO: reservation count 4, signal count 3 --Thread 3028 has waited at .\trx\trx0purge.c line 730 for 256.00 seconds the se maphore: Wait array cell state 1 Mutex at 02F9C284 created file .\trx\trx0rseg.c line 151, lock var 1 waiters flag 1 Mutex spin waits 0, rounds 20, OS waits 1 RW-shared spins 4, OS waits 2; RW-excl spins 1, OS waits 1 ------------ TRANSACTIONS ------------ Trx id counter 0 10887680 Purge done for trx's n:o < 0 0 undo n:o < 0 0 History list length 12 Total number of lock structs in row lock hash table 0 LIST OF TRANSACTIONS FOR EACH SESSION: ---TRANSACTION 0 10887273, ACTIVE 272 sec, OS thread id 2192 ROLLING BACK -------- FILE I/O -------- I/O thread 0 state: wait Windows aio (insert buffer thread) I/O thread 1 state: wait Windows aio (log thread) I/O thread 2 state: wait Windows aio (read thread) I/O thread 3 state: wait Windows aio (write thread) Pending normal aio reads: 0, aio writes: 0, ibuf aio reads: 0, log i/o's: 0, sync i/o's: 0 Pending flushes (fsync) log: 0; buffer pool: 0 171 OS file reads, 3 OS file writes, 3 OS fsyncs 0.00 reads/s, 0 avg bytes/read, 0.00 writes/s, 0.00 fsyncs/s ------------------------------------- INSERT BUFFER AND ADAPTIVE HASH INDEX ------------------------------------- Ibuf: size 1, free list len 5, seg size 7, 0 inserts, 0 merged recs, 0 merges Hash table size 34679, used cells 0, node heap has 0 buffer(s) 0.00 hash searches/s, 0.00 non-hash searches/s --- LOG --- Log sequence number 96 2586379276 Log flushed up to 96 2586379276 Last checkpoint at 96 2586379276 0 pending log writes, 0 pending chkp writes 8 log i/o's done, 0.00 log i/o's/second ---------------------- BUFFER POOL AND MEMORY ---------------------- Total memory allocated 15715156; in additional pool allocated 1385216 Dictionary memory allocated 18296 Buffer pool size 512 Free buffers 479 Database pages 33 Modified db pages 0 Pending reads 0 Pending writes: LRU 0, flush list 0, single page 0 Pages read 33, created 0, written 0 0.00 reads/s, 0.00 creates/s, 0.00 writes/s No buffer pool page gets since the last printout -------------- ROW OPERATIONS -------------- 0 queries inside InnoDB, 0 queries in queue 1 read views open inside InnoDB Main thread id 3028, state: purging Number of rows inserted 0, updated 0, deleted 0, read 0 0.00 inserts/s, 0.00 updates/s, 0.00 deletes/s, 0.00 reads/s ---------------------------- END OF INNODB MONITOR OUTPUT ============================ 070228 14:49:56InnoDB: Assertion failure in thread 2396 in file .\dict\dict0loa .c line 486 InnoDB: Failing assertion: btr_pcur_is_on_user_rec(&pcur, &mtr) 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/mysql/en/Forcing_recovery.html InnoDB: about forcing recovery. InnoDB: Thread 3044 stopped in file .\sync\sync0arr.c line 126