Log Data Directory Not Set Or It Is Set to Data Directory in A MySQL Auto-Discovered Instance
Article ID: 54346
Article Type: Troubleshooting
Last Modified:
In a MySQL auto-discovered instance, the value of log data directory is either not set, or it is set to data directory.
Symptoms
A MySQL auto-discovered instance either does not have a value set for the log data directory, or the value is set to data directory.
Causes
No value or wrong value is set for the log data directory because the --log-bin parameter and the --datadir parameter are not set in the command line or the configuration file.
Resolution
To resolve this problem, you can use one of the following procedures:
In the auto-discovered instance, update the value for the log data directory.
If binary logging is enabled, complete the following steps:
Do one of the following:
Add the value to the log-bin parameter in the config file.
Start the MySQL server with --log-bin = /<log data directory path>/<log file prefix> parameter.
Delete the incomplete instance that was created, and then discover the instance again.
If binary logging is disabled, complete the following step:
Do one of the following:
Add the data directory value to the datadir parameter in the config file.
Start the MySQL server with the --datadir = <data directory> parameter.
Delete the incomplete instance that was created, and then discover the instance again.