Hi,
so the script is calling mysqld_install_cmd_line(), which is calling mysqld with some options
mysqld_install_cmd_line()
|
{
|
"$mysqld_bootstrap" $defaults $defaults_group_suffix "$mysqld_opt" --bootstrap $silent_startup\
|
"--basedir=$basedir" "--datadir=$ldata" --log-warnings=0 --enforce-storage-engine="" \
|
"--plugin-dir=${plugindir}" \
|
$args --max_allowed_packet=8M \
|
--net_buffer_length=16K
|
}
|
Note that above there is no log_error server option.
Based on log_error server variable if the server is started without --log-error errors should be in stderr.
If there is no name (of a file for this option) logs will be in <hostname.err> in the datadir (since $ldata == datadir in your case in /var/lib/mysql).
So in your case the error logs will be in stderr already you can try to find out does it exist.
Even the server code is saying the same:
case OPT_LOG_ERROR:
|
/*
|
"No --log-error" == "write errors to stderr",
|
"--log-error without argument" == "write errors to a file".
|
*/
|
Note that if you have a config file (see option files that is configuring log_error) it can be invoked from there also.
In debian there is postinst script that is using hardcoded value for logs {{mysql_logdir=/var/log/mysql }}.
I think that correct patch for this case is to write Examine the logs in stderr for more information. - since log_error="" and parsing the arguments is already finished before!
But let's wait on danblack review too.
Hi,
so the script is calling mysqld_install_cmd_line(), which is calling mysqld with some options
mysqld_install_cmd_line()
{
"$mysqld_bootstrap" $defaults $defaults_group_suffix "$mysqld_opt" --bootstrap $silent_startup\
"--basedir=$basedir" "--datadir=$ldata" --log-warnings=0 --enforce-storage-engine="" \
"--plugin-dir=${plugindir}" \
$args --max_allowed_packet=8M \
--net_buffer_length=16K
}
Note that above there is no log_error server option.
Based on log_error server variable if the server is started without --log-error errors should be in stderr.
If there is no name (of a file for this option) logs will be in <hostname.err> in the datadir (since $ldata == datadir in your case in /var/lib/mysql).
So in your case the error logs will be in stderr already you can try to find out does it exist.
Even the server code is saying the same:
case OPT_LOG_ERROR:
/*
"No --log-error" == "write errors to stderr",
"--log-error without argument" == "write errors to a file".
*/
Note that if you have a config file (see option files that is configuring log_error) it can be invoked from there also.
In debian there is postinst script that is using hardcoded value for logs {{mysql_logdir=/var/log/mysql }}.
I think that correct patch for this case is to write Examine the logs in stderr for more information. - since log_error="" and parsing the arguments is already finished before!
But let's wait on danblack review too.