Ir para conteúdo

POWERED BY:

Arquivado

Este tópico foi arquivado e está fechado para novas respostas.

William Monteiro_35606

Erro Mysql Xampp

Recommended Posts

Galera eu troquei meu note e nesta maquina estou tendo problemas com o xampp, toda vez que tento iniciar o serviço do apache ou mysql da erro... ontem aconteceu a mesma coisa e precisei desisntalar e instalar novamente o xampp.

 

Na minha maquina antiga eu tinha problema com o skype, mas nessa eu não sei ainda o pq:

 

Mensagem de erro:

 

09:22:08 [mysql] Error: MySQL shutdown unexpectedly.
09:22:08 [mysql] This may be due to a blocked port, missing dependencies,
09:22:08 [mysql] improper privileges, a crash, or a shutdown by another method.
09:22:08 [mysql] Press the Logs button to view error logs and check
09:22:08 [mysql] the Windows Event Viewer for more clues
09:22:08 [mysql] If you need more help, copy and post this
09:22:08 [mysql] entire log window on the forums

 

LOG

2013-09-20 09:24:32 5284 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-09-20 09:24:32 5284 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-09-20 09:24:32 5284 [Note] InnoDB: Not using CPU crc32 instructions
2013-09-20 09:24:32 5284 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-09-20 09:24:32 5284 [Note] InnoDB: Completed initialization of buffer pool
2013-09-20 09:24:32 5284 [Note] InnoDB: Highest supported file format is Barracuda.
2013-09-20 09:24:32 5284 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1786561 in the ib_logfiles!
2013-09-20 09:24:32 5284 [Note] InnoDB: Database was not shutdown normally!
2013-09-20 09:24:32 5284 [Note] InnoDB: Starting crash recovery.
2013-09-20 09:24:32 5284 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-09-20 09:24:32 5284 [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 seg_solution/agenda_frota which uses space ID: 1 at filepath: .\seg_solution\agenda_frota.ibd
InnoDB: Error: could not open single-table tablespace file .\seg_solution\agenda_frota.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.

 

O estranho e que ele da um erro bem um arquivo da tabela de um site

 

which uses space ID: 1 at filepath: .\seg_solution\agenda_frota.ibd

 

Compartilhar este post


Link para o post
Compartilhar em outros sites

×

Informação importante

Ao usar o fórum, você concorda com nossos Termos e condições.