Welcome Guest. Please Login or Register  


You are here: Index > AMPPS > General Support > Topic : MySQL will not Start



Threaded Mode | Print  

 MySQL will not Start (7 Replies, Read 94074 times)
ptmuldoon
Group: Member
Post Group: Newbie
Posts: 5
Status:
Things were working great, but today I just launched Ampps and MySQL will not start.  This is using a Windows 7 machine.

Looking at the log, I see

FYI, the 'testdrive' database is what I created for yii as I attempt to learn more about the framework

Quote

2013-10-18 15:55:27 6808 [Note] Plugin 'FEDERATED' is disabled.
2013-10-18 15:55:27 6808 [Note] InnoDB: The InnoDB memory heap is disabled
2013-10-18 15:55:27 6808 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-10-18 15:55:27 6808 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-10-18 15:55:27 6808 [Note] InnoDB: Not using CPU crc32 instructions
2013-10-18 15:55:27 6808 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2013-10-18 15:55:27 6808 [Note] InnoDB: Completed initialization of buffer pool
2013-10-18 15:55:27 6808 [Note] InnoDB: Highest supported file format is Barracuda.
2013-10-18 15:55:27 6808 [Note] InnoDB: The log sequence numbers 1628736 and 1628736 in ibdata files do not match the log sequence number 1628746 in the ib_logfiles!
2013-10-18 15:55:27 6808 [Note] InnoDB: Database was not shutdown normally!
2013-10-18 15:55:27 6808 [Note] InnoDB: Starting crash recovery.
2013-10-18 15:55:27 6808 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-10-18 15:55:27 6808 [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 testdrive/tbl_user which uses space ID: 1 at filepath: .\testdrive\tbl_user.ibd
InnoDB: Error: could not open single-table tablespace file .\testdrive\tbl_user.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.
IP: --   

MySQL will not Start
DeeJaVu
Group: Member
Post Group: Newbie
Posts: 17
Status:
i have exact the same error


Quote
2013-10-19 06:50:53 3712 [Note] Plugin 'FEDERATED' is disabled.
2013-10-19 06:50:53 3712 [Note] InnoDB: The InnoDB memory heap is disabled
2013-10-19 06:50:53 3712 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-10-19 06:50:53 3712 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-10-19 06:50:53 3712 [Note] InnoDB: Not using CPU crc32 instructions
2013-10-19 06:50:53 3712 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2013-10-19 06:50:53 3712 [Note] InnoDB: Completed initialization of buffer pool
2013-10-19 06:50:53 3712 [Note] InnoDB: Highest supported file format is Barracuda.
2013-10-19 06:50:53 3712 [Note] InnoDB: The log sequence numbers 1631613 and 1631613 in ibdata files do not match the log sequence number 2733317 in the ib_logfiles!
2013-10-19 06:50:53 3712 [Note] InnoDB: Database was not shutdown normally!
2013-10-19 06:50:53 3712 [Note] InnoDB: Starting crash recovery.
2013-10-19 06:50:53 3712 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-10-19 06:50:53 3712 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace gazelle/api_applications uses space ID: 5 at filepath: .\gazelle\api_applications.ibd. Cannot open tablespace mysql/slave_worker_info which uses space ID: 5 at filepath: .\mysql\slave_worker_info.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\slave_worker_info.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.
IP: --   

MySQL will not Start
DeeJaVu
Group: Member
Post Group: Newbie
Posts: 17
Status:
i found a way to fix this. just follow my steps and mysql will start again.

1. Go to Ampps\mysql\data

2. Create a "Backup" folder under data

3. Move those files to your Backup folder
Quote
innodb_index_stats.frm
innodb_index_stats.ibd
innodb_table_stats.frm
innodb_table_stats.ibd
slave_master_info.ibd
slave_relay_log_info.frm
slave_relay_log_info.ibd
slave_worker_info.frm
slave_worker_info.ibd


4. now open control panel and click on start under mysql

5. smile :)

6. reply back
IP: --   

MySQL will not Start
ptmuldoon
Group: Member
Post Group: Newbie
Posts: 5
Status:
Yes,

I found that it must be something with the initial database creation i'm following in my Yii tutorial.  If I remove that folder from they mysql folder at:

