#MARIADB UPDATE FULL#
To get the full information I run ‘sealert -a /var/log/audit/audit.log’ as shown below. # ausearch -c 'mysqld_safe_hel' -raw | audit2allow -M my-mysqldsafehel You can generate a local policy module to allow this access. If you believe that mysqld_safe_helper should have the setgid capability by default. Jan 14 10:21:38 server python: SELinux is preventing /usr/bin/mysqld_safe_helper from using the setgid capability. Jan 14 10:21:38 server setroubleshoot: SELinux is preventing /usr/bin/mysqld_safe_helper from using the setgid capability. Instead I tried running journalctl -xe as suggested, this output the following: I tried to undo the yum transaction in order to get back into a working state so that I could investigate more later, however this too failed. Jan 14 10:21:37 server systemd: rvice failed. Jan 14 10:21:37 server systemd: Unit rvice entered failed state. Jan 14 10:21:37 server systemd: Failed to start LSB: start and stop MySQL. Jan 14 10:21:37 server systemd: rvice: control process exited, code=exited status=1 Jan 14 10:21:36 server mysql: /usr/bin/mysqld_safe_helper: Cannot change uid/gid (errno: 1) Jan 14 10:21:36 server mysql: 170114 10:21:36 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql Jan 14 10:21:36 server systemd: Starting LSB: start and stop MySQL. usr/bin/mysqld_safe_helper: Cannot change uid/gid (errno: 1) We can see that the error appears to be related with mysqld_safe_helper trying to change UID/GID as per this error line:
Jan 14 10:17:09 server systemd: rvice failed. Jan 14 10:17:09 server systemd: Unit rvice entered failed state. Jan 14 10:17:09 server systemd: Failed to start LSB: start and stop MySQL. Jan 14 10:17:09 server systemd: rvice: control process exited, code=exited status=1 Jan 14 10:17:08 server mysql: /usr/bin/mysqld_safe_helper: Cannot change uid/gid (errno: 1) Jan 14 10:17:08 server mysql: 170114 10:17:08 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql Jan 14 10:17:08 server systemd: Starting LSB: start and stop MySQL. Process: 14016 ExecStart=/etc/rc.d/init.d/mysql start (code=exited, status=1/FAILURE) Process: 14010 ExecStop=/etc/rc.d/init.d/mysql stop (code=exited, status=0/SUCCESS) Loaded: loaded (/etc/rc.d/init.d/mysql bad vendor preset: disabled)Īctive: failed (Result: exit-code) since Sat 10:17:09 UTC 4s ago Sure enough all websites were returning an “Error connecting to database” error.įirst I had a look to see if MariaDB/MySQL was running.
The problem was identified through monitoring, which notified that a website on the server was unresponsive.
#MARIADB UPDATE HOW TO#
After the most recent MariaDB update to version 10.0. in CentOS 7.3 I found that it failed to start back up correctly, here’s how to fix it. I have this server to set to automatically perform a ‘yum update -y’ once every 24 hours in order to keep it automatically up to date.
0 kommentar(er)
