service mysql start bails out with weird error message from the new mysqld_safe_helper binary when having log-error option set in either [mysqld] or [mysqld_safe] section of my.cnf. Whether log-error is used with an explicit file name argument or not doesn't matter. Also when not having log-error in the config file at all mysqld_safe_helper is still throwing an error, but in this case the service startup script reports SUCCESS instead of ERROR
The error message is
(Jira does not show this, but the actual file name shown in the error message is the unicode placeholder character for code point U+0001, and not just an empty string)
The actual error code varies and is usually a large positive or negative value, but not a valid error code.
When looking at strace output the parameters passed to mysqld_safe_helper look fine:
Also when running mysqld_safe_helper with the same arguments manually it works as expected without throwing an error at all:
Also when passing in an invalid file name a correct error message is displayed (^A here was entered using CTRL-V CTRL-A, so it is really 0x01
(again the file name in the actual error message is the U+0001 unicode placeholder, and not just an empty string)