The mysqld_safe script that is used to start mariadb has bad delimeter for sed command in parse_arguments(). When the socket.ssl_cert and socket.ssl_key options are passed, mysqld_safe will generate the following errors: Aug 26 11:11:31 mesa-virt-18.lab.msp.redhat.com mysqld_safe[23525]: sed: -e expression #1, char 26: unknown option to `s' Aug 26 11:11:31 mesa-virt-18.lab.msp.redhat.com mysqld_safe[23525]: sed: -e expression #1, char 25: unknown option to `s' It seems that sed has a problem here since it is using "/" as a delimeter and both socket.ssl_cert and socket.ssl_key take full paths, which of course include "/" characters. Fix is to simply change: arg=`echo $arg | sed "s/^$optname/$optname_subst/"` to arg=`echo $arg | sed "s|^$optname|$optname_subst|"` Note that this error seems completely harmless. In my testing, the ssl_cert and ssl_key are set correctly even when the error occurs.
mariadb-galera-server-5.5.42-1.el7ost.x86_64. No errors were generated by mysqld_safe.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-1762.html