| Bug #60518 | On reinstal of MySql 5.5.1, conf wizard fails to start service and gets stuck | ||
|---|---|---|---|
| Submitted: | 17 Mar 2011 17:28 | Modified: | 31 Mar 2014 8:50 |
| Reporter: | masi pay | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Config Wizard | Severity: | S2 (Serious) |
| Version: | 5.5.10 | OS: | Windows (Vista) |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | config wizard fails to complete, reinstall problem | ||
[17 Mar 2011 17:28]
masi pay
[17 Mar 2011 17:45]
MySQL Verification Team
Thank you for the bug report. Could you please provide the *.err file (look for it in the datadir directory). Thanks in advance.
[17 Mar 2011 21:25]
masi pay
Thanks for prompt reply. I can't find *.err file. After incomplete reinstall>> C:\MySQL Datafiles\ includes one file "ibdata1" size:10,240KB (on opening in text editor the file looks blank however) C:\Program Files\MySQL\MySQL Server 5.5\data\ :: mysql\ performance_schema\ test\ All three folders contain no file with extension .err Thanks
[17 Mar 2011 21:43]
masi pay
By checking on Windows Event Viewer on MySQL errors following was found. however, errors created on different incomplete reinstalls looked different. Following are 2 such errors. ------------------------------------------ Log Name: Application Source: MySQL Date: 3/17/2011 3:25:34 PM Event ID: 100 Task Category: None Level: Error Keywords: Classic User: N/A Computer: masi-PC Description: Plugin 'InnoDB' registration as a STORAGE ENGINE failed. <<-------------------- For more information, see Help and Support Center at http://www.mysql.com. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="MySQL" /> <EventID Qualifiers="49152">100</EventID> <Level>2</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2011-03-17T22:25:34.000Z" /> <EventRecordID>2606</EventRecordID> <Channel>Application</Channel> <Computer>bale-PC</Computer> <Security /> </System> <EventData> <Data>Plugin 'InnoDB' registration as a STORAGE ENGINE failed. </Data> </EventData> </Event> ------------------------------------------------------------------ error 2 -------------------------------------- Log Name: Application Source: MySQL Date: 3/17/2011 4:10:14 PM Event ID: 100 Task Category: None Level: Error Keywords: Classic User: N/A Computer: bale-PC Description: Aborting For more information, see Help and Support Center at http://www.mysql.com. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="MySQL" /> <EventID Qualifiers="49152">100</EventID> <Level>2</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2011-03-17T23:10:14.000Z" /> <EventRecordID>2687</EventRecordID> <Channel>Application</Channel> <Computer>bale-PC</Computer> <Security /> </System> <EventData> <Data>Aborting </Data> </EventData> </Event>
[17 Mar 2011 22:31]
MySQL Verification Team
Thanks for the feedback. Then please look for your my.ini file and try: mysqld --defaults-file=path_for_my.ini\my.ini --console --standalone from a command prompt running as administrator and print here eventual error messages. Thanks.
[18 Mar 2011 1:18]
masi pay
C:\Users\masi>mysqld --defaults-file=c:\Program Files\MySQL\MySQL Server 5.5\my. ini --console --standalone Could not open required defaults file: c:\Program Fatal error in defaults handling. Program aborted
[18 Mar 2011 4:14]
Valeriy Kravchuk
Use quotes, like this: mysqld --defaults-file="c:\Program Files\MySQL\MySQL Server 5.5\my.ini" --console --standalone
[18 Mar 2011 19:03]
masi pay
After UNINSTALL ---------------------- C:\Users\bale>mysqld --defaults-file="c:\Program Files\MySQL\MySQL Server 5.5\my.ini" --console --standalone 'mysqld' is not recognized as an internal or external command, operable program or batch file. After Reinstall and restart of system --------------------------------------- C:\Users\bale>mysqld --defaults-file="C:\Program Files\MySQL\MySQL Server 5.5\my .ini" --console --standalone 'mysqld' is not recognized as an internal or external command, operable program or batch file. -------------------------------------------------------------- Looking at 'Services' MySQL is not started, tried restarting MySQL but it fails every time. The over all behavior is unpredictable, at one point mysql ran fine from cmd. I was able to create database and tables but after another reinstall it is not working. Conclusion: The Uninstall wizard is messing up something that's what is causing the reinstallation crash. At one point, after uninstall I was able to find .err file which I am pasting below. My intention here is not just to find the solution or make it work. I have spent more than few days on this so far, and I know if I just restore my computer and start fresh install it will work like it did before, which would take only an hour or so to do. I was hoping perhaps the development team of mysql would pay some attention to this issue since this problem seems to exists on Windows 7, Mac and Linux + reading the topics on this forum -> this issue was reported back in 2006!! Sadly the mysql team has not responded properly to this issue. I thank you the gentlemen/ladies who have responded to this thread even though I am not sure if you are part of mysql dev-team or just community enthusiasts. ------------------- .err file I found in one of unistall/reinstall process (Which was not created in other uninstall/reinstall process later on) 110317 18:43:03 [Note] Plugin 'FEDERATED' is disabled. 110317 18:43:03 InnoDB: The InnoDB memory heap is disabled 110317 18:43:03 InnoDB: Mutexes and rw_locks use Windows interlocked functions 110317 18:43:03 InnoDB: Compressed tables use zlib 1.2.3 110317 18:43:03 InnoDB: Initializing buffer pool, size = 128.0M 110317 18:43:03 InnoDB: Completed initialization of buffer pool InnoDB: The first specified data file .\ibdata1 did not exist: InnoDB: a new database to be created! 110317 18:43:03 InnoDB: Setting file .\ibdata1 size to 10 MB InnoDB: Database physically writes the file full: wait... 110317 18:43:04 InnoDB: Log file .\ib_logfile0 did not exist: new to be created InnoDB: Setting log file .\ib_logfile0 size to 5 MB InnoDB: Database physically writes the file full: wait... 110317 18:43:04 InnoDB: Log file .\ib_logfile1 did not exist: new to be created InnoDB: Setting log file .\ib_logfile1 size to 5 MB InnoDB: Database physically writes the file full: wait... InnoDB: Doublewrite buffer not found: creating new InnoDB: Doublewrite buffer created InnoDB: 127 rollback segment(s) active. InnoDB: Creating foreign key constraint system tables InnoDB: Foreign key constraint system tables created 110317 18:43:05 InnoDB: Waiting for the background threads to start 110317 18:43:06 InnoDB: 1.1.5 started; log sequence number 0 110317 18:43:06 [Note] Event Scheduler: Loaded 0 events 110317 18:43:06 [Note] mysqld: ready for connections. Version: '5.5.10' socket: '' port: 3306 MySQL Community Server (GPL) 110317 18:47:31 [Note] Plugin 'FEDERATED' is disabled. 110317 18:47:31 InnoDB: The InnoDB memory heap is disabled 110317 18:47:31 InnoDB: Mutexes and rw_locks use Windows interlocked functions 110317 18:47:31 InnoDB: Compressed tables use zlib 1.2.3 110317 18:47:31 InnoDB: Initializing buffer pool, size = 128.0M 110317 18:47:31 InnoDB: Completed initialization of buffer pool 110317 18:47:31 InnoDB: Operating system error number 32 in a file operation. InnoDB: The error means that another program is using InnoDB's files. InnoDB: This might be a backup or antivirus software or another instance InnoDB: of MySQL. Please close it to get rid of this error. 110317 18:47:41 InnoDB: Operating system error number 32 in a file operation. InnoDB: The error means that another program is using InnoDB's files. InnoDB: This might be a backup or antivirus software or another instance InnoDB: of MySQL. Please close it to get rid of this error. 110317 18:47:51 InnoDB: Operating system error number 32 in a file operation. InnoDB: The error means that another program is using InnoDB's files. InnoDB: This might be a backup or antivirus software or another instance InnoDB: of MySQL. Please close it to get rid of this error. 110317 18:48:01 InnoDB: Operating system error number 32 in a file operation. InnoDB: The error means that another program is using InnoDB's files. InnoDB: This might be a backup or antivirus software or another instance InnoDB: of MySQL. Please close it to get rid of this error. 110317 18:48:11 InnoDB: Operating system error number 32 in a file operation. InnoDB: The error means that another program is using InnoDB's files. InnoDB: This might be a backup or antivirus software or another instance InnoDB: of MySQL. Please close it to get rid of this error. 110317 18:48:21 InnoDB: Operating system error number 32 in a file operation. InnoDB: The error means that another program is using InnoDB's files. InnoDB: This might be a backup or antivirus software or another instance InnoDB: of MySQL. Please close it to get rid of this error. 110317 18:48:31 InnoDB: Operating system error number 32 in a file operation. InnoDB: The error means that another program is using InnoDB's files. InnoDB: This might be a backup or antivirus software or another instance InnoDB: of MySQL. Please close it to get rid of this error. 110317 18:48:41 InnoDB: Operating system error number 32 in a file operation. InnoDB: The error means that another program is using InnoDB's files. InnoDB: This might be a backup or antivirus software or another instance InnoDB: of MySQL. Please close it to get rid of this error. --------------------------------------------- Note: my anti-virus Norton has expired on this computer, YES. I have not uninstalled or updated Norton -True Error msg pointing to fact 'another program might is using innoDB's files' is related to expired Norton ? I am not sure. thanks
[21 Mar 2011 18:12]
Santo Leto
Hello Masi, I'm sorry to hear all your problems. 1. The error you obtained: 'mysqld' is not recognized as an internal or external command, operable program or batch file. means that mysqld is not in the PATH environment variable of your operating system. In this case if you execute 'mysqld' (or any other mysql program) the command line simply does not know what to do. In general, there are two possibilities to solve this problem: a) you can add mysqld in your PATH environment variable. If you do so, then you can start mysqld from any location. You can verify whether mysqld is on your command line PATH or not, executing the following command: where mysqld Please remember to open a new command prompt after you change the PATH variable, for your changes to take effect. You can add mysqld in your PATH environment variable in two ways: a.1) at installation level, by clicking on the "Include Bin directory in Windows PATH" option a.2) manually, at any time, by including the MySQL "bin" directory to your PATH variable as described, for instance, here: http://support.microsoft.com/kb/310519) b) the second possibility is to start the server directly from the "bin" directory, so that when you execute mysqld, the windows command line find the program on the current directory and start it: cd path_to_your_mysql_installation\bin mysqld your_options_here 2. > My intention here is not just to find the solution or make it work. I can ensure you that we have the same goal. We are happy to fix any know bugs so that all users can benefit of the improvements / bugs fix. > and I know if I just restore my computer and start fresh install it will work like it did before, which would take only an hour or so to do. Please do not restore your computer. A less drastic workaround can be to use the zip archive and start a fresh installation from there or create the MySQL Window Service manually (please see later for some suggestions) > I was hoping perhaps the development team of mysql would pay some attention to this issue ... > Sadly the mysql team has not responded properly to this issue. I verified there are some problems with the Configuration Wizard after reinstalling MySQL. These are the steps I followed on a fresh machine (XP): - installed MySQL 5.5.10 32 bit using MSI package --> all worked fine - uninstalled the instance installed previously (using "add / remove programs") --> all worked fine - noted that the file my.ini is still in the MySQL directory (all other files were removed) - noted that the entry "MySQL" on the Service window has not been removed, and it's in an incoherent status ("started") - installed MySQL again, on the same folder, using the same MSI package - arrived at the Configuration Wizard, I had two options: "Reconfigure Instance" and "Remove Instance". I chose "Reconfigure Instance" - noted that it was not possible to change the innodb tablespace destination folder, not the name of the MySQL Service - arrived at "Security Option" screen: wrote the old password, specified a new password - server start successfully So in my test I was not able to verify the bug as described initially. But a problem is there if I don't remember the old root password: - uninstalled the instance installed previously (using "add / remove programs") --> all worked fine - installed MySQL again, on the same folder, using the same MSI package - arrived at the Configuration Wizard, I chose "Reconfigure Instance" as before - arrived at "Security Settings" screen: left the old password field empty, specified a new password - server did not start successfully: got an error at "applying security settings" because the password I provided was wrong. I performed that second attempt just to find myself in wrong situation, and see what I could do to fix the error. So let's suppose I made some errors and I want to find a solution. So, if I don't remember the old password, the first idea I have is to choose "Remove Instance" instead of "Reconfigure Instance". Here are the steps: - click on "Cancel" button - run again the configuration wizard (opening it from bin directory) - selected "Remove Instance" - noted that the instance has been removed from the Service window - run again the Configuration Wizard - noted that if I want, I can set tablespace and a Service name (left the defaults) - arrived at screen "Security Option" I see there is a "current root password" field. This is a bug, it should not be there. I don't know the password. Left if blank and set a new password - of course the server did not start successfully: got an error at "applying security settings" because the password I provided was wrong - clicked on "Cancel" button ---> the bug is that there is not way to fix the problems using the Configuration Wizard (as far as I saw). > I thank you the gentlemen/ladies who have responded to this thread even though I am not sure if you are part of mysql dev-team or just community enthusiasts. We are part of the MySQL support / bug verification teams. 3. > InnoDB: The error means that another program is using InnoDB's files. > InnoDB: This might be a backup or antivirus software or another instance > InnoDB: of MySQL. Please close it to get rid of this error. > Note: my anti-virus Norton has expired on this computer, YES. I have not uninstalled or updated Norton - True. Error msg pointing to fact 'another program might is using innoDB's files' is related to expired Norton ? I am not sure. Those InnoDB errors are probably caused by the fact that mysqld.exe is already running on that datadir. BTW, a best practice is to exclude mysql data directory from anti virus online scan. I use another antivirus and don't know exactly how this is handled by Norton, but in general antivirus programs have an option where you can exclude one or more directories from online scan (this is very useful for example, also when you download source code using bazaar and you compile it). 4. I would suggest you to try again the command: mysqld --defaults-file="C:\Program Files\MySQL\MySQL Server 5.5\my.ini"--console --standalone from the "bin" directory of your server. Please make sure your server is not running already executing the ping command: mysqladmin ping -uroot -p if it is, shut it down first, using the command. mysql shutdown -uroot -p Hope this helps.
[22 Mar 2011 20:19]
masi pay
Thanks for detailed reply. I have done everything in the past before your post and the problems were still there. But before I go on let me say that I have fixed the problem some how(..) and mysql is running fine now. Most people who post problems and bugs constantly try different options and work around that they can't keep track of what they did in the process of fixing the problem. And some how out of no where it works! By the time they get their problem fixed they can't remember what part of what they did actually fixed the problem. In my case it was the same. I was trying all the options and suggestions posted here in this forum and else where and adding few of my own, suddenly it all worked just fine out of no where and I couldnt' figure out what was it that i did that fixed the problem. Sadly, when the problem is solved in such manner, the people who post the problems do not come back to their thread to answer or to provide some idea to how to fix the problem and such threads just stays open giving no clue to others. I have seen many post regarding the same problem here and in many other forums. All of such post include suggestions by different people but at the end there is no solution posted. Some of such posts were posted in 2006! with no solution posted there. Which only implies the person with the problem must have fixed the problem(by now) but just didn't care to come back to post it or the person didn't know exactly how he got the problem fixed. I am using windows vista. I have seen many other people having same problem with XP as well. Anyway let me point out to from what i remember that got the problem fixed. [ @santos, I had already tried everything you suggested. Remove Instance, delete mysql directory, trying to start mysqld from bin folder etc. Regardless of what the reinstallation gets stuck at Start Service. Funny thing is that some times it asks for old root password and sometime it doesn't. This alone points to the underlying bug.] My solution:: On my vista, -Reinstall mysql 5.5.1 -- failed(at Start Service with or without asking the root password) -uninstall using add/remove program(or using the same installer, will give uninstall/remove option) -delete c:\Program Files\MySQL folder -delete c:\MySQL folder (this could be \MySQL\ or \MySQL datafiles\ based on what you chose in the installation process) -On C:\ change folder options to view 'hidden' files/folders There is C:\ProgramData\MySQL foldera -delete C:\ProgramData\MySQL folder -restart the machine and do fresh installation of MySQL 5.5.1 --End of the problem-- If you are using XP or other versions of windows try to find where MySQL data files folder is located. It could be under username\AppData\ or else where based on XP or Windows 7 @dev-team Even when you uninstall, the data files in this hidden folder are not deleted regardless of whether you chose Remove Instance or Reconfigure option(I think). Actually the hidden C:\ProgramData\MySQL\MySQL Server5.5\data contains all of C:\program files\mysql\mysql server 5.5\data files and .err file and other log files. So, when you Reinstall, installer is fetching and using some data from previous installation which is causing this problem? --------------------------- note:(not related to mysql) Even after you get mysql proglem fixed and/if you are running WAMP server you might get PHP error message regarding 'timezone' when you run a script or when you set up PhpMyAdmin. Simply go to PHP .ini ,find [Date] under 'Module Setting' and set date.timezone = US/Central or find appropriate timezone from php.net.
[18 Jan 2012 21:48]
Patrick Brewer
I think this work around needs to be made more visible on the site; and the problem addressed in the installer/uninstaller. I just wasted 7.5 hours of an 8 hour work day on this exact issue. And the solution of deleting the hidden directories before reinstalling worked. Also when encountering this problem I could find no error messages written anywhere to even hint at the problem.
[31 Mar 2014 8:49]
Yngve Svendsen
Posted by developer: Thank you for the bug report. We are closing this report now since the original config wizard is no longer the focus of Windows deployment efforts. For recent MySQL Server versions, the config wizard is also no longer available, and the MySQL Installer for Windows is the recommended way to install MySQL Server on Windows.
