WampServer

Dear All ,

I was able to successfully install WAMP server in my windows machine with the green icon loaded.

However, today , I am not able to start my MySql server for some reason. Please Advice. Below is the error I am facing :
2015-06-09 18:14:18 4772 [Note] InnoDB: Starting crash recovery.
2015-06-09 18:14:18 4772 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-06-09 18:14:19 4772 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace healthcompare/wp_commentmeta uses space ID: 11 at filepath: .\healthcompare\wp_commentmeta.ibd. Cannot open tablespace ushouldknowtv/wp_commentmeta which uses space ID: 11 at filepath: .\ushouldknowtv\wp_commentmeta.ibd
InnoDB: Error: could not open single-table tablespace file .\ushouldknowtv\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.

Greatly appreciate if you can assist me.
Thank you ,
Best Regards,
Nilay

You have corrupted your database, and MYSQL has failed to recover it using its automatic restart/recovery mechanism.

First this may well be caused by closing windows before stopping WAMPServer/MySQL

The answer is in the information that MySQL puts in the error log you supplied.


First, if you have a backup (ha ha) then restore your database from the backup.

Second option

Quote

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.

To do this you need to edit the my.ini file,
.. If you are using WAMPServer 64bit, look for this section heading

[wampmysqld]

and change it to

[wampmysqld64]

This fixes a minor bug in the WAMPServer2.5 64bit release.

Now read and understand this and any other MYSQL help you can find Forcing InnoDB Recovery


To set the innodb_force_recovery flag you will need to add it and its value after the
(32bit WAMP) [wampmysqld] line
or (64bit WAMP) [wampmysqld64] line

[wampmysqld]
innodb_force_recovery = 1

For example.


No guarantees are give that this will work but before you have to throw your database away is worth a try. As per the MySQL documentation start with innodb_force_recovery = 1 and then move up one at a time until the recovery works. You will have to check the mysql error log each time to see if recovery has worked.

Remove this line when completed dont leave it there.

---------------------------------------------------------------------------------------------
(Windows 10 Pro 64bit) (Wampserver 3.3.4 64bit) Aestan Tray Menu 3.2.5.4
<Apache versions MULTIPE> <PHP versions MULTIPLE> <MySQL Versions MULTIPLE>
<MariaDB versions MULTIPLE> <phpMyAdmin versions MULTIPLE> <MySQL Workbench 8.0.23>
Read The Manuals Apache -- MySQL -- PHP -- phpMyAdmin
Get your Apache/MySQL/mariaDB/PHP ADDONs here from the WAMPServer alternate Repo
-X-X-X- Backup your databases regularly Here is How dont regret it later! Yes even when developing -X-X-X-

Hi RIggs ,
I had uninstalled the whole setup and installed again with a new DB. It worked again for few days and again it started behaving the same manner.
Let me follow your procedure of second option and revert.
Thanks a lot pal ,

--
Nilay

Dear Riggs ,

As per your instructions, I have added the changed the my.ini file to wampmysqld64, however, still receiving the below error : , Please advise the exact steps I need to make it working. Thanks a lot once again for all your support.

