On Sun, May 14, 2017 at 7:45 AM, Patrick Shanahan <paka@opensuse.org> wrote:

* Glen <glenbarney@gmail.com> [05-14-17 10:39]: I am at 20170510 and have no problem with mysql after rebooting to latest kernel-default build there. you don't say which update caused your problem, but I didn't see any recent hickup.

I apologize. I am running Leap 42.2 on about 24 different servers. Every few weeks I run zypper update to fetch the repo updates. Servers which are still on mysql-community-server-5.6.35-22.1.x86_64 do not exhibit this problem. However, servers which have been updated to mysql-community-server-5.6.36-24.3.3.x86_64 do have the problem. In that update, /usr/lib/mysql/mysql-systemd-helper contains an explicit "umask 077" command, which is tagged with a comment "set the default umask bsc#1020976". The effect of that umask command is to cause /var/run/mysql to be created with 700 permissions when the server reboots (inasmuch as /var/run symlinks to /run which is a tmpfs), and this prevents applications not owned by mysql from reaching the socket and communicating with the database. I am trying to determine how best to adjust to these new permissions, which seem to cut off access to MySQL to all user applications needing MySQL. I hope this answers? Please let me know if I need to provide other detail. Thank you! Glen -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org