Page MenuHomePhabricator

/run/mysqld with correct rights should be exitst
Closed, InvalidPublic

Description

After finishing cloning of db2096 (T206593) I was not able to start MySQL, because there was no /run/mysqld directory. After creating the directory I still wasn't able to start the server, because I had to set up the correct rights.
We need to ensure this directory will be created on mariadb servers

Related Objects

Event Timeline

because there was no /run/mysqld directory

This is because the server was not rebooted- /run/mysqld is created automaticly by tmpfile config on start.

In order to be able to do it on server start we need the systemd version on buster at least.

Change 467317 had a related patch set uploaded (by Jcrespo; owner: Jcrespo):
[operations/puppet@production] mariadb: Create socket dir also on puppet run, & for multiinstance

https://gerrit.wikimedia.org/r/467317

Change 467317 had a related patch set uploaded (by Jcrespo; owner: Jcrespo):
[operations/puppet@production] mariadb: Create socket dir also on puppet run, & for multiinstance

https://gerrit.wikimedia.org/r/467317

Change 467317 abandoned by Jcrespo:

[operations/puppet@production] mariadb: Create socket dir also on puppet run, & for multiinstance

Reason:

This is no longer needed, the systemd unit of the package creates it on start and doesn't delete it after stop.

https://gerrit.wikimedia.org/r/467317