MySQL Bugs: #95293: edit conf file lead to error 1053 services didnot respond in timely fashion

Bug #95293	edit conf file lead to error 1053 services didnot respond in timely fashion
Submitted:	8 May 2019 11:04	Modified:	9 May 2019 9:57
Reporter:	mohamed atef	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL for Windows: Installer	Severity:	S3 (Non-critical)
Version:	5.7.25,5.7.26	OS:	Windows
Assigned to:		CPU Architecture:	Any
Tags:	edit conf file lead to error 1053 services didnot respond in timely fashion

Description:
changing any option in the my.ini file manual change lead to services didn`t start 

How to repeat:
set up server 5.7.25 in win 10 64x
then use workbench to edit my.ini file
then restart service
it will work
but if you opened the my.ini file 
and change options like adding new replicate do db line or binlog do db line
then restart the server
the services will not respond with error 1053

 i added theses lines
replicate-do-db = abc_info
replicate-do-db = abc_arc 

binlog-do-db = abc_info
binlog-do-db = abc_arc

Suggested fix:
i dont know

We're sorry, but the bug system is not the appropriate forum for asking help on using MySQL products. Your problem is not the result of a bug.

Support on using our products is available both free in our forums at http://forums.mysql.com/ and for a reasonable fee direct from our skilled support engineers at http://www.mysql.com/support/

Thank you for your interest in MySQL.

I couldn't repeat with 5.7:

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

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

C:\>NET STOP mysql57
The MySQL57 service is stopping.
The MySQL57 service was stopped successfully.

C:\>notepad "C:\ProgramData\MySQL\MySQL Server 5.7\my.ini"

C:\>type "C:\ProgramData\MySQL\MySQL Server 5.7\my.ini" | findstr 95293
# added line bug 95293

C:\>NET START  mysql57
The MySQL57 service is starting.
The MySQL57 service was started successfully.

Then I tested before with version 8.0 and failed. I guess this is issue with environment and not MySQL server, need to test more.

Thank you for the feedback.
- Installed 5.7.26 using mysql-installer-commercial-5.7.26.0.msi (pulled from internal repository)
- Connected to instance using WB
- Edited conf file using Administrator TAB  
  INSTANCE -> Open file -> Logging -> checked "binlog-do-db" and entered "mysql" and applied
- restarted 5.7 instance using services.msc -> MySQL57 right click and restarted
- Noted that below entry at the end exists in C:\ProgramData\MySQL\MySQL Server 5.7\my.ini

binlog-do-db = mysql
- Manually edited (To specify multiple databases you must use multiple instances of this binlog-do-db) C:\ProgramData\MySQL\MySQL Server 5.7\my.ini
 and appended below lines

replicate-do-db = abc_info
replicate-do-db = abc_arc 
binlog-do-db = abc_info
binlog-do-db = abc_arc

- Attempted to restart 5.7 instance using services.msc -> MySQL57 right click and observed 1053 error as provided in the screenshot.

Hello!

I have had the exactly same problem, in a production server... In my case, the problem was the format of the file... when I changed the file My.cnf, the type of file was changed to UTF-8... and, the service wasn't start again... 

Then, I tried to start the "mysql" on the prompt and received a suggestive message, something like "Error on position 1...". I realized that the error was the config file, then I created a new file, copy all the body of the previous file and paste into the new... and the service was started normally!

I hope this tip help others solve any problems...

Best regards,
Fernando Zapata

Bug #103561 marked as duplicate of this one.

Bug #104509 marked as duplicate of this one.

I finally solved this issue by opening my.ini with notepad++ and converting the encoding from utf8 to ansi....  Weird....