Error number: 3844; Symbol: ER_INNODB_REDO_LOG_ARCHIVE_NO_SUCH_DIR; SQLSTATE: HY000
Message: Redo log archive directory ‘%s’ does not exist or is not a directory
Error 3844, ER_INNODB_REDO_LOG_ARCHIVE_NO_SUCH_DIR, occurs when the sever attempts to run InnoDB redo log backup operations, but it is unable to find a directory specified for such tasks.
This error is typically associated with a missing or incorrectly defined data directory in the MySQL Enterprise Backup options of the config file for the MySQL server, innodb-redo-log.cnf. The designated folder path specified in this config file must exist, so that the server can create the archive logs.
Common Cases
When setting up a MySQL server, Error 3844 is commonly encountered. When the MySQL server starts, it runs an initial configuration that specifies the directory location of the redo log and any other relevant files. The configuration file must be correctly defined, and if not, it can result in Error 3844.
Another common cause of Error 3844 is a mismatch between the directory path specified in the configuration file and the directory path that actually exists. For example, if the data directory is set to a directory that does not exist, it will result in the error.
Resolution
The resolution for Error 3844 is to ensure that the directory paths are correctly defined in the MySQL Enterprise Backup and innodb-redo-log.cnf.
If the server is not able to locate the directory associated with the archive log, then the configuration file must be updated and the server must be restarted. If the directory exists, check the spelling of the existing path when compared to the path named in the configuration file, as this discrepancy can also result in this error.
If the server is unable to connect to the directory due to invalid credentials, then the credentials must be updated. Additionally, the server must also be restarted to allow any changes to take effect before attempting any operations.
In some cases, Error 3844 can be resolved by deleting or renaming the innodb-redo-log.cnf, and then restarting the server. This will cause the server to either create a new configuration file, or create the directory that it needs to write the archive log.