C:\Program Files\Ampps\mysql\data

Then MySql starts just fine.  I could then even place the folder back but phpmyadmin seemed to run slow as well.

I'll try and trouble shoot why the Yii database (1 table in the DB) is causing the issue, but have moved on in the book already.

But hope this helps someone else if they come across the same problem.
IP: --   

MySQL will not Start
tidus
Group: Member
Post Group: Super Member
Posts: 1121
Status:
Hi,

Take a backup of Ampps\mysql\data folder before doing anything.

The workaround/solution can be found here itself in log.
Quote

2013-10-19 06:50:53 3712 [ERROR] InnoDB: Attempted to open a previously
opened tablespace. Previous tablespace gazelle/api_applications uses
space ID: 5 at filepath: .\gazelle\api_applications.ibd. Cannot open
tablespace mysql/slave_worker_info which uses space ID: 5 at filepath:
.\mysql\slave_worker_info.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\slave_worker_info.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.


  1. If there is a permission problem in the file and mysqld cannot open the file, you should modify the permissions.
  2. If the table is not needed, or you can restore it from a backup, then you can remove the .ibd file, and InnoDB will do a normal crash recovery and ignore that table.
  3. If the file system or the disk is broken, and you cannot remove the .ibd file, you can set innodb_force_recovery > 0 in my.cnf and force InnoDB to continue crash recovery here.


-----------------------
Follow AMPPS on,
Twitter : https://twitter.com/AMPPS_Stack
Facebook :  http://www.facebook.com/softaculousampps
Google+ : https://plus.google.com/+AmppsStack
IP: --   

MySQL will not Start
DeeJaVu
Group: Member
Post Group: Newbie
Posts: 17
Status:
Quote From : tidus October 22, 2013, 7:56 am
Hi,

Take a backup of Ampps\mysql\data folder before doing anything.

The workaround/solution can be found here itself in log.
Quote

2013-10-19 06:50:53 3712 [ERROR] InnoDB: Attempted to open a previously
opened tablespace. Previous tablespace gazelle/api_applications uses
space ID: 5 at filepath: .\gazelle\api_applications.ibd. Cannot open
tablespace mysql/slave_worker_info which uses space ID: 5 at filepath:
.\mysql\slave_worker_info.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\slave_worker_info.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.


  1. If there is a permission problem in the file and mysqld cannot open the file, you should modify the permissions.
  2. If the table is not needed, or you can restore it from a backup, then you can remove the .ibd file, and InnoDB will do a normal crash recovery and ignore that table.
  3. If the file system or the disk is broken, and you cannot remove the .ibd file, you can set innodb_force_recovery > 0 in my.cnf and force InnoDB to continue crash recovery here.


we already fixed that  :/
IP: --   

MySQL will not Start
mukabadak
Group: Member
Post Group: Newbie
Posts: 1
Status:
Quote From : DeeJaVu October 19, 2013, 5:16 am
i found a way to fix this. just follow my steps and mysql will start again.

1. Go to Ampps\mysql\data

2. Create a "Backup" folder under data

3. Move those files to your Backup folder
Quote
innodb_index_stats.frm
innodb_index_stats.ibd
innodb_table_stats.frm
innodb_table_stats.ibd
slave_master_info.ibd
slave_relay_log_info.frm
slave_relay_log_info.ibd
slave_worker_info.frm
slave_worker_info.ibd


4. now open control panel and click on start under mysql

5. smile :)

6. reply back


You save my day. :xd:
IP: --   

MySQL will not Start
Rishi_P
Group: Member
Post Group: Elite Member
Posts: 317
Status:
Hi,

You can try this method also:

1. Open Ampps Application -> MySQL Tab -> Configuration.

2. In [mysqld] section, add the following line:
innodb_force_recovery = 1

3. Save the file and try starting MySQL

4. Remove that line which you just added and Save.
IP: --   

« Previous    Next »

Threaded Mode | Print  



Jump To :


Users viewing this topic
1 guests, 0 users.


All times are GMT. The time now is March 28, 2024, 10:53 pm.

  Powered By AEF 1.0.8 © 2007-2008 Electron Inc.Queries: 11  |  Page Created In:0.020