2015-06-13 12:08:21 3872 [Note] Plugin 'FEDERATED' is disabled.
2015-06-13 12:08:21 3872 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-06-13 12:08:21 3872 [Note] InnoDB: The InnoDB memory heap is disabled
2015-06-13 12:08:21 3872 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-06-13 12:08:21 3872 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-06-13 12:08:21 3872 [Note] InnoDB: Not using CPU crc32 instructions
2015-06-13 12:08:22 3872 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2015-06-13 12:08:22 3872 [Note] InnoDB: Completed initialization of buffer pool
2015-06-13 12:08:23 3872 [Note] InnoDB: Highest supported file format is Barracuda.
2015-06-13 12:08:23 3872 [Note] InnoDB: The log sequence numbers 21670721 and 21670721 in ibdata files do not match the log sequence number 22542487 in the ib_logfiles!
2015-06-13 12:08:23 3872 [Note] InnoDB: Database was not shutdown normally!
2015-06-13 12:08:23 3872 [Note] InnoDB: Starting crash recovery.
2015-06-13 12:08:23 3872 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-06-13 12:08:27 3872 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace healthcompare/wp_commentmeta uses space ID: 11 at filepath: .\healthcompare\wp_commentmeta.ibd. Cannot open tablespace _healthcompare/wp_commentmeta which uses space ID: 11 at filepath: .\_healthcompare\wp_commentmeta.ibd
InnoDB: Error: could not open single-table tablespace file .\_healthcompare\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.
2015-06-13 12:08:40 5124 [Note] Plugin 'FEDERATED' is disabled.
2015-06-13 12:08:40 5124 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-06-13 12:08:40 5124 [Note] InnoDB: The InnoDB memory heap is disabled
2015-06-13 12:08:40 5124 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-06-13 12:08:40 5124 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-06-13 12:08:40 5124 [Note] InnoDB: Not using CPU crc32 instructions
2015-06-13 12:08:40 5124 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2015-06-13 12:08:40 5124 [Note] InnoDB: Completed initialization of buffer pool
2015-06-13 12:08:40 5124 [Note] InnoDB: Highest supported file format is Barracuda.
2015-06-13 12:08:40 5124 [Note] InnoDB: The log sequence numbers 21670721 and 21670721 in ibdata files do not match the log sequence number 22542487 in the ib_logfiles!
2015-06-13 12:08:40 5124 [Note] InnoDB: Database was not shutdown normally!
2015-06-13 12:08:40 5124 [Note] InnoDB: Starting crash recovery.
2015-06-13 12:08:40 5124 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-06-13 12:08:40 5124 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace healthcompare/wp_commentmeta uses space ID: 11 at filepath: .\healthcompare\wp_commentmeta.ibd. Cannot open tablespace _health/wp_commentmeta which uses space ID: 11 at filepath: .\_healthcompare\wp_commentmeta.ibd
InnoDB: Error: could not open single-table tablespace file .\_health\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.

Thanks,
Nilay

Read he help that is in the error log.

Have you moved something?

Have you deleted something?

Did you read the above link I gave you?



My suggestion is to reload the database from your last backup

---------------------------------------------------------------------------------------------
(Windows 10 Pro 64bit) (Wampserver 3.3.4 64bit) Aestan Tray Menu 3.2.5.4
<Apache versions MULTIPE> <PHP versions MULTIPLE> <MySQL Versions MULTIPLE>
<MariaDB versions MULTIPLE> <phpMyAdmin versions MULTIPLE> <MySQL Workbench 8.0.23>
Read The Manuals Apache -- MySQL -- PHP -- phpMyAdmin
Get your Apache/MySQL/mariaDB/PHP ADDONs here from the WAMPServer alternate Repo
-X-X-X- Backup your databases regularly Here is How dont regret it later! Yes even when developing -X-X-X-

32 bit
Windows Vista

Hello, I've been having the same problem. It worked for years, and then I went to use it the other day, and got the problem with Mysql. I removed and reinstalled wamp yesterday, and it worked the first time out, but today, Mysql won't start again, and the icon is orange. I've scoured the internet and this site looking for solutions and nothing is working. I did not create a backup. Here is my log. Thank you in advance.


2015-06-25 16:52:24 5480 [Note] Plugin 'FEDERATED' is disabled.
2015-06-25 16:52:27 5480 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-06-25 16:52:27 5480 [Note] InnoDB: The InnoDB memory heap is disabled
2015-06-25 16:52:27 5480 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-06-25 16:52:27 5480 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-06-25 16:52:27 5480 [Note] InnoDB: Not using CPU crc32 instructions
2015-06-25 16:52:27 5480 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2015-06-25 16:52:27 5480 [Note] InnoDB: Completed initialization of buffer pool
2015-06-25 16:52:27 5480 [Note] InnoDB: Highest supported file format is Barracuda.
2015-06-25 16:52:28 5480 [Note] InnoDB: 128 rollback segment(s) are active.
2015-06-25 16:52:29 5480 [Note] InnoDB: Waiting for purge to start
2015-06-25 16:52:29 5480 [Note] InnoDB: 5.6.17 started; log sequence number 1625977
2015-06-25 16:52:29 5480 [Warning] No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: 798f9876-1b84-11e5-80f6-001e335b930f.
2015-06-25 16:52:29 5480 [Note] Server hostname (bind-address): '*'; port: 3306
2015-06-25 16:52:29 5480 [Note] IPv6 is available.
2015-06-25 16:52:29 5480 [Note] - '::' resolves to '::';
2015-06-25 16:52:29 5480 [Note] Server socket created on IP: '::'.
2015-06-25 16:52:32 5480 [Note] Event Scheduler: Loaded 0 events
2015-06-25 16:52:32 5480 [Note] wampmysqld: ready for connections.
Version: '5.6.17' socket: '' port: 3306 MySQL Community Server (GPL)
2015-06-25 16:53:21 5480 [Note] wampmysqld: Arrêt normal du serveur

