MySQL Bugs: #70464: MySQL Fresh install will not Start

Bug #70464	MySQL Fresh install will not Start
Submitted:	29 Sep 2013 18:38	Modified:	25 Aug 2014 20:04
Reporter:	CE Stanley	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: Installing	Severity:	S5 (Performance)
Version:	5.6.6	OS:	Windows (Windows 7 64bit)
Assigned to:		CPU Architecture:	Any
Tags:	StartPending to Stopped

Description:
I loaded Windows 7 64bit to an SSD drive. I loaded Visual Studio 2010 including MSSQL Lite. I loaded MySQL 5.6.6. Configuration went as expected. When the service is pending Start, it transitions to Stopped when I expected it yo start. Logs state "Timeout" as the issue. The SSD drive has 540M bit/sec read access and 460Mbit/sec write (Not sure if this is the issue).

I am currently not able to start MySQL in any mode. No logs are created in the specified log directory.

The syntax of the reported error is:
The service MySQL56 failed the most recent status change request with the message Time out has expired and the operation has not been completed.

How to repeat:
Install fresh SSD drive in Windows 7 64 bit PC. Load Windows 7 64bit. Load Visual Studio 2010 including MSSQL. Load MySQL 5.6.6. During configuration, specify a different drive for log files (in my case, E: drive). Click next to Start service. Service will not start.

If you can provide evidence of a software bug, please reopen this.
Check the mysql error log for clues...

Administrative Evens Log:
9/29/2013 12:08:13 PM Service Control Manager Event ID 7034
"The MySQL56 service terminated unexpectedly.  It has done this 1 time(s)."

9/29/2013 12:08:08 PM MySQL Event ID 100
"The description for Event ID 100 from source MySQL cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event: 

Aborting"

From MySQL Workbench, Administration - Startup / Shutdown:
2013-09-29 12:38:21 - Workbench will use cmd shell commands to start/stop this instance
2013-09-29 12:38:21 - Status check of service 'MySQL56' returned stopped
2013-09-29 12:38:24 - Status check of service 'MySQL56' returned stopped
2013-09-29 12:38:24 - Starting server...
2013-09-29 12:38:28 - Status check of service 'MySQL56' returned start pending
2013-09-29 12:38:28 - Server start done.
2013-09-29 12:38:28 - Status check of service 'MySQL56' returned start pending
2013-09-29 12:38:37 - Status check of service 'MySQL56' returned stopped

Please open a command prompt with Administrator privileges and issue the below command to get the defaults-file used by the service:

C:\>sc qc mysql56
[SC] QueryServiceConfig SUCCESS

SERVICE_NAME: mysql56
        TYPE               : 10  WIN32_OWN_PROCESS
        START_TYPE         : 2   AUTO_START
        ERROR_CONTROL      : 1   NORMAL
        BINARY_PATH_NAME   : "C:/Program Files/MySQL/MySQL Server 5.6/bin\mysqld" --defaults-file="C:\ProgramData\MySQL\MySQL Server 5.6\my.ini" MySQL56
        LOAD_ORDER_GROUP   :
        TAG                : 0
        DISPLAY_NAME       : MySQL56
        DEPENDENCIES       :
        SERVICE_START_NAME : NT AUTHORITY\NetworkService

Then go to the bin install directory and issue the below command:

mysqld --defaults-file="C:\ProgramData\MySQL\MySQL Server 5.6\my.ini" --standalone --console

print here the error messages . Thanks.

No logs are created during startup. Perhaps the issue occurs before logs are initialized.

Events are logged in Windows Events.
This is preventing me from working.

The description for Event ID 100 from source MySQL cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event: 

Could not use E:/Users/CE/Downloads/MySQL_Logs/PC-CHARLES-slow.log for logging (error 9). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.

Drive E is a accessible SATA drive. The directory is empty. If this is not a bug then MySQL should not be distributed as software.

Thank you for the feedback. The instruction I gave you before assuming the service failed to start is to start the server as standalone so we can see the error printed. Please do as requested. Thanks.

C:\Windows\system32>sc qc mysqk56
[SC] OpenService FAILED 1060:

The specified service does not exist as an installed service.

C:\Windows\system32>

Hello Godofredo Miguel Solorzano,

  It seems that I am unable to update the code base as well. I entered the command you requested and got a Not Installed error got Not Installed error from the command line. So maybe the issue is with the install process, not with runtime code? What do you think?

Using Cygwin helps -
CE@PC-Charles /cygdrive/c
$ sc qc mysql56
[SC] QueryServiceConfig SUCCESS

SERVICE_NAME: mysql56
        TYPE               : 10  WIN32_OWN_PROCESS
        START_TYPE         : 2   AUTO_START
        ERROR_CONTROL      : 1   NORMAL
        BINARY_PATH_NAME   : "C:/Program Files/MySQL/MySQL Server 5.6/bin\mysqld" --defaults-file="C:\ProgramData\MySQL\MySQL Server 5.6\my.ini" MySQL56
        LOAD_ORDER_GROUP   :
        TAG                : 0
        DISPLAY_NAME       : MySQL56
        DEPENDENCIES       :
        SERVICE_START_NAME : NT AUTHORITY\NetworkService

Thank you for the feedback. How before asked please print here the result of the below command from the bin installl directory:

mysqld --defaults-file="C:\ProgramData\MySQL\MySQL Server 5.6\my.ini" --standalone --console

Thanks in advance.

MySQL.log

Attachment: PC-Charles_MySQL.log (application/octet-stream, text), 3.88 KiB.

I may have found the issue. When I uninstalled MySQL, it did not clean up the files on C:/Program Files or C:/Program Data. These files and folders had information in them that caused MySQL to not fully load and the upgrade operation failed as well. So the issue is in code, but  it is in the installer and uninstaller, not in MySQL itself.

Thank you for the feedback.

Which not expected files did MYSQL Installer left in C:/Program Files. Note, that this is expected behavior to do not touch Program Data, because it contains data directory with databases and tables, created by a user.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".