RHEL

Can you provide error log from the joiner ?

This issue originally came from me.

Afraid I don't have the error log now. I actually didn't see an .err file in the data dir on the joiner while this was ongoing. (I did look for one!) I think I got the above warning from "systemctl status mariadb" or journalctl.

I think this works as designed when it can't write the datadir it will select the default location.

That seems rather confusing. Why would it try to write to the datadir specified in the .cnf files, and if it can't write there, then report that it can't write to the default datadir? Why not simply report that it couldn't write where it actually tried to write?

Hi jplindst,

The error is that the log warning is reporting the wrong directory. Even if the server does try the default data directory after failing a test write on the configured data directory, it should log that it was unable to write to the configured data directory.

This problem does not look specific to Galera. It looks the problem is here:

https://github.com/MariaDB/server/blob/mariadb-10.1.43/sql/mysqld.cc#L4541

It is performing the check with the value mysql_real_data_home, which refers to the path of the default datadir:

  SYSVAR_AUTOSIZE(lower_case_file_system,

                  test_if_case_insensitive(mysql_real_data_home));

I believe that it should actually be performing the check with the value of mysql_real_data_home_ptr, which refers to the path of the actual datadir. e.g.:

  SYSVAR_AUTOSIZE(lower_case_file_system,

                  test_if_case_insensitive(mysql_real_data_home_ptr));

A check has been added for a variable indicating a user value (instead of default), plus the corresponding option has been parsed at an early stage, plus a check for its absence has been added: https://github.com/MariaDB/server/commit/93dea7da8302f2518b70175d3d4d8075b878f545

Fixed, https://github.com/MariaDB/server/commit/93dea7da8302f2518b70175d3d4d8075b878f545