Bug #78667 workbench change acces permission of my.cnf after editing option file
Submitted: 1 Oct 2015 12:12 Modified: 22 Nov 2017 22:17
Reporter: Сергей Соболев Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:6.3.2 OS:Microsoft Windows (Microsoft Windows 10 Pro)
Assigned to: CPU Architecture:Any
Tags: WBBugReporter

[1 Oct 2015 12:12] Сергей Соболев
Description:
----[For better reports, please attach the log file after submitting. You can find it in C:\Users\sergei\AppData\Roaming\MySQL\Workbench\log\wb.log]

MySQL - arch: x86_64
ver: 5.7.8
release: 0.3.rc.el7
installed from yum repository  mysql57-community-dmr.
OS - RHEL7.1

Workbench 6.3.2 running under Win10.

I'm editing option file my.cnf in Workbench. after saving, access permittion of my.cnf changed to -rw-------
while origninally it was -rw-r--r--.

after that, if I try to restart mysql server, mysqld can't read my.cnf, because it run under mysql user.
eventually mysql started with default option but 
workbench and systemd can't detect that mysql is running because 
pid file created in /var/lib/mysql 
not in /var/run/mysql as it needed for systemd.

How to repeat:
connect Workbench to mysql server, edit option file and save.
then check my.cnf access permission bits.
try to restart server.
[1 Oct 2015 13:42] Сергей Соболев
the same happened if I run Workbench under Linux.
so problem is on server side
[22 Nov 2017 22:17] Miguel Solorzano
Thank you for the bug report. I couldn't repeat with version 6.3.10 and MySQL server 5.7.20 running on CentOS 7.