Description:
Hi Guys,
I have installed wampserver2 on a windows 2003 server.
It gets down every time when I try to connect through phpmyadmin.
I have attached the log it creates.
Gayan
How to repeat:
thd: 0x229ef70
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...
006AC8BB mysqld.exe!???
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 022F2AF8=REPAIR TABLE `bundle`
thd->thread_id=2
thd->killed=NOT_KILLED
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.
InnoDB: Thread 4448 stopped in file .\os\os0sync.c line 574
InnoDB: Thread 5592 stopped in file .\os\os0sync.c line 271
InnoDB: Thread 3072 stopped in file .\sync\sync0arr.c line 337
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
120523 16:01:44 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...
InnoDB: Last MySQL binlog file position 0 10991, file name .\mysql-bin.000099
120523 16:01:45 InnoDB: Started; log sequence number 0 90537584
120523 16:01:45 [Note] Recovering after a crash using mysql-bin
120523 16:01:45 [Note] Starting crash recovery...
120523 16:01:45 [Note] Crash recovery finished.
120523 16:01:45 [Note] Event Scheduler: Loaded 0 events
120523 16:01:45 [Note] wampmysqld: ready for connections.
Version: '5.1.33-community-log' socket: '' port: 3306 MySQL Community Server (GPL)
120523 16:03:03 InnoDB: Error: (1500) Couldn't read the MAX(bundle_id) autoinc value from the index (PRIMARY).
120523 16:03:03 InnoDB: Assertion failure in thread 652 in file .\handler\ha_innodb.cc line 2601
InnoDB: Failing assertion: error == DB_SUCCESS
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-recovery.html
InnoDB: about forcing recovery.
120523 16:03:03 - mysqld got exception 0xc0000005 ;
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=262144
max_used_connections=1
max_threads=151
threads_connected=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 133304 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
