Softaculous

Topic : MySql closes instantly after started !

Posted By: hazCreative on April 21, 2015, 8:38 am

Yesterday was working properly I wonder is anybody else is having this problem!

Posted By: Rishi_P on April 21, 2015, 1:26 pm | Post: 1

Hi hazCreative,

Which Operating System you are using ?
Show me your MySQL Error Log.

Posted By: hazCreative on April 21, 2015, 7:48 pm | Post: 2

I have OS yosemite ver 10.10.2.

It says it ´s started but actually is off.
While waiting and searching for an answer I did:
-Clean my hard disk in case was it for it! Ihave 120 GB able.
-In my terminal I killed all queries and restarted my computer.

when I go to the logo of user and log in with my password there is not problem to with that either. so what could be?

Posted By: hazCreative on April 21, 2015, 7:55 pm | Post: 3

Quote From : hazCreative April 21, 2015, 7:48 pm

Posted By: hazCreative on April 21, 2015, 7:55 pm | Post: 4

Quote From : hazCreative April 21, 2015, 7:48 pm

Posted By: hazCreative on April 21, 2015, 8:10 pm | Post: 5

Quote From : hazCreative April 21, 2015, 7:48 pm

2015-04-21 21:52:05 7550 [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 wp775/wp_commentmeta which uses space ID: 1 at filepath: ./wp775/wp_commentmeta.ibd
2015-04-21 21:52:05 a0e9e1d4 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
InnoDB: Error: could not open single-table tablespace file ./wp775/wp_commentmeta.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.

Posted By: Rishi_P on April 22, 2015, 7:26 am | Post: 6

Hi hazCreative,

Try this:

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.

Posted By: hazCreative on April 22, 2015, 5:08 pm | Post: 7

Your answer resolved all my nightmares ;-D

Thanks! Hope other gets this info when they need it ,too!