Details
-
Bug
-
Status: Open (View Workflow)
-
Critical
-
Resolution: Unresolved
-
13.3
-
None
-
Not for Release Notes
-
Q1/2027 Server Maintenance
Description
mariadbd-multi start uses the mariadbd= binary given in a [mariadbd<N>] or [mysqld<N>] group. mariadbd-multi reload for the same group ignores it and uses the default binary from [mariadbd_multi]. killproc then looks for the wrong program name when it sends SIGHUP. mysqld= works for both commands.
Test case
export PATH=/test/mtest/MDEV-42003/MD031126-mariadb-13.2.0-linux-x86_64-opt/bin:$PATH |
|
|
# Two dummy server binaries, so that both paths exist
|
mkdir -p /tmp/old /tmp/new |
printf '#!/bin/sh\n' > /tmp/old/mariadbd; printf '#!/bin/sh\n' > /tmp/new/mariadbd |
chmod +x /tmp/old/mariadbd /tmp/new/mariadbd |
|
|
cat > /tmp/multi.cnf <<'EOF' |
[mariadbd_multi]
|
mariadbd=/tmp/old/mariadbd |
[mariadbd3]
|
mariadbd=/tmp/new/mariadbd |
pid-file=/tmp/m3.pid |
EOF
|
|
|
mariadbd-multi --defaults-file=/tmp/multi.cnf --no-log --silent --print-commands start |
mariadbd-multi --defaults-file=/tmp/multi.cnf --no-log --silent --print-commands reload 2>/dev/null |
Actual result
Starting MariaDB servers
|
Running: /tmp/new/mariadbd --defaults-group-suffix=bd3 --pid-file=/tmp/m3.pid &
|
|
|
Reloading MySQL servers
|
Running: killproc -p /tmp/m3.pid -HUP /tmp/old/mariadbd
|
Running: touch /tmp/m3.pid
|
Expected result
Reloading MySQL servers
|
Running: killproc -p /tmp/m3.pid -HUP /tmp/new/mariadbd
|
Running: touch /tmp/m3.pid
|
Attachments
Issue Links
- is caused by
-
MDEV-42003 Enhance mariadbd-multi to support mariadbd prefixes
-
- In Testing
-
