Olá a todos,
O serviço do mysql não inicia no wampserver.
Desde já agradeço a ajuda.
Abaixo o log do mysql:
2015-01-07 14:44:37 4788 [Note] Plugin 'FEDERATED' is disabled.
2015-01-07 14:44:37 4788 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-01-07 14:44:37 4788 [Note] InnoDB: The InnoDB memory heap is disabled
2015-01-07 14:44:37 4788 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-01-07 14:44:37 4788 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-01-07 14:44:37 4788 [Note] InnoDB: Not using CPU crc32 instructions
2015-01-07 14:44:37 4788 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2015-01-07 14:44:37 4788 [Note] InnoDB: Completed initialization of buffer pool
2015-01-07 14:44:38 4788 [Note] InnoDB: Highest supported file format is Barracuda.
2015-01-07 14:44:38 4788 [Note] InnoDB: The log sequence numbers 1703653 and 1703653 in ibdata files do not match the log sequence number 1704552 in the ib_logfiles!
2015-01-07 14:44:38 4788 [Note] InnoDB: Database was not shutdown normally!
2015-01-07 14:44:38 4788 [Note] InnoDB: Starting crash recovery.
2015-01-07 14:44:38 4788 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-01-07 14:44:38 4788 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace posto/usuario uses space ID: 10 at filepath: .\posto\usuario.ibd. Cannot open tablespace tw/s38df_banners which uses space ID: 10 at filepath: .\tw\s38df_banners.ibd
InnoDB: Error: could not open single-table tablespace file .\tw\s38df_banners.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
