[MDEV-10395] socket path on tmpfs while package does care about creating the path Created: 2016-07-19  Updated: 2017-04-26  Resolved: 2017-04-26

Status: Closed
Project: MariaDB Server
Component/s: Packaging, Platform SUSE
Affects Version/s: 10.1.16
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Wolfgang Rosenauer Assignee: Sergei Golubchik
Resolution: Cannot Reproduce Votes: 0
Labels: None
Environment:

openSUSE Leap 42.1 / almost identical to SLES12


 Description   

The mariadb server does not start with default settings because of:

Jul 19 09:20:14 db2 sh[5819]: 2016-07-19  9:20:12 140074415835008 [ERROR] Can't start server : Bind on unix socket: No such file or directory

The default path to the socket is:
/var/run/mysql/mysql.sock
but that location is a tmpfs and therefore after a reboot the path /var/run/mysql/ does not exist at all and mariadb refused to start.

At least on openSUSE/SUSE it's required to put a definition into the system as described here:
https://en.opensuse.org/openSUSE:Systemd_packaging_guidelines#Creating_files_.2F_subdirectories_in_.2Fvar.2Frun_and_.2Frun

 Comments   
Comment by Elena Stepanova [ 2016-07-19 ]

Thanks for the report.

I remember this issue being raised before, but on some reason I can't find it now in JIRA; maybe serg remembers the outcome, if there was any.

Comment by Sergei Golubchik [ 2016-12-07 ]

I don't. But as far as I can see, the default socket path in our rpm packages is /var/lib/mysql/mysql.sock.

If you have it different, then, I'd guess, you are using packages built by SuSE. As it's a packaging bug, it needs to be reported to the packager.

Comment by Wolfgang Rosenauer [ 2016-12-08 ]

Oh, Actually you are right apparently for your default location.
I use your packages actually but I found that I have a local /etc/my.cnf specifying that path
[client-server]
socket=/var/run/mysql/mysql.sock

So I guess I somehow inherited that configuration from a previously installed SUSE specific package and forgot about it since I didn't explicitely specify it.
Feel free to close the issue in that case.

Generated at Thu Feb 08 07:41:54 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.