Details
Major
Description
The /etc/init.d/mysql script does not accept any arguments, even though the "service" tool on those platforms does accept arguments/"OPTIONS" these days. This is particularly problematic in the case of Galera, for example, where you may occasionally need to pass --wsrep-cluster-address=gcomm:// to bootstrap a cluster.
This issue is very easily resolved by replacing this line:
/usr/bin/mysqld_safe > /dev/null 2>&1 &
with this one:
/usr/bin/mysqld_safe "${@:2}" > /dev/null 2>&1 &
Gliffy Diagrams
Attachments
Issue Links
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
Verified that the patch with:
/usr/bin/mysqld_safe "$
{@:2}" > /dev/null 2>&1 &
works fine.
Now:
service mysql start --wsrep-cluster-address=gcomm://
works great.
Not really sure who it should belong to, please reassign if needed.
It's more generic than MDEV-4253 and I also don't see why not to do it in all init scripts rather than Galera only; but I'm inclined to keep MDEV-4253 open too, and assigned to Seppo, so that he'll make the change in the upstream (codership) version of the script and it won't get lost on the next merge if it again comes as a replacement of the old files.
Raising the priority due to upcoming 5.5.31-galera release, since it should be easy and safe to fix.
See also MDEV-4253.
seems to be fixed
mariadb-galera-server-5.5 5.5.35+maria-1~wheezy
fgrep safe /etc/init.d/mysql
# and its wrapper script "mysqld_safe".
/usr/bin/mysqld_safe "${@:2}" > /dev/null 2>&1 &
I believe
MDEV-4253is the same issue, the analysis there is the same, i.e. mysql init script does not pass on parameters.