Bug #84173 | mysqld_safe --no-defaults & silently does NOT work any more | ||
---|---|---|---|
Submitted: | 13 Dec 2016 8:33 | Modified: | 15 Feb 2017 1:22 |
Reporter: | Valeriy Kravchuk | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Command-line Clients | Severity: | S3 (Non-critical) |
Version: | 5.7.17 | OS: | Fedora (Fedora 23) |
Assigned to: | Terje Røsten | CPU Architecture: | Any |
Tags: | basedir, datadir, missing manual, mysqld_safe, regression |
[13 Dec 2016 8:33]
Valeriy Kravchuk
[13 Dec 2016 8:57]
Valeriy Kravchuk
This was on recently updated Fedora 23 64-bit box
[13 Dec 2016 9:14]
MySQL Verification Team
Hello Valeriy, Thank you for the bug report. Thanks, Umesh
[13 Dec 2016 9:16]
MySQL Verification Team
test results
Attachment: 84173.results (application/octet-stream, text), 4.60 KiB.
[13 Dec 2016 9:17]
MySQL Verification Team
Imho - this sounds like doc bug to me after reading https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-17.html
[13 Dec 2016 10:49]
Terje Røsten
Posted by developer: I think root cause is that "mysqld_safe ignores the current working directory"; from release notes: http://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-17.html Workaround: use absolute path to datadir, for example: $ bin/mysqld_safe --no-defaults --datadir=$(pwd)/data & Or even better: stop using leagcy mysql_safe script and use the daemonize option[1]: $ bin/mysqld --no-defaults --daemonize --log-error --datadir=$(pwd)/data (no trailing & neeeded) [1]: http://dev.mysql.com/doc/refman/5.7/en/server-options.html#option_mysqld_daemonize
[13 Dec 2016 13:35]
Peter Laursen
To me it looks like this page http://dev.mysql.com/doc/refman/5.7/en/mysqld-safe.html also needs an update where it says Because mysqld_safe tries to find the server and databases relative to its own working directory, you can install a binary distribution of MySQL anywhere, as long as you run mysqld_safe from the MySQL installation directory: shell> cd mysql_installation_directory shell> bin/mysqld_safe & -- Peter -- not a MySQL/Oracle person
[25 Dec 2016 10:36]
Terje Røsten
Hi Valerii! $ bin/mysqld_safe --no-defaults & not working is regression we hope to fix in next batch of releases, sorry for the trouble.
[31 Jan 2017 11:37]
Valeriy Kravchuk
Version 5.5.54 is also affected.
[15 Feb 2017 1:22]
Paul DuBois
Posted by developer: Noted in 5.5.55, 5.6.36, 5.7.18, 8.0.1 changelogs. mysqld_safe --no-defaults did not work (inadvertent consequence of an earlier bug fix).