MYSQL failed suddenly in existing WAMP installation
Posted by: rdownes (---.15-3.cable.virginm.net)
Date: November 15, 2014 03:46PM

I allowed a windows update (defender data it appears) and now MYSQL does not work.
I am using Windows 8 64bit, WAMP 2.2 64bit, Apache 2.2.22, PHP 5.4.3, My Sql 5.5.24 all running on localhost for testing and development purposes.
The defender update happened last night and did not affect things, I then allowed the auto reboot this morning and when I restarted WAMP it went to Orange. Looking a the service options I can see that Apache and PHP are running but MYSQL is not and will not start when I manually try to in the Service option.
The message I get with phpmyadmin is:
#2002 - No connection could be made because the target machine actively refused it.

The server is not responding (or the local server's socket is not correctly configured).

The SQL log contains:
141115 10:02:49 [Note] Plugin 'FEDERATED' is disabled.
141115 10:02:49 InnoDB: The InnoDB memory heap is disabled
141115 10:02:49 InnoDB: Mutexes and rw_locks use Windows interlocked functions
141115 10:02:49 InnoDB: Compressed tables use zlib 1.2.3
141115 10:02:49 InnoDB: Initializing buffer pool, size = 384.0M
141115 10:02:49 InnoDB: Completed initialization of buffer pool
141115 10:02:49 InnoDB: Operating system error number 3 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: File name C:\mysql\data\ibdata1
InnoDB: File operation call: 'create'.
InnoDB: Cannot continue operation.

My hosts file is:
127.0.0.1 localhost
127.0.0.1 www.playdrupal.com
127.0.0.1 basingstokeproskills.localhost
My vhosts file is:
<VirtualHost *:80>
DocumentRoot "c:/wamp/www/drupal"
ServerName www.playdrupal.com
ServerAlias playdrupal.com domain
ErrorLog "c:/wamp/www/drupal/logs/playdrupalcom-error.log"
CustomLog "c:/wamp/www/drupal/logs/playdrupal.com-access.log" common
</VirtualHost>

<VirtualHost *:80>
DocumentRoot "c:/wamp/www/drupal"
ServerName basingstokeproskills.localhost
ServerAlias basingstokeproskills.localhost domain
ErrorLog "c:/wamp/www/drupal/logs/basinstokeproskills.localhost-error.log"
CustomLog "c:/wamp/www/drupal/logs/basingstokeproskills.localhost-access.log" common
</VirtualHost>

<VirtualHost *:80>
DocumentRoot "c:/wamp/www"
ServerName localhost
ErrorLog "logs/error.log"
CustomLog "logs/access.log" common
</VirtualHost>

I have checked lots of forums including this one and tried the following to no avail:
Checked port 80 and 3306 and not being used
Tried network reset running CMD as administrator
Looked in Event viewer for MYSQL and Apache events. Found the ‘Plugin FEDERATED is disabled’ note seen in the SQL log and Apache error [warn] NameVirtualHost *:80 has no VirtualHosts but this has always happened and has not caused this issue before.

I looked up FEDERATED in the MySQL site and found that it is for creating local tables that are a mirror of remote tables - this is not something I do and I see that in my.ini I see it is switched off by default so I don't think that is the problem.

Any ideas as I am stuck now and I cannot even backup my databases to rebuild or even switch to using a host. I do have a backup from a while ago but I would rather not revert that far back if I can help it. But also I would like to continue working on localhost so that I do not need internet coverage when working.

Thanks in advance.

Regards
Rory Downes
Web developer new to Drupal but experienced in JavaScript, MYSQL, PHP and WAMP

Options: ReplyQuote
Re: MYSQL failed suddenly in existing WAMP installation
Posted by: RiggsFolly (---.as43234.net)
Date: November 15, 2014 04:57PM

Hi Rory,

This is the line that gives me the most cause for concern!

InnoDB: File name C:\mysql\data\ibdata1


This of course is not where the MySQL should be looking for anything if its a WAMPServer install.



Have you recently installed a stand alone MySQL Server?
Or a product like MySQL Workbench one verison of which comes with its own MySQL Server.


WampServers service name for MySQL is wampmysqld or wampmysqld64. Check to see it you have another MySQL service probably actually called 'MYSQL' if so then you have somehow installed another instalnce of a MySQL Server.

---------------------------------------------------------------------------------------------
(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-

Options: ReplyQuote
Re: MYSQL failed suddenly in existing WAMP installation
Posted by: rdownes (---.15-3.cable.virginm.net)
Date: November 15, 2014 05:16PM

Hi RiggsFolly,
Thanks for your prompt response.

I have not intentionally installed another MySQL or Workbench, indeed I have not done any installations recently (other than Drupal modules). I did check the services list and the only SQL service is wampmysqld - next to wampapache.

I also checked for this folder on my hard drive and the MySQL folder does not exist at the C root.

Any further ways of making sure of this or any further ideas as to why it is looking in the wrong place? Perhaps there is a config file pointing in the wrong place for some reason.

Ta
Rory

Regards
Rory Downes
Web developer new to Drupal but experienced in JavaScript, MYSQL, PHP and WAMP

Options: ReplyQuote
Re: MYSQL failed suddenly in existing WAMP installation
Posted by: rdownes (---.15-3.cable.virginm.net)
Date: November 15, 2014 05:36PM

I attempted to answer my own question. I looked in my.ini and did find the offending folder in the InnoDB section. I changed it to:
C:\wamp\bin\mysql\mysql5.5.24\data
This did not solve the problem, even with a full restart of WAMP. However the log file is different:
141115 16:21:57 [Note] Plugin 'FEDERATED' is disabled.
141115 16:21:57 InnoDB: The InnoDB memory heap is disabled
141115 16:21:57 InnoDB: Mutexes and rw_locks use Windows interlocked functions
141115 16:21:57 InnoDB: Compressed tables use zlib 1.2.3
141115 16:21:57 InnoDB: Initializing buffer pool, size = 384.0M
141115 16:21:57 InnoDB: Completed initialization of buffer pool
141115 16:21:57 InnoDB: Operating system error number 123 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: [dev.mysql.com]
InnoDB: File name C:\wampin\mysql\mysql5.5.24\data\ibdata1
InnoDB: File operation call: 'create'.
InnoDB: Cannot continue operation.

I don't understand why the log has the wrong folder name. The direct copy of the section of my.ini is:
innodb_data_home_dir = C:\wamp\bin\mysql\mysql5.5.24\data/
innodb_data_file_path = ibdata1:10M:autoextend
innodb_log_group_home_dir = C:\wamp\bin\mysql\mysql5.5.24\data/
innodb_log_arch_dir = C:\wamp\bin\mysql\mysql5.5.24\data/


I did also look for multiple my.ini files. I did find two, each in a failed attempt to install WAMP from years ago when I first installed it. In both cases the InnoDB section was uncommented as I have only recently used InnoDB because Drupal uses it.
Anything else I should look for or do?
Ta Rory

Regards
Rory Downes
Web developer new to Drupal but experienced in JavaScript, MYSQL, PHP and WAMP

Options: ReplyQuote
Re: MYSQL failed suddenly in existing WAMP installation
Posted by: RiggsFolly (---.as43234.net)
Date: November 15, 2014 05:52PM

Ok, so search your C drive for these 2 files 'my.ini' and 'my.cnf'

They should only exist in the \wamp\.... folder structure.

If you find any anywhere else, delete them.

---------------------------------------------------------------------------------------------
(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-

Options: ReplyQuote
Re: MYSQL failed suddenly in existing WAMP installation
Posted by: RiggsFolly (---.as43234.net)
Date: November 15, 2014 06:00PM

Ahhhhhh,


Sometimes you cannot see the wood for the tree's


These lines are wrong !!


innodb_data_home_dir = C:\wamp\bin\mysql\mysql5.5.24\data/
innodb_log_group_home_dir = C:\wamp\bin\mysql\mysql5.5.24\data/
innodb_log_arch_dir = C:\wamp\bin\mysql\mysql5.5.24\data/


Dont us the DOS backslash, use the UNIX forward slash

So it should be

innodb_data_home_dir = C:/wamp/bin/mysql/mysql5.5.24/data/
innodb_log_group_home_dir = C:/wamp/bin/mysql/mysql5.5.24/data/
innodb_log_arch_dir = C:/wamp/bin/mysql/mysql5.5.24/data/


You had better check all the directory seperators that yo may have edited in my.ini

---------------------------------------------------------------------------------------------
(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-



Edited 1 time(s). Last edit at 11/15/2014 06:01PM by RiggsFolly.

Options: ReplyQuote
Re: MYSQL failed suddenly in existing WAMP installation
Posted by: rdownes (---.15-3.cable.virginm.net)
Date: November 15, 2014 08:34PM

Wow thanks RiggsFolly. That almost did it. It then said that the log file was not the same file as defined, which meant changing the innodb_log_file_size, but it also said that innodb_log_arch_dir was an unrecognised parameter so I commented it out and it finally worked!

Thanks for your help. I am now back in action!

Regards
Rory

Regards
Rory Downes
Web developer new to Drupal but experienced in JavaScript, MYSQL, PHP and WAMP

Options: ReplyQuote


Sorry, only registered users may post in this forum.