+++ This bug was initially created as a clone of Bug #1689300 +++ Description of problem: mysqld_safe --dry-run doesn't work as expected Version-Release number of selected component (if applicable): mariadb-server-10.3.11-1.module+el8+2765+cfa4f87b How reproducible: always Steps to Reproduce: 1. dnf install -y mariadb-server 2. systemctl start mariadb 3. systemctl stop mariadb 4. mysqld_safe --dry-run Actual results: [root@host-8-250-109 ~]# mysqld_safe --dry-run /usr/bin/mysqld_safe: line 932: return: can only `return' from a function or sourced script ^C^C^C^C^C^Z [1]+ Stopped mysqld_safe --dry-run [root@host-8-250-109 ~]# ps -ef | grep mysql root 7196 6107 0 11:52 pts/0 00:00:00 /bin/sh /usr/bin/mysqld_safe --dry-run mysql 7280 7196 0 11:52 pts/0 00:00:00 /usr/libexec/mysqld --basedir=/usr --datadir=/var/lib/mysql --plugin-dir=/usr/lib64/mariadb/plugin --user=mysql --log-error=/var/log/mariadb/mariadb.log --pid-file=/run/mariadb/mariadb.pid --socket=/var/lib/mysql/mysql.sock Expected results: it returns to shell without mysqld running Additional info: # mysqld_safe --help | grep dry --dry-run Simulate the start to detect errors but don't start --- Additional comment from Michal Schorm on 2019-03-21 10:43:42 UTC --- Fix deployed for Fedora: https://src.fedoraproject.org/rpms/mariadb/c/fe4891c5b8e6e5f0ce35328e3fa7b9e6efbb2644?branch=master
MAINTAINER NOTE: I reached upstream with this issue. The script was never meant to be called by an user, instead, that particual part of script was intended to be ran by other scripts. The upstream solved the issue in: MariaDB 10.1.42 MariaDB 10.2.28 MariaDB 10.3.19 with: https://github.com/MariaDB/server/commit/6a7d51b1cb --- I removed the internally prepared patch in favor of the upstream fix.
z-stream clone for rhscl-3.5 created: Bug#1894105
Errata for RHSCL 3.5.z has been released. RHBA-2020:5318