Welcome Guest. Please Login or Register  


You are here: Index > AMPPS > General Support > Topic : MySql won't start in Windows 7



Threaded Mode | Print  

 MySql won't start in Windows 7 (1 Replies, Read 5359 times)
larryurner
Group: Member
Post Group: Newbie
Posts: 1
Status:
Apache starts just fine, but MySql won't start. I'm using Windows 7

Here is whats in the error log

2014-04-02 19:29:55 3176 [Warning] You need to use --log-bin to make --binlog-format work.
2014-04-02 19:29:55 3176 [Note] Plugin 'FEDERATED' is disabled.
2014-04-02 19:29:55 3176 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-04-02 19:29:55 3176 [Note] InnoDB: The InnoDB memory heap is disabled
2014-04-02 19:29:55 3176 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-04-02 19:29:55 3176 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-04-02 19:29:55 3176 [Note] InnoDB: Not using CPU crc32 instructions
2014-04-02 19:29:55 3176 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-04-02 19:29:55 3176 [Note] InnoDB: Completed initialization of buffer pool
2014-04-02 19:29:55 3176 [Note] InnoDB: Highest supported file format is Barracuda.
2014-04-02 19:29:55 3176 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2641768 in the ib_logfiles!
2014-04-02 19:29:55 3176 [Note] InnoDB: Database was not shutdown normally!
2014-04-02 19:29:55 3176 [Note] InnoDB: Starting crash recovery.
2014-04-02 19:29:55 3176 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-04-02 19:29:56 3176 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace loc_word_wp/wp_usermeta uses space ID: 2 at filepath: .\loc_word_wp\wp_usermeta.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.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 won't start in Windows 7
bsdtux
Group: Member
Post Group: Newbie
Posts: 8
Status:
Can you go to the var directory of where AMPPS was installed go to the data directory, move ibdata1 to a new location and then try and restart mysql? If that doesn't work then move that file back into the directory.
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 19, 2024, 2:53 am.

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