Jump to content
AprendendoC

Erro ao iniciar serviço do Mysql

Recommended Posts

AprendendoC

buenas galera estou com um problema quando inicio o meu serviço do mySQL, nãom sei o que fazer...

aqui está o error log dele..

2013-08-07 18:02:36 1380 [Note] Plugin 'FEDERATED' is disabled.

2013-08-07 18:02:36 1380 [Note] InnoDB: The InnoDB memory heap is disabled

2013-08-07 18:02:36 1380 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions

2013-08-07 18:02:36 1380 [Note] InnoDB: Compressed tables use zlib 1.2.3

2013-08-07 18:02:36 1380 [Note] InnoDB: Not using CPU crc32 instructions

2013-08-07 18:02:36 1380 [Note] InnoDB: Initializing buffer pool, size = 128.0M

2013-08-07 18:02:36 1380 [Note] InnoDB: Completed initialization of buffer pool

2013-08-07 18:02:36 1380 [Note] InnoDB: Highest supported file format is Barracuda.

2013-08-07 18:02:36 1380 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1604689 in the ib_logfiles!

2013-08-07 18:02:36 1380 [Note] InnoDB: Database was not shutdown normally!

2013-08-07 18:02:36 1380 [Note] InnoDB: Starting crash recovery.

2013-08-07 18:02:36 1380 [Note] InnoDB: Reading tablespace information from the .ibd files...

2013-08-07 18:02:36 1380 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/innodb_table_stats uses space ID: 1 at filepath: .\mysql\innodb_table_stats.ibd. Cannot open tablespace teste/usuarios which uses space ID: 1 at filepath: .\teste\usuarios.ibd

InnoDB: Error: could not open single-table tablespace file .\teste\usuarios.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.

estou usandoo easy php..

o erro acontece quando crio tabelas no banco de dados, na hora funciona normal, mas quando desligo o pc ou reinicio ele não funciona mais...

alguem saberia o que está acontecendo?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...

Important Information

By using this site you accept our Terms of Use and Privacy Policy. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.