Bug #6780 | Configuration Wizard 1.0.1 fails when service is blocked by firewall | ||
---|---|---|---|
Submitted: | 23 Nov 2004 20:51 | Modified: | 29 Nov 2004 20:39 |
Reporter: | Olaf van Zandwijk | Email Updates: | |
Status: | Won't fix | Impact on me: | |
Category: | MySQL Server: Installing | Severity: | S3 (Non-critical) |
Version: | 4.1.7 | OS: | Windows (WindowsXP) |
Assigned to: | Michael G. Zinner | CPU Architecture: | Any |
[23 Nov 2004 20:51]
Olaf van Zandwijk
[29 Nov 2004 20:39]
Michael G. Zinner
Thanks for reporting. There are several issues that occure if you select to block the MySQL server port on your local machine. The best solution is, to simply run the Configuration Wizard again and select to remove the service. A fresh install is not needed. When the Windows service is removed by the Configuration Wizard and then re-installed, this should trigger your personal firewall to ask again whether the port should be blocked or not. The reason why we cannot remove the data directory on an de-installation is, that we need to keep the data for an upgrade. This is also where your root password is stored. Please note that the Configuration Wizard is not a part of the MSI installation process. It is just a tool that can be used to configure the server. You can execute it as many times you like via the Windows Start Menu. When the Configuration Wizard is executed once, the old password has to be entered again, or the configuration will fail since the login data is incorrect. This is also true if you de-install the server via the Setup program - due to the face again, that the "data" is kept. I hope this helps to avoid issues with personal firewalls in the future.
[30 Nov 2004 8:44]
Olaf van Zandwijk
Thanks for the reply, A removal of the service and re-install through the configuration wizard, does not fix the issue. The service still won't start, even with the port already open. I would not have reported this bug if that worked.
[4 Dec 2004 22:56]
Max Hearn
I can confirm that this problem exists as reported. In my case, I had ZoneAlarm on my system. At the end of the configuration process, ZoneAlarm posted a warning after the service was started. I clicked "Allow" to allow the connection to occur, but the brief delay was enough to cause the installation script to fail before setting the security settings. At that point, everything I saw was exactly as Olaf described the problem. Removing and reinstalling didn't fix the problem. But removing, manually deleting the directories, and reinstalling did. So, I'd say there are two bugs here: 1) The installation should not have failed in the first place. The connection wasn't blocked, just delayed by a few seconds. 2) After the problem occurs, the removal process does not remove enough for a reinstall to work.