WampServer
Apache, PHP, MySQL
on Windows
WAMP 2.5 suddenly became Orange and MYSQL wont start
Posted by:
benia
(---.red.bezeqint.net)
Date: November 22, 2015 08:48AM
Here is a stepped description of the prob, thanks in advance!:
--- Background ---
I use Windows 10 home & WAMP server 2.5 that until the last week worked just fine.
At start, I thought WAMP orangized because of an Apache problem, so I have tested port 80 and vindicated that indeed, Apache uses this port. I also totally closed skype and restarted all services. My port 80 is used by Apache and the problem is NOT Apache or Skype or IIS related for 100%.
--- The problem ---
Suddenly WAMP has became Orange. Until last week it was Green. I don't recall making changes to any files whatsoever, but I know have a trace to solve this problem: The Direction is surly mySQL.
All the sites are off, showing a mySQL error 2002. While further checking this, I opened Windows Powershell (Windows CMD) as an administrator and ran netstat -a -b. This command shows that the mySQL port 3306 isn't used, so it seems that something stands between WAMP and this port, and prevents WAMP of using it.
Edited 1 time(s). Last edit at 11/22/2015 10:02AM by benia.
--- Background ---
I use Windows 10 home & WAMP server 2.5 that until the last week worked just fine.
At start, I thought WAMP orangized because of an Apache problem, so I have tested port 80 and vindicated that indeed, Apache uses this port. I also totally closed skype and restarted all services. My port 80 is used by Apache and the problem is NOT Apache or Skype or IIS related for 100%.
--- The problem ---
Suddenly WAMP has became Orange. Until last week it was Green. I don't recall making changes to any files whatsoever, but I know have a trace to solve this problem: The Direction is surly mySQL.
All the sites are off, showing a mySQL error 2002. While further checking this, I opened Windows Powershell (Windows CMD) as an administrator and ran netstat -a -b. This command shows that the mySQL port 3306 isn't used, so it seems that something stands between WAMP and this port, and prevents WAMP of using it.
Edited 1 time(s). Last edit at 11/22/2015 10:02AM by benia.
Re: WAMP 2.5 suddenly became Orange and MYSQL wont start
Posted by:
Otomatic
(Moderator)
Date: November 22, 2015 09:42AM
Hi,
Read TROUBLESHOOTING TIPS
---------------------------------------------------------------
Documentation Apache - Documentation PHP - Documentation MySQL - Wampserver install files & addons
Read TROUBLESHOOTING TIPS
---------------------------------------------------------------
Documentation Apache - Documentation PHP - Documentation MySQL - Wampserver install files & addons
Re: WAMP 2.5 suddenly became Orange and MYSQL wont start
Posted by:
benia
(---.red.bezeqint.net)
Date: November 22, 2015 10:22AM
While reading this page I noticed the suggestion of checking the log. Well, I checked at C:\ > Wamp > Logs > mysql.log, and when I opened the file it was totally empty --- Like something has deleted all it's content.
I must say I haven't installed any software in the last week and generally I'm the only human who uses my PC, so I've no idea why would that happen.
I have detailed my question very much and already tried some reasonable things; Please help,
I must say I haven't installed any software in the last week and generally I'm the only human who uses my PC, so I've no idea why would that happen.
I have detailed my question very much and already tried some reasonable things; Please help,
Re: WAMP 2.5 suddenly became Orange and MYSQL wont start
Posted by:
Otomatic
(Moderator)
Date: November 22, 2015 11:02AM
Hi,
In the services manager (Run, Execute, services.msc), in the Properties for wampmysqld service try to start it, then see what error is.
---------------------------------------------------------------
Documentation Apache - Documentation PHP - Documentation MySQL - Wampserver install files & addons
In the services manager (Run, Execute, services.msc), in the Properties for wampmysqld service try to start it, then see what error is.
---------------------------------------------------------------
Documentation Apache - Documentation PHP - Documentation MySQL - Wampserver install files & addons
Re: WAMP 2.5 suddenly became Orange and MYSQL wont start
Posted by:
benia
(---.red.bezeqint.net)
Date: November 22, 2015 01:16PM
services manager (Run, Execute, services.msc)?
Properties for wampmysqld service?
I couldn't find it when left\right clicked that Orange icon?...
Properties for wampmysqld service?
I couldn't find it when left\right clicked that Orange icon?...
Re: WAMP 2.5 suddenly became Orange and MYSQL wont start
Posted by:
Otomatic
(Moderator)
Date: November 22, 2015 02:51PM
Hi,
It is for Windows, not Wampserver icon.
Re-read TROUBLESHOOTING TIPS
---------------------------------------------------------------
Documentation Apache - Documentation PHP - Documentation MySQL - Wampserver install files & addons
It is for Windows, not Wampserver icon.
Re-read TROUBLESHOOTING TIPS
---------------------------------------------------------------
Documentation Apache - Documentation PHP - Documentation MySQL - Wampserver install files & addons
Re: WAMP 2.5 suddenly became Orange and MYSQL wont start
Posted by:
benia
(---.red.bezeqint.net)
Date: November 23, 2015 04:38AM
Hey man: I went to msconfig > services > wampmysqld64 and it was unchecked and it's status was "Stopped", so I check-marked it and restarted all services. The WAMP icon then became Red instead of Orange and the service status was still "Stopped".
Then I restarted my computer and started WAMP --- Again, it was red instead of Orange, and the service status was still "Stopped".
The log is still empty btw.
Thus, I am still stuck with this. Any further idea? Please help,
Edited 1 time(s). Last edit at 11/23/2015 05:44AM by benia.
Then I restarted my computer and started WAMP --- Again, it was red instead of Orange, and the service status was still "Stopped".
The log is still empty btw.
Thus, I am still stuck with this. Any further idea? Please help,
Edited 1 time(s). Last edit at 11/23/2015 05:44AM by benia.
Re: WAMP 2.5 suddenly became Orange and MYSQL wont start
Posted by:
Otomatic
(Moderator)
Date: November 23, 2015 09:47AM
Hi,
When you START manually wampmysqld64 in the services manager, what is the error?
WAMPServer 2.5 64bit MYSQL ONLY
The my.in file contains a woops!
Edit the my.ini file using the wampmanager menus (wampmanager->MySQL->my.ini)
Locate this section header
---------------------------------------------------------------
Documentation Apache - Documentation PHP - Documentation MySQL - Wampserver install files & addons
When you START manually wampmysqld64 in the services manager, what is the error?
WAMPServer 2.5 64bit MYSQL ONLY
The my.in file contains a woops!
Edit the my.ini file using the wampmanager menus (wampmanager->MySQL->my.ini)
Locate this section header
[wampmysqld]and change it to
[wampmysqld64]
---------------------------------------------------------------
Documentation Apache - Documentation PHP - Documentation MySQL - Wampserver install files & addons
Re: WAMP 2.5 suddenly became Orange and MYSQL wont start
Posted by:
benia
(---.red.bezeqint.net)
Date: November 23, 2015 01:16PM
Things I tried:
1. I went to my.ini and changed as you suggested. I saved and RAS. It was still Red, so I right-clicked on the WAMP icon and clicked refresh and than RAS - also didn't help.
2. I went to services and unchecked the service (as was in the start), applied, and saved. Then, considering that my.ini was still changed, I just RAS. It was still red, so I right-clicked on the WAMP icon and clicked refresh and than RAS - also didn't help.
3. Restarting the comp in that situation (service disabled), refreshing WAMP, and then RAS. Was still red.
4. Disabling the service, applying and saving, and then right click on the WAMP icon and refreshing it, and also RAS after refresh. Was still red.
5. Restarting the comp in that situation (service enabled),refreshing WAMP, and then RAS. Was still red.
---
I DO SHOULD MENTION!
Now, the mySQL.log file does contain data. Maybe it's due to the enabling of the service (which I've by now disabled). It seems I can't attach the mySQL.log file here, so I uploaded it to an external server, and you can download it from here:
[www.filedropper.com]
1. I went to my.ini and changed as you suggested. I saved and RAS. It was still Red, so I right-clicked on the WAMP icon and clicked refresh and than RAS - also didn't help.
2. I went to services and unchecked the service (as was in the start), applied, and saved. Then, considering that my.ini was still changed, I just RAS. It was still red, so I right-clicked on the WAMP icon and clicked refresh and than RAS - also didn't help.
3. Restarting the comp in that situation (service disabled), refreshing WAMP, and then RAS. Was still red.
4. Disabling the service, applying and saving, and then right click on the WAMP icon and refreshing it, and also RAS after refresh. Was still red.
5. Restarting the comp in that situation (service enabled),refreshing WAMP, and then RAS. Was still red.
---
I DO SHOULD MENTION!
Now, the mySQL.log file does contain data. Maybe it's due to the enabling of the service (which I've by now disabled). It seems I can't attach the mySQL.log file here, so I uploaded it to an external server, and you can download it from here:
[www.filedropper.com]
Re: WAMP 2.5 suddenly became Orange and MYSQL wont start
Posted by:
Otomatic
(Moderator)
Date: November 23, 2015 02:54PM
Hi,
I will not download a file.
It's still easy to put in your message errors, and only those, by copy / paste.
That's twice I ask you to give the error message that occurs when you want to start the service wampmysqld64 in the Services Manager.
I do not ask you to write a novel about what you do, but to respond to what I ask.
---------------------------------------------------------------
Documentation Apache - Documentation PHP - Documentation MySQL - Wampserver install files & addons
I will not download a file.
It's still easy to put in your message errors, and only those, by copy / paste.
That's twice I ask you to give the error message that occurs when you want to start the service wampmysqld64 in the Services Manager.
I do not ask you to write a novel about what you do, but to respond to what I ask.
---------------------------------------------------------------
Documentation Apache - Documentation PHP - Documentation MySQL - Wampserver install files & addons
Re: WAMP 2.5 suddenly became Orange and MYSQL wont start
Posted by:
benia
(---.red.bezeqint.net)
Date: November 23, 2015 03:00PM
Indeed I have no intention of writing a novel:
I couldn't understand your question --- I have no error when I double click on this service called "wampmysqld64". Surly there's also no such task at the task manager.
I didn't know if it's Okay to paste here so much text, but here it is - The whole text of my mySQL.log file:
2015-11-23 13:36:07 4516 [Note] Plugin 'FEDERATED' is disabled.
2015-11-23 13:36:07 4516 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-11-23 13:36:07 4516 [Note] InnoDB: The InnoDB memory heap is disabled
2015-11-23 13:36:07 4516 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-11-23 13:36:07 4516 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-11-23 13:36:07 4516 [Note] InnoDB: Not using CPU crc32 instructions
2015-11-23 13:36:07 4516 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2015-11-23 13:36:07 4516 [Note] InnoDB: Completed initialization of buffer pool
2015-11-23 13:36:07 4516 [Note] InnoDB: Highest supported file format is Barracuda.
2015-11-23 13:36:07 4516 [Note] InnoDB: The log sequence numbers 152480527 and 152480527 in ibdata files do not match the log sequence number 307126539 in the ib_logfiles!
2015-11-23 13:36:07 4516 [Note] InnoDB: Database was not shutdown normally!
2015-11-23 13:36:07 4516 [Note] InnoDB: Starting crash recovery.
2015-11-23 13:36:07 4516 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-11-23 13:36:07 4516 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace manyouareking/menu_custom uses space ID: 301 at filepath: .\manyouareking\menu_custom.ibd. Cannot open tablespace pan/actions which uses space ID: 301 at filepath: .\pan\actions.ibd
InnoDB: Error: could not open single-table tablespace file .\pan\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.
2015-11-23 13:45:56 4488 [Note] Plugin 'FEDERATED' is disabled.
2015-11-23 13:45:56 4488 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-11-23 13:45:56 4488 [Note] InnoDB: The InnoDB memory heap is disabled
2015-11-23 13:45:56 4488 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-11-23 13:45:56 4488 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-11-23 13:45:56 4488 [Note] InnoDB: Not using CPU crc32 instructions
2015-11-23 13:45:56 4488 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2015-11-23 13:45:56 4488 [Note] InnoDB: Completed initialization of buffer pool
2015-11-23 13:45:56 4488 [Note] InnoDB: Highest supported file format is Barracuda.
2015-11-23 13:45:56 4488 [Note] InnoDB: The log sequence numbers 152480527 and 152480527 in ibdata files do not match the log sequence number 307126539 in the ib_logfiles!
2015-11-23 13:45:56 4488 [Note] InnoDB: Database was not shutdown normally!
2015-11-23 13:45:56 4488 [Note] InnoDB: Starting crash recovery.
2015-11-23 13:45:56 4488 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-11-23 13:45:56 4488 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace manyouareking/menu_custom uses space ID: 301 at filepath: .\manyouareking\menu_custom.ibd. Cannot open tablespace pan/actions which uses space ID: 301 at filepath: .\pan\actions.ibd
InnoDB: Error: could not open single-table tablespace file .\pan\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.
2015-11-23 13:46:38 6132 [Note] Plugin 'FEDERATED' is disabled.
2015-11-23 13:46:38 6132 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-11-23 13:46:38 6132 [Note] InnoDB: The InnoDB memory heap is disabled
2015-11-23 13:46:38 6132 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-11-23 13:46:38 6132 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-11-23 13:46:38 6132 [Note] InnoDB: Not using CPU crc32 instructions
2015-11-23 13:46:38 6132 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2015-11-23 13:46:38 6132 [Note] InnoDB: Completed initialization of buffer pool
2015-11-23 13:46:39 6132 [Note] InnoDB: Highest supported file format is Barracuda.
2015-11-23 13:46:39 6132 [Note] InnoDB: The log sequence numbers 152480527 and 152480527 in ibdata files do not match the log sequence number 307126539 in the ib_logfiles!
2015-11-23 13:46:39 6132 [Note] InnoDB: Database was not shutdown normally!
2015-11-23 13:46:39 6132 [Note] InnoDB: Starting crash recovery.
2015-11-23 13:46:39 6132 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-11-23 13:46:39 6132 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace manyouareking/menu_custom uses space ID: 301 at filepath: .\manyouareking\menu_custom.ibd. Cannot open tablespace pan/actions which uses space ID: 301 at filepath: .\pan\actions.ibd
InnoDB: Error: could not open single-table tablespace file .\pan\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.
2015-11-23 14:01:05 5408 [Note] Plugin 'FEDERATED' is disabled.
2015-11-23 14:01:05 5408 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-11-23 14:01:05 5408 [Note] InnoDB: The InnoDB memory heap is disabled
2015-11-23 14:01:05 5408 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-11-23 14:01:05 5408 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-11-23 14:01:05 5408 [Note] InnoDB: Not using CPU crc32 instructions
2015-11-23 14:01:05 5408 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2015-11-23 14:01:05 5408 [Note] InnoDB: Completed initialization of buffer pool
2015-11-23 14:01:05 5408 [Note] InnoDB: Highest supported file format is Barracuda.
2015-11-23 14:01:05 5408 [Note] InnoDB: The log sequence numbers 152480527 and 152480527 in ibdata files do not match the log sequence number 307126539 in the ib_logfiles!
2015-11-23 14:01:05 5408 [Note] InnoDB: Database was not shutdown normally!
2015-11-23 14:01:05 5408 [Note] InnoDB: Starting crash recovery.
2015-11-23 14:01:05 5408 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-11-23 14:01:09 5408 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace manyouareking/menu_custom uses space ID: 301 at filepath: .\manyouareking\menu_custom.ibd. Cannot open tablespace pan/actions which uses space ID: 301 at filepath: .\pan\actions.ibd
InnoDB: Error: could not open single-table tablespace file .\pan\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.
2015-11-23 14:02:09 7692 [Note] Plugin 'FEDERATED' is disabled.
2015-11-23 14:02:09 7692 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-11-23 14:02:09 7692 [Note] InnoDB: The InnoDB memory heap is disabled
2015-11-23 14:02:09 7692 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-11-23 14:02:09 7692 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-11-23 14:02:09 7692 [Note] InnoDB: Not using CPU crc32 instructions
2015-11-23 14:02:09 7692 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2015-11-23 14:02:09 7692 [Note] InnoDB: Completed initialization of buffer pool
2015-11-23 14:02:09 7692 [Note] InnoDB: Highest supported file format is Barracuda.
2015-11-23 14:02:09 7692 [Note] InnoDB: The log sequence numbers 152480527 and 152480527 in ibdata files do not match the log sequence number 307126539 in the ib_logfiles!
2015-11-23 14:02:09 7692 [Note] InnoDB: Database was not shutdown normally!
2015-11-23 14:02:09 7692 [Note] InnoDB: Starting crash recovery.
2015-11-23 14:02:09 7692 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-11-23 14:02:09 7692 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace manyouareking/menu_custom uses space ID: 301 at filepath: .\manyouareking\menu_custom.ibd. Cannot open tablespace pan/actions which uses space ID: 301 at filepath: .\pan\actions.ibd
InnoDB: Error: could not open single-table tablespace file .\pan\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 couldn't understand your question --- I have no error when I double click on this service called "wampmysqld64". Surly there's also no such task at the task manager.
I didn't know if it's Okay to paste here so much text, but here it is - The whole text of my mySQL.log file:
2015-11-23 13:36:07 4516 [Note] Plugin 'FEDERATED' is disabled.
2015-11-23 13:36:07 4516 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-11-23 13:36:07 4516 [Note] InnoDB: The InnoDB memory heap is disabled
2015-11-23 13:36:07 4516 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-11-23 13:36:07 4516 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-11-23 13:36:07 4516 [Note] InnoDB: Not using CPU crc32 instructions
2015-11-23 13:36:07 4516 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2015-11-23 13:36:07 4516 [Note] InnoDB: Completed initialization of buffer pool
2015-11-23 13:36:07 4516 [Note] InnoDB: Highest supported file format is Barracuda.
2015-11-23 13:36:07 4516 [Note] InnoDB: The log sequence numbers 152480527 and 152480527 in ibdata files do not match the log sequence number 307126539 in the ib_logfiles!
2015-11-23 13:36:07 4516 [Note] InnoDB: Database was not shutdown normally!
2015-11-23 13:36:07 4516 [Note] InnoDB: Starting crash recovery.
2015-11-23 13:36:07 4516 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-11-23 13:36:07 4516 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace manyouareking/menu_custom uses space ID: 301 at filepath: .\manyouareking\menu_custom.ibd. Cannot open tablespace pan/actions which uses space ID: 301 at filepath: .\pan\actions.ibd
InnoDB: Error: could not open single-table tablespace file .\pan\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.
2015-11-23 13:45:56 4488 [Note] Plugin 'FEDERATED' is disabled.
2015-11-23 13:45:56 4488 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-11-23 13:45:56 4488 [Note] InnoDB: The InnoDB memory heap is disabled
2015-11-23 13:45:56 4488 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-11-23 13:45:56 4488 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-11-23 13:45:56 4488 [Note] InnoDB: Not using CPU crc32 instructions
2015-11-23 13:45:56 4488 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2015-11-23 13:45:56 4488 [Note] InnoDB: Completed initialization of buffer pool
2015-11-23 13:45:56 4488 [Note] InnoDB: Highest supported file format is Barracuda.
2015-11-23 13:45:56 4488 [Note] InnoDB: The log sequence numbers 152480527 and 152480527 in ibdata files do not match the log sequence number 307126539 in the ib_logfiles!
2015-11-23 13:45:56 4488 [Note] InnoDB: Database was not shutdown normally!
2015-11-23 13:45:56 4488 [Note] InnoDB: Starting crash recovery.
2015-11-23 13:45:56 4488 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-11-23 13:45:56 4488 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace manyouareking/menu_custom uses space ID: 301 at filepath: .\manyouareking\menu_custom.ibd. Cannot open tablespace pan/actions which uses space ID: 301 at filepath: .\pan\actions.ibd
InnoDB: Error: could not open single-table tablespace file .\pan\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.
2015-11-23 13:46:38 6132 [Note] Plugin 'FEDERATED' is disabled.
2015-11-23 13:46:38 6132 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-11-23 13:46:38 6132 [Note] InnoDB: The InnoDB memory heap is disabled
2015-11-23 13:46:38 6132 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-11-23 13:46:38 6132 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-11-23 13:46:38 6132 [Note] InnoDB: Not using CPU crc32 instructions
2015-11-23 13:46:38 6132 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2015-11-23 13:46:38 6132 [Note] InnoDB: Completed initialization of buffer pool
2015-11-23 13:46:39 6132 [Note] InnoDB: Highest supported file format is Barracuda.
2015-11-23 13:46:39 6132 [Note] InnoDB: The log sequence numbers 152480527 and 152480527 in ibdata files do not match the log sequence number 307126539 in the ib_logfiles!
2015-11-23 13:46:39 6132 [Note] InnoDB: Database was not shutdown normally!
2015-11-23 13:46:39 6132 [Note] InnoDB: Starting crash recovery.
2015-11-23 13:46:39 6132 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-11-23 13:46:39 6132 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace manyouareking/menu_custom uses space ID: 301 at filepath: .\manyouareking\menu_custom.ibd. Cannot open tablespace pan/actions which uses space ID: 301 at filepath: .\pan\actions.ibd
InnoDB: Error: could not open single-table tablespace file .\pan\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.
2015-11-23 14:01:05 5408 [Note] Plugin 'FEDERATED' is disabled.
2015-11-23 14:01:05 5408 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-11-23 14:01:05 5408 [Note] InnoDB: The InnoDB memory heap is disabled
2015-11-23 14:01:05 5408 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-11-23 14:01:05 5408 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-11-23 14:01:05 5408 [Note] InnoDB: Not using CPU crc32 instructions
2015-11-23 14:01:05 5408 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2015-11-23 14:01:05 5408 [Note] InnoDB: Completed initialization of buffer pool
2015-11-23 14:01:05 5408 [Note] InnoDB: Highest supported file format is Barracuda.
2015-11-23 14:01:05 5408 [Note] InnoDB: The log sequence numbers 152480527 and 152480527 in ibdata files do not match the log sequence number 307126539 in the ib_logfiles!
2015-11-23 14:01:05 5408 [Note] InnoDB: Database was not shutdown normally!
2015-11-23 14:01:05 5408 [Note] InnoDB: Starting crash recovery.
2015-11-23 14:01:05 5408 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-11-23 14:01:09 5408 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace manyouareking/menu_custom uses space ID: 301 at filepath: .\manyouareking\menu_custom.ibd. Cannot open tablespace pan/actions which uses space ID: 301 at filepath: .\pan\actions.ibd
InnoDB: Error: could not open single-table tablespace file .\pan\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.
2015-11-23 14:02:09 7692 [Note] Plugin 'FEDERATED' is disabled.
2015-11-23 14:02:09 7692 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-11-23 14:02:09 7692 [Note] InnoDB: The InnoDB memory heap is disabled
2015-11-23 14:02:09 7692 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-11-23 14:02:09 7692 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-11-23 14:02:09 7692 [Note] InnoDB: Not using CPU crc32 instructions
2015-11-23 14:02:09 7692 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2015-11-23 14:02:09 7692 [Note] InnoDB: Completed initialization of buffer pool
2015-11-23 14:02:09 7692 [Note] InnoDB: Highest supported file format is Barracuda.
2015-11-23 14:02:09 7692 [Note] InnoDB: The log sequence numbers 152480527 and 152480527 in ibdata files do not match the log sequence number 307126539 in the ib_logfiles!
2015-11-23 14:02:09 7692 [Note] InnoDB: Database was not shutdown normally!
2015-11-23 14:02:09 7692 [Note] InnoDB: Starting crash recovery.
2015-11-23 14:02:09 7692 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-11-23 14:02:09 7692 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace manyouareking/menu_custom uses space ID: 301 at filepath: .\manyouareking\menu_custom.ibd. Cannot open tablespace pan/actions which uses space ID: 301 at filepath: .\pan\actions.ibd
InnoDB: Error: could not open single-table tablespace file .\pan\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.
Re: WAMP 2.5 suddenly became Orange and MYSQL wont start
Posted by:
Otomatic
(Moderator)
Date: November 23, 2015 03:46PM
Hi,
Your database is corrupted.
You have to do waht it is explained in log file :
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.
Or go to MySQL documentation and see how to recover InnoDB database.
---------------------------------------------------------------
Documentation Apache - Documentation PHP - Documentation MySQL - Wampserver install files & addons
Your database is corrupted.
You have to do waht it is explained in log file :
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.
Or go to MySQL documentation and see how to recover InnoDB database.
---------------------------------------------------------------
Documentation Apache - Documentation PHP - Documentation MySQL - Wampserver install files & addons
Re: WAMP 2.5 suddenly became Orange and MYSQL wont start
Posted by:
benia
(---.red.bezeqint.net)
Date: November 23, 2015 03:52PM
One small question just to make sure I understand you right: When you say that my DB is corrupted I guess you don't talk on a specific site I store at the WAMP localhost but on somekind of an external DB that mySQL itself uses which is called InnoDB?
Thanks,
Thanks,
Re: WAMP 2.5 suddenly became Orange and MYSQL wont start
Posted by:
Otomatic
(Moderator)
Date: November 23, 2015 04:04PM
Hi,
The error log speaks about:
Attempted to open a previously opened tablespace. Previous tablespace manyouareking/menu_custom uses space ID: 301 at filepath: .\manyouareking\menu_custom.ibd. Cannot open tablespace pan/actions which uses space ID: 301 at filepath: .\pan\actions.ibd
InnoDB: Error: could not open single-table tablespace file .\pan\actions.ibd
Tables manyouareking/menu_custom is not a MySQL table. MySQL itself don't use InnoDB but only MyISAM.
---------------------------------------------------------------
Documentation Apache - Documentation PHP - Documentation MySQL - Wampserver install files & addons
The error log speaks about:
Attempted to open a previously opened tablespace. Previous tablespace manyouareking/menu_custom uses space ID: 301 at filepath: .\manyouareking\menu_custom.ibd. Cannot open tablespace pan/actions which uses space ID: 301 at filepath: .\pan\actions.ibd
InnoDB: Error: could not open single-table tablespace file .\pan\actions.ibd
Tables manyouareking/menu_custom is not a MySQL table. MySQL itself don't use InnoDB but only MyISAM.
---------------------------------------------------------------
Documentation Apache - Documentation PHP - Documentation MySQL - Wampserver install files & addons
Re: WAMP 2.5 suddenly became Orange and MYSQL wont start
Posted by:
benia
(---.red.bezeqint.net)
Date: November 23, 2015 04:53PM
As you can tell I'm not an SQL programmer. I lost you here --- I don't understand if the problem comes from a specific DB or is something general?
Can you please suggest me what to me manually via Windows\notepad++ ?
Edited 1 time(s). Last edit at 11/23/2015 05:21PM by benia.
Can you please suggest me what to me manually via Windows\notepad++ ?
Edited 1 time(s). Last edit at 11/23/2015 05:21PM by benia.
Re: WAMP 2.5 suddenly became Orange and MYSQL wont start
Posted by:
Otomatic
(Moderator)
Date: November 23, 2015 05:57PM
Hi,
Quit Wampserver
it would be nice to delete the contents of the mysql log file (wamp/logs/ mysql.log) to see, each time you start mysql if the errors are changing.
With Notepad++ edit the file wamp/bin/mysql/mysql5.6.12/my.ini
Just under the section [wampmysqld64] add :
Start Wampserver and wait a moment then see mysql.log for error.
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, but don't use more than 4. 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.
---------------------------------------------------------------
Documentation Apache - Documentation PHP - Documentation MySQL - Wampserver install files & addons
Quit Wampserver
it would be nice to delete the contents of the mysql log file (wamp/logs/ mysql.log) to see, each time you start mysql if the errors are changing.
With Notepad++ edit the file wamp/bin/mysql/mysql5.6.12/my.ini
Just under the section [wampmysqld64] add :
[wampmysqld64] innodb_force_recovery = 1Save the file.
Start Wampserver and wait a moment then see mysql.log for error.
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, but don't use more than 4. 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.
---------------------------------------------------------------
Documentation Apache - Documentation PHP - Documentation MySQL - Wampserver install files & addons
Sorry, only registered users may post in this forum.
