Recently My production server was corrupted due to maintenance shutdown by digital ocean. When we trying to recover our database we couldn't access our droplet. Somehow we managed to recover these (ibdata1, ib_logfile0, ib_logfile1 and some .frm) files. When i copied this files to my new mysql server(in another machine), I could't start the mysql server. I got this output
sudo service mysql restart
mysql stop/waiting
start: Job failed to start
I checked the log file and i got this error,
151019 8:55:27 [Warning] Using unique option prefix myisam-recover instead of $
151019 8:55:27 [Note] Plugin 'FEDERATED' is disabled.
151019 8:55:27 InnoDB: The InnoDB memory heap is disabled
151019 8:55:27 InnoDB: Mutexes and rw_locks use GCC atomic builtins
151019 8:55:27 InnoDB: Compressed tables use zlib 1.2.8
151019 8:55:27 InnoDB: Using Linux native AIO
151019 8:55:27 InnoDB: Initializing buffer pool, size = 128.0M
151019 8:55:27 InnoDB: Completed initialization of buffer pool
InnoDB: Error: log file ./ib_logfile0 is of different size 0 50331648 bytes
InnoDB: than specified in the .cnf file 0 5242880 bytes!
151019 8:55:27 [ERROR] Plugin 'InnoDB' init function returned error.
151019 8:55:27 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
151019 8:55:27 [ERROR] Unknown/unsupported storage engine: InnoDB
151019 8:55:27 [ERROR] Aborting
151019 8:55:27 [Note] /usr/sbin/mysqld: Shutdown complete
151019 8:55:28 [Warning] Using unique option prefix myisam-recover instead of $
151019 8:55:28 [Note] Plugin 'FEDERATED' is disabled.
151019 8:55:28 InnoDB: The InnoDB memory heap is disabled
151019 8:55:28 InnoDB: Mutexes and rw_locks use GCC atomic builtins
151019 8:55:28 InnoDB: Compressed tables use zlib 1.2.8
151019 8:55:28 InnoDB: Using Linux native AIO
151019 8:55:28 InnoDB: Initializing buffer pool, size = 128.0M
151019 8:55:28 InnoDB: Completed initialization of buffer pool
InnoDB: Error: log file ./ib_logfile0 is of different size 0 50331648 bytes
InnoDB: than specified in the .cnf file 0 5242880 bytes!
151019 8:55:28 [ERROR] Plugin 'InnoDB' init function returned error.
151019 8:55:28 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
151019 8:55:28 [ERROR] Unknown/unsupported storage engine: InnoDB
151019 8:55:28 [ERROR] Aborting
151019 8:55:28 [Note] /usr/sbin/mysqld: Shutdown complete
151019 8:55:29 [Warning] Using unique option prefix myisam-recover instead of $
151019 8:55:29 [Note] Plugin 'FEDERATED' is disabled.
151019 8:55:29 InnoDB: The InnoDB memory heap is disabled
151019 8:55:29 InnoDB: Mutexes and rw_locks use GCC atomic builtins
151019 8:55:29 InnoDB: Compressed tables use zlib 1.2.8
151019 8:55:29 InnoDB: Using Linux native AIO
151019 8:55:29 InnoDB: Initializing buffer pool, size = 128.0M
151019 8:55:29 InnoDB: Completed initialization of buffer pool
InnoDB: Error: log file ./ib_logfile0 is of different size 0 50331648 bytes
InnoDB: than specified in the .cnf file 0 5242880 bytes!
151019 8:55:29 [ERROR] Plugin 'InnoDB' init function returned error.
151019 8:55:29 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
151019 8:55:29 [ERROR] Unknown/unsupported storage engine: InnoDB
151019 8:55:29 [ERROR] Aborting
151019 8:55:29 [Note] /usr/sbin/mysqld: Shutdown complete
I tried adding innodb_log_file_size= 50331648 as suggested by #akuzminsky
Then I got this error log.
151022 6:54:13 [Warning] Using unique option prefix myisam-recover instead of $
151022 6:54:13 [Note] Plugin 'FEDERATED' is disabled.
151022 6:54:13 InnoDB: The InnoDB memory heap is disabled
151022 6:54:13 InnoDB: Mutexes and rw_locks use GCC atomic builtins
151022 6:54:13 InnoDB: Compressed tables use zlib 1.2.8
151022 6:54:13 InnoDB: Using Linux native AIO
151022 6:54:13 InnoDB: Initializing buffer pool, size = 128.0M
151022 6:54:13 InnoDB: Completed initialization of buffer pool
151022 6:54:13 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 15379293
151022 6:54:13 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Error: space header page consists of zero bytes in file ./toucan/ormcli$
InnoDB: Error: space header page consists of zero bytes in file ./toucan/catego$
InnoDB: Error: space header page consists of zero bytes in file ./toucan/survey$
InnoDB: Error: space header page consists of zero bytes in file ./toucan/compla$
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 15382291
InnoDB: Page directory corruption: infimum not pointed to
151022 6:54:13 InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex 10cfd0d80000000000000000000000000000000000e9e915000800000000001$
InnoDB: End of page dump
151022 6:54:13 InnoDB: Page checksum 282054872, prior-to-4.0.14-form checksum$
InnoDB: stored checksum 282054872, prior-to-4.0.14-form stored checksum 3468306$
InnoDB: Page lsn 0 15329557, low 4 bytes of lsn at page end 15329557
InnoDB: Page number (if stored to page already) 0,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be a file space header page
10:54:13 UTC - mysqld got signal 11 ;
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=131072
max_used_connections=0
max_threads=151
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 = 346701 K $
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+0x20)[0x7fa4d90e2f10]
/usr/sbin/mysqld(handle_fatal_signal+0x3d5)[0x7fa4d8fcd175]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x10340)[0x7fa4d7d5d340]
/usr/sbin/mysqld(+0x5f058a)[0x7fa4d91e258a]
/usr/sbin/mysqld(+0x56c44e)[0x7fa4d915e44e]
/usr/sbin/mysqld(+0x576137)[0x7fa4d9168137]
/usr/sbin/mysqld(+0x5a5632)[0x7fa4d9197632]
/usr/sbin/mysqld(+0x5a6699)[0x7fa4d9198699]
/usr/sbin/mysqld(+0x591ad3)[0x7fa4d9183ad3]
/usr/sbin/mysqld(+0x542a1a)[0x7fa4d9134a1a]
/usr/sbin/mysqld(+0x511d48)[0x7fa4d9103d48]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x41)[0x7fa4d8fcf$
/usr/sbin/mysqld(+0x302221)[0x7fa4d8ef4221]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0x92a)[0x7fa4d8ef821a]
/usr/sbin/mysqld(+0x28ac5b)[0x7fa4d8e7cc5b]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x45b)[0x7fa4d8e815db]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7fa4d739fec5]
/usr/sbin/mysqld(+0x286b18)[0x7fa4d8e78b18]
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.
Please help me to resolve this.
Thanks in advance.
Note lines in the error log:
InnoDB: Error: log file ./ib_logfile0 is of different size 0 50331648 bytes
InnoDB: than specified in the .cnf file 0 5242880 bytes!
The actual size of the redo log file differs from the size in MySQL config.
Add this line to my.cnf
innodb_log_file_size= 50331648
If the tablespace is corrupted you'll still have to heal it. But at least MySQL won't stop at this step.
Related
My disk still has a lot of space, so it's not the memory problem.
Filesystem Size Used Avail Use% Mounted on
/dev/vda1 55G 17G 36G 32% /
Here's the error log
190712 7:55:45 [Warning] Using unique option prefix myisam-recover
instead of myisam-recover-options is deprecated and will be removed in
a future release. Please use the full name instead.
190712 7:55:45 [Note] Plugin 'FEDERATED' is disabled.
190712 7:55:45 InnoDB: The InnoDB memory heap is disabled
190712 7:55:45 InnoDB: Mutexes and rw_locks use GCC atomic builtins
190712 7:55:45 InnoDB: Compressed tables use zlib 1.2.8
190712 7:55:45 InnoDB: Using Linux native AIO
190712 7:55:45 InnoDB: Initializing buffer pool, size = 128.0M
InnoDB: mmap(137363456 bytes) failed; errno 12
190712 7:55:45 InnoDB: Completed initialization of buffer pool
190712 7:55:45 InnoDB: Fatal error: cannot allocate memory for the
buffer pool
190712 7:55:45 [ERROR] Plugin 'InnoDB' init function returned error.
190712 7:55:45 [ERROR] Plugin 'InnoDB' registration as a STORAGE
ENGINE failed.
190712 7:55:45 [ERROR] Unknown/unsupported storage engine: InnoDB
190712 7:55:45 [ERROR] Aborting
190712 7:55:45 [Note] /usr/sbin/mysqld: Shutdown complete
I have to restart MySQL manually
One of our servers was the subject of a ransomware attack from a group of international Hackers. So we’ve re-grouped and started over and the only unaffected data we had was the ibdata1 file stored in mysql program data folder.
We would like to restore that data on the new instance so that we carry forward our operations but after trying to run the new installation of mysql it the service stops with error 1067. It suggests to delete all files created by InnoDB: all ibdata files and all ib_logfile files. If I do that the service will run but I can’t do it because I need to access the data in this particular data file. I’ve also added these two lines in my .cnf file
innodb_force_recovery=6
innodb_fast_shutdown=0
That hasn’t worked. So I deleted just the log files and it created new log files along with it came this error
190223 11:38:48 [Note] Plugin 'FEDERATED' is disabled.
190223 11:38:48 InnoDB: The InnoDB memory heap is disabled
190223 11:38:48 InnoDB: Mutexes and rw_locks use Windows interlocked functions
190223 11:38:48 InnoDB: Compressed tables use zlib 1.2.3
190223 11:38:48 InnoDB: Initializing buffer pool, size = 2.0G
190223 11:38:48 InnoDB: Completed initialization of buffer pool
190223 11:38:48 InnoDB: highest supported file format is Barracuda.
InnoDB: No valid checkpoint found.
InnoDB: If this error appears when you are creating an InnoDB database,
InnoDB: the problem may be that during an earlier attempt you managed
InnoDB: to create the InnoDB data files, but log file creation failed.
InnoDB: If that is the case, please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/error-creating-innodb.html
190223 11:38:48 [ERROR] Plugin 'InnoDB' init function returned error.
190223 11:38:48 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
190223 11:38:48 [ERROR] Unknown/unsupported storage engine: INNODB
190223 11:38:48 [ERROR] Aborting
Then I replaced the log files with the same ones I used with the original ibdata1 file then I got this error.
190223 12:11:26 [Note] Plugin 'FEDERATED' is disabled.
190223 12:11:26 InnoDB: The InnoDB memory heap is disabled
190223 12:11:26 InnoDB: Mutexes and rw_locks use Windows interlocked functions
190223 12:11:26 InnoDB: Compressed tables use zlib 1.2.3
190223 12:11:26 InnoDB: Initializing buffer pool, size = 2.0G
190223 12:11:26 InnoDB: Completed initialization of buffer pool
InnoDB: Error: log file .\ib_logfile0 is of different size 0 1073741824 bytes
InnoDB: than specified in the .cnf file 0 224395264 bytes!
190223 12:11:26 [ERROR] Plugin 'InnoDB' init function returned error.
190223 12:11:26 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
190223 12:11:26 [ERROR] Unknown/unsupported storage engine: INNODB
190223 12:11:26 [ERROR] Aborting
It appears there is a check point somewhere in the log files that is necessary for the data file to be read properly by the mysql service. Maybe I need to specify the log file size in the my.ini config file. But I don’t know how to go about it.
Any help will really come in handy here.
In your my.ini (or my.cnf) file, add (or replace) the following line:
innodb_log_file_size = 1024M
See https://dev.mysql.com/doc/refman/5.6/en/innodb-parameters.html#sysvar_innodb_log_file_size for details.
When I tried to restart mysql after I restarted Linux server,
I got in trouble, I am not able to start mysql It is responding Job failed to start
here is error log
170225 0:46:41 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
170225 0:46:41 [Note] Plugin 'FEDERATED' is disabled.
170225 0:46:41 InnoDB: The InnoDB memory heap is disabled
170225 0:46:41 InnoDB: Mutexes and rw_locks use GCC atomic builtins
170225 0:46:41 InnoDB: Compressed tables use zlib 1.2.8
170225 0:46:41 InnoDB: Using Linux native AIO
170225 0:46:41 InnoDB: Initializing buffer pool, size = 128.0M
InnoDB: mmap(137363456 bytes) failed; errno 12
170225 0:46:41 InnoDB: Completed initialization of buffer pool
170225 0:46:41 InnoDB: Fatal error: cannot allocate memory for the buffer pool
170225 0:46:41 [ERROR] Plugin 'InnoDB' init function returned error.
170225 0:46:41 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
170225 0:46:41 [ERROR] Unknown/unsupported storage engine: InnoDB
170225 0:46:41 [ERROR] Aborting
170225 0:46:41 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
170225 0:46:41 [Note] Plugin 'FEDERATED' is disabled.
170225 0:46:41 InnoDB: The InnoDB memory heap is disabled
170225 0:46:41 InnoDB: Mutexes and rw_locks use GCC atomic builtins
170225 0:46:41 InnoDB: Compressed tables use zlib 1.2.8
170225 0:46:41 InnoDB: Using Linux native AIO
170225 0:46:41 InnoDB: Initializing buffer pool, size = 128.0M
InnoDB: mmap(137363456 bytes) failed; errno 12
170225 0:46:41 InnoDB: Completed initialization of buffer pool
170225 0:46:41 InnoDB: Fatal error: cannot allocate memory for the buffer pool
170225 0:46:41 [ERROR] Plugin 'InnoDB' init function returned error.
170225 0:46:41 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
170225 0:46:41 [ERROR] Unknown/unsupported storage engine: InnoDB
170225 0:46:41 [ERROR] Aborting
thx for your help
Maybe the option "skip-innodb" was uncommented on configuration file my.cnf. If that's the case, comment the line again. If you don't want to use INNODB, you must modify your tables to use another table format, as MyISAM p.e.
I tried running optimize on one of my tables, and when I did the server crashed. Now when I try to restart it, I get this error:
The server quit without updating PID file (/usr/local/mysql/data/Diskise.pid).
Then when I look at the error log to help me see what happened, I don't really understand it. What can I do to get my server back up?
131117 17:13:43 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/data
2013-11-17 17:13:44 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2013-11-17 17:13:44 29352 [Note] Plugin 'FEDERATED' is disabled.
2013-11-17 17:13:44 29352 [Note] InnoDB: The InnoDB memory heap is disabled
2013-11-17 17:13:44 29352 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2013-11-17 17:13:44 29352 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-11-17 17:13:44 29352 [Note] InnoDB: Using Linux native AIO
2013-11-17 17:13:44 29352 [Note] InnoDB: Not using CPU crc32 instructions
2013-11-17 17:13:44 29352 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2013-11-17 17:13:44 29352 [Note] InnoDB: Completed initialization of buffer pool
2013-11-17 17:13:44 29352 [Note] InnoDB: Highest supported file format is Barracuda.
2013-11-17 17:13:44 29352 [Note] InnoDB: Log scan progressed past the checkpoint lsn 57196040504
2013-11-17 17:13:44 29352 [Note] InnoDB: Database was not shutdown normally!
2013-11-17 17:13:44 29352 [Note] InnoDB: Starting crash recovery.
2013-11-17 17:13:44 29352 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-11-17 17:13:44 29352 [Note] InnoDB: Restoring possible half-written data pages
2013-11-17 17:13:44 29352 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 57201283072
InnoDB: Doing recovery: scanned up to log sequence number 57204973005
InnoDB: Error: trying to access page number 377945542 in space 0,
InnoDB: space name ./ibdata1,
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.
2013-11-17 17:13:44 b73ae700 InnoDB: Assertion failure in thread 3074090752 in file fil0fil.cc line 5423
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.
17:13:44 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=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
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 = 67592 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/local/mysql/bin/mysqld(my_print_stacktrace+0x33)[0x84e19b3]
/usr/local/mysql/bin/mysqld(handle_fatal_signal+0x3c8)[0x826c218]
[0xb76ef400]
[0xb76ef416]
/lib/i386-linux-gnu/libc.so.6(gsignal+0x4f)[0xb73de1df]
/lib/i386-linux-gnu/libc.so.6(abort+0x175)[0xb73e1825]
/usr/local/mysql/bin/mysqld[0x864f06f]
/usr/local/mysql/bin/mysqld[0x861d3f3]
/usr/local/mysql/bin/mysqld[0x861e03d]
/usr/local/mysql/bin/mysqld[0x8605e5c]
/usr/local/mysql/bin/mysqld[0x85d135f]
/usr/local/mysql/bin/mysqld[0x85c649d]
/usr/local/mysql/bin/mysqld[0x85c739e]
/usr/local/mysql/bin/mysqld[0x85c844f]
/usr/local/mysql/bin/mysqld[0x85b33d9]
/usr/local/mysql/bin/mysqld[0x84f593a]
/usr/local/mysql/bin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x43)[0x81c1c93]
/usr/local/mysql/bin/mysqld[0x82f32bd]
/usr/local/mysql/bin/mysqld(_Z11plugin_initPiPPci+0x7c8)[0x82f5058]
/usr/local/mysql/bin/mysqld(_Z11mysqld_mainiPPc+0x8c3)[0x81bae83]
/usr/local/mysql/bin/mysqld(main+0x1b)[0x819b30b]
/lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf3)[0xb73c94d3]
/usr/local/mysql/bin/mysqld[0x81afa11]
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.
131117 17:13:44 mysqld_safe mysqld from pid file /usr/local/mysql/data/Diskise.pid ended
In my Moodle database, everytime I select the mdl_certificate table, the MySQL server goes down. I thought it could be a problem with the PHPMyAdmin, but I installed the MySQL Workbench and the same still happens.
So I tried the console. The problem persists. I got two prints:
I've never seen this. How can I solve it?
Thanks!
UPDATE:
This is the log around the time the error was showed:
130411 8:51:20 [Note] Plugin 'FEDERATED' is disabled.
130411 8:51:20 InnoDB: The InnoDB memory heap is disabled
130411 8:51:20 InnoDB: Mutexes and rw_locks use Windows interlocked functions
130411 8:51:20 InnoDB: Compressed tables use zlib 1.2.3
130411 8:51:20 InnoDB: Initializing buffer pool, size = 128.0M
130411 8:51:20 InnoDB: Completed initialization of buffer pool
130411 8:51:20 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!
130411 8:51:20 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
130411 8:51:20 InnoDB: Operating system error number 1392 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html
InnoDB: File name .\prestashopprod
InnoDB: File operation call: 'readdir_next_file'.
InnoDB: Error: os_file_readdir_next_file() returned -1 in
InnoDB: directory .\prestashopprod
InnoDB: Crash recovery may have failed for some .ibd files!
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Last MySQL binlog file position 0 4793, file name .\mysql-bin.000062
130411 8:51:33 InnoDB: Waiting for the background threads to start
130411 8:51:34 InnoDB: 1.1.8 started; log sequence number 795429719
130411 8:51:34 [Note] Recovering after a crash using mysql-bin
130411 8:51:34 [Note] Starting crash recovery...
130411 8:51:34 [Note] Crash recovery finished.
130411 8:51:34 [Note] Event Scheduler: Loaded 0 events
130411 8:51:34 [Note] wampmysqld: ready for connections.
Version: '5.5.20-log' socket: '' port: 3306 MySQL Community Server (GPL)
The solution was drop the tables and re-create them. Luckly, they were empty.