+++ 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
In this particular collection the server won't be started afterwards, so it is less of an issue than the original bug
(In reply to Michal Schorm from comment #2) > In this particular collection the server won't be started afterwards, so it is less of an issue than the original bug I found out the issue is reproducible with the server starting. It is worth fixing.
The --dry-run worked well with its original purpose: https://github.com/MariaDB/server/pull/1238#issuecomment-475494807 Since 10.1 collection will EOL soon an there is not an agreement on Upstream side, WONTFIX.