Welcome Guest. Please Login or Register  
Client Area  |  Softaculous Cloud  |  Calendar  |  Quick Links  |  
   


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



Normal Mode | Print  

 MySQL not starting, MySQL is not starting (8 Replies, Read 18134 times)
anoniemand
November 18, 2013, 7:35 pm
Group: Member
Post Group: Newbie
Posts: 3
Status:
Hope someone can help.  MySQL is not starting.  Apache is starting fine.

Here is the error log. 

2013-11-18 21:25:25 1319 [Note] Plugin 'FEDERATED' is disabled.
2013-11-18 21:25:25 1319 [Note] InnoDB: The InnoDB memory heap is disabled
2013-11-18 21:25:25 1319 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2013-11-18 21:25:25 1319 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-11-18 21:25:25 1319 [Note] InnoDB: Not using CPU crc32 instructions
2013-11-18 21:25:25 1319 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2013-11-18 21:25:25 1319 [Note] InnoDB: Completed initialization of buffer pool
2013-11-18 21:25:25 1319 [Note] InnoDB: Highest supported file format is Barracuda.
2013-11-18 21:25:25 1319 [Note] InnoDB: The log sequence numbers 3463523 and 3463523 in ibdata files do not match the log sequence number 21075251 in the ib_logfiles!
2013-11-18 21:25:25 1319 [Note] InnoDB: Database was not shutdown normally!
2013-11-18 21:25:25 1319 [Note] InnoDB: Starting crash recovery.
2013-11-18 21:25:25 1319 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-11-18 21:25:25 1319 [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 testdb/dr_actions which uses space ID: 1 at filepath: ./testdb/dr_actions.ibd
2013-11-18 21:25:25 a171e1a8  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 ./testdb/dr_actions.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.


I am a total noob, so please be as clear as possible.

Thanks
IP: --   


Threads
 anoniemand   MySQL not starting, MySQL is not starting (8 Replies, Read 18134 times)
    |--  ketan   Hi, 1. Open...   on November 19, 2013, 7:32 am
    |--  fonte   Hi, 1. Open...   on December 4, 2013, 5:03 am
    |--  ketan   Hi, How did...   on December 4, 2013, 6:42 am
    |--  fonte   Hi, How did...   on December 4, 2013, 6:51 am
    |--  pluscss   did the same.....   on January 9, 2014, 5:21 pm
    |--  cpardon   Tried this trick....   on February 6, 2014, 3:13 am
    |--  freestyle   Thanks I had...   on February 16, 2014, 8:18 am
    |--  tidus   Hi, For those...   on February 17, 2014, 6:46 am

« Previous    Next »

Normal Mode | Print  



Users viewing this topic
1 guests, 0 users.


All times are GMT. The time now is September 21, 2024, 6:09 pm.

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