The recent update to mysql-community-server-5.6.36-24.3.3.x86_64 introduced a change to /usr/lib/mysql/mysql-systemd-helper: # diff mysql-systemd-helper.old mysql-systemd-helper 168a169,171
# set the default umask bsc#1020976 umask 077
After this update, and a subsequent serve reboot, the permissions on /var/run/mysql (wherein lives the mysql.sock socket) changed from 0755 to 0700. This promptly caused all of the application software and programs on my servers which communicate with MySQL to fail, with an "unable to connect" error. chmod 755 /var/run/mysql fixed the immediate connection problem, and a very hacky change to systemd: # diff mysql.service.old mysql.service 13a14
ExecStartPost=/usr/bin/chmod 755 /var/run/mysql
has made it persist between reboots.... for now. I have read https://lists.opensuse.org/opensuse-security-announce/2017-04/msg00036.html, which says:
This non-security issue was fixed: - Set the default umask to 077 in rc.mysql-multi [bsc#1020976]
So, I am trying to understand why this change was made (since I don't want to revert something deemed an issue) and what the correct response to this change should be. Should all my apps have "just worked anyway?" Is nobody else experiencing problems? Should I be doing something differently? The programs I run were written by different teams, and run on different servers, and they *all* failed with this patch. I can't believe that I'm the only one affected by this, and am seeking to understand what I'm doing wrong that caused all my software to get tripped up by this change, and what the most correct fixes would be to compensate/adjust on my end. Guidance, pointers, redirects all solicited and gratefully accepted! Thanks so much! Glen Glen Barney -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org