2015-06-25 16:53:21 5480 [Note] Giving 0 client threads a chance to die gracefully
2015-06-25 16:53:21 5480 [Note] Event Scheduler: Purging the queue. 0 events
2015-06-25 16:53:21 5480 [Note] Shutting down slave threads
2015-06-25 16:53:21 5480 [Note] Forcefully disconnecting 0 remaining clients
2015-06-25 16:53:21 5480 [Note] Binlog end
2015-06-25 16:53:21 5480 [Note] Shutting down plugin 'partition'
2015-06-25 16:53:21 5480 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2015-06-25 16:53:21 5480 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2015-06-25 16:53:21 5480 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2015-06-25 16:53:21 5480 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2015-06-25 16:53:21 5480 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2015-06-25 16:53:21 5480 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2015-06-25 16:53:21 5480 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2015-06-25 16:53:21 5480 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2015-06-25 16:53:21 5480 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2015-06-25 16:53:21 5480 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2015-06-25 16:53:21 5480 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2015-06-25 16:53:21 5480 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2015-06-25 16:53:21 5480 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2015-06-25 16:53:21 5480 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2015-06-25 16:53:21 5480 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2015-06-25 16:53:21 5480 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2015-06-25 16:53:21 5480 [Note] Shutting down plugin 'INNODB_METRICS'
2015-06-25 16:53:21 5480 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2015-06-25 16:53:21 5480 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2015-06-25 16:53:21 5480 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2015-06-25 16:53:21 5480 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2015-06-25 16:53:21 5480 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2015-06-25 16:53:21 5480 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2015-06-25 16:53:21 5480 [Note] Shutting down plugin 'INNODB_CMPMEM'
2015-06-25 16:53:21 5480 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2015-06-25 16:53:21 5480 [Note] Shutting down plugin 'INNODB_CMP'
2015-06-25 16:53:21 5480 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2015-06-25 16:53:21 5480 [Note] Shutting down plugin 'INNODB_LOCKS'
2015-06-25 16:53:21 5480 [Note] Shutting down plugin 'INNODB_TRX'
2015-06-25 16:53:21 5480 [Note] Shutting down plugin 'InnoDB'
2015-06-25 16:53:21 5480 [Note] InnoDB: FTS optimize thread exiting.
2015-06-25 16:53:21 5480 [Note] InnoDB: Starting shutdown...
2015-06-25 16:53:22 5480 [Note] InnoDB: Shutdown completed; log sequence number 1625987
2015-06-25 16:53:22 5480 [Note] Shutting down plugin 'BLACKHOLE'
2015-06-25 16:53:22 5480 [Note] Shutting down plugin 'ARCHIVE'
2015-06-25 16:53:22 5480 [Note] Shutting down plugin 'MRG_MYISAM'
2015-06-25 16:53:22 5480 [Note] Shutting down plugin 'MyISAM'
2015-06-25 16:53:22 5480 [Note] Shutting down plugin 'MEMORY'
2015-06-25 16:53:22 5480 [Note] Shutting down plugin 'CSV'
2015-06-25 16:53:22 5480 [Note] Shutting down plugin 'sha256_password'
2015-06-25 16:53:22 5480 [Note] Shutting down plugin 'mysql_old_password'
2015-06-25 16:53:22 5480 [Note] Shutting down plugin 'mysql_native_password'
2015-06-25 16:53:22 5480 [Note] Shutting down plugin 'binlog'
2015-06-25 16:53:22 5480 [Note] wampmysqld: Arrêt du serveur terminé



Edited 1 time(s). Last edit at 06/27/2015 10:01PM by DeeWright.

That looks like a fairly normal startup and shutdown.

Does the Windwos Event Viewer give anything to go on?

---------------------------------------------------------------------------------------------
(Windows 10 Pro 64bit) (Wampserver 3.3.4 64bit) Aestan Tray Menu 3.2.5.4
<Apache versions MULTIPE> <PHP versions MULTIPLE> <MySQL Versions MULTIPLE>
<MariaDB versions MULTIPLE> <phpMyAdmin versions MULTIPLE> <MySQL Workbench 8.0.23>
Read The Manuals Apache -- MySQL -- PHP -- phpMyAdmin
Get your Apache/MySQL/mariaDB/PHP ADDONs here from the WAMPServer alternate Repo
-X-X-X- Backup your databases regularly Here is How dont regret it later! Yes even when developing -X-X-X-

This is what shows in event viewer under Mysql:

1. InnoDB: Doublewrite does not have page_no=0 of space: 0
2. The server service was unable to recreate the share cache2 because the directory C:\wamp\www\wordagaincache no longer exists. Please run "net share cache2 /delete" to delete the share, or recreate the directory C:\wamp\www\wordagain\. (I completely deleted the old installation and version of Wamp which contained this directory - so why is Wamp looking for it now?)
3.TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts.
4. The wampmysqld service terminated unexpectedly. It has done this 3 time(s).
5. Unknown/unsupported storage engine: InnoDB
6. Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
7. Plugin 'InnoDB' init function returned error.
8. InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!
9. InnoDB: space header page consists of zero bytes in data file .\ibdata1 (I did delete this file, but it didn't help)
10. wampmysqld: Arrêt du serveur terminé
11. Shutting down plugin 'binlog'
11. Shutting down plugin 'mysql_native_password' ( I never added a password)
12. Shutting down plugin 'mysql_old_password'
13. Shutting down plugin 'sha256_password'
14. Shutting down plugin 'CSV'
15. Shutting down plugin "MEMORY"

(just a sampling)


Thank you for responding

1. Do you have another instance of MYSQL running on your system?

2. What amendments did you make to MYSQL??
-- as C:\wamp\www\wordagaincache would not notmally be used by a default WAMPServer installation

3. If you dont think you did anything to MYSQL's default config, what software did you install?
-- No guarantee this will mean anything to me/us

---------------------------------------------------------------------------------------------
(Windows 10 Pro 64bit) (Wampserver 3.3.4 64bit) Aestan Tray Menu 3.2.5.4
<Apache versions MULTIPE> <PHP versions MULTIPLE> <MySQL Versions MULTIPLE>
<MariaDB versions MULTIPLE> <phpMyAdmin versions MULTIPLE> <MySQL Workbench 8.0.23>
Read The Manuals Apache -- MySQL -- PHP -- phpMyAdmin
Get your Apache/MySQL/mariaDB/PHP ADDONs here from the WAMPServer alternate Repo
-X-X-X- Backup your databases regularly Here is How dont regret it later! Yes even when developing -X-X-X-

I had an old installation (which still worked), but I uninstalled it and deleted all folders before installing the latest version of Wamp. So the log is actually referring to one of the old files. Not sure why that is happening, because I did a search on all old Wamp files to delete them.

Why would it work and then stop? The only thing I did after installing the new was begin work on a Wordpress theme. All went fine. When I was done, I shut down properly. Then the next day...no Mysql. Do you know if there is some conflict with Wordpress?



Edited 1 time(s). Last edit at 06/29/2015 03:46PM by DeeWright.

Ok

Possibly you followed some bad advice and placed the my.ini or my.cnf file somewhere in a folder on you PATH or you have placed a my.ini or my.cnf in the \Windows\ structurefolder somewhere.

Search for my.ini and if any exist outside the \wamp\bin\mysql\... folder structure delete them.

Check the windows PATH and make sure NO \wamp..... folders are entered on that.

---------------------------------------------------------------------------------------------
(Windows 10 Pro 64bit) (Wampserver 3.3.4 64bit) Aestan Tray Menu 3.2.5.4
<Apache versions MULTIPE> <PHP versions MULTIPLE> <MySQL Versions MULTIPLE>
<MariaDB versions MULTIPLE> <phpMyAdmin versions MULTIPLE> <MySQL Workbench 8.0.23>
Read The Manuals Apache -- MySQL -- PHP -- phpMyAdmin
Get your Apache/MySQL/mariaDB/PHP ADDONs here from the WAMPServer alternate Repo
-X-X-X- Backup your databases regularly Here is How dont regret it later! Yes even when developing -X-X-X-

No, I didn't do any more than what I wrote. However, I will look for the file and delete it to see if that helps.

Thanks