The server throws this error when the audit_log plugin is referenced but has not been installed with INSTALL PLUGIN.
ER_AUDIT_LOG_HAS_NOT_BEEN_INSTALLED appears when MySQL cannot find the audit_log plugin. Install or enable the plugin with INSTALL PLUGIN audit_log SONAME 'audit_log.so'; then restart or reload the plugin to clear the error.
ER_AUDIT_LOG_HAS_NOT_BEEN_INSTALLED
MySQL raises error 3216 when a statement or configuration setting tries to use the audit_log plugin but the server cannot locate the plugin binary in the plugin directory.
The error surfaced starting with MySQL 5.7.22 and continues in 8.x when audit_log is referenced without prior installation.
The message typically appears at startup if audit_log is listed in the my.cnf file, or after a dynamic SET GLOBAL command enables audit_log without installing it first.
It can also occur during an INSTALL COMPONENT command that references audit_log incorrectly.
Leaving the plugin uninstalled can break compliance monitoring, generate noisy logs, and block startup when audit_log is marked as mandatory in configuration.
Proper installation restores auditing and prevents service interruptions.
Omitting the INSTALL PLUGIN statement before enabling audit_log is the main trigger.
Moving or deleting the audit_log.so file from the plugin directory causes MySQL to think the plugin is missing.
Incorrect plugin_dir paths or file permissions stop MySQL from loading the shared library.
Install the plugin with INSTALL PLUGIN or mysql_plugin, then verify it is active in performance_schema.
Ensure the audit_log shared object resides in the plugin_dir and the mysqld process can read it.
Cloud migrations often skip custom plugins; reinstall audit_log after restore.
Package upgrades may overwrite plugin binary paths; confirm the file exists and permissions remain intact.
Automate plugin installation in deployment scripts so new servers always run INSTALL PLUGIN before configuration enables audit_log.
Monitor SHOW PLUGINS results at startup with tools like Galaxy to detect missing plugins quickly.
ER_PLUGIN_IS_NOT_LOADED indicates an installed plugin failed to load; reinstall or fix library path.
ER_CANT_OPEN_LIBRARY shows MySQL cannot open the shared object file due to permissions or missing dependencies.
Administrators enabled audit_log in my.cnf but never ran INSTALL PLUGIN audit_log.
The audit_log.so file was deleted or moved during an upgrade or filesystem cleanup.
The plugin_dir parameter points to a directory that does not contain audit_log.so.
mysqld lacks read or execute permission on the plugin file.
Plugin was installed but failed to load at runtime.
MySQL cannot open the shared object due to path or permission issues.
An error occurred during plugin loading, often signaling missing dependencies.
Run SELECT PLUGIN_NAME, PLUGIN_STATUS FROM information_schema.PLUGINS WHERE PLUGIN_NAME='audit_log';. If you see ACTIVE, it is installed.
Yes. Use INSTALL PLUGIN audit_log SONAME 'audit_log.so'; then SET GLOBAL audit_log_policy=ALL; to start auditing.
Galaxy surfaces plugin status in its schema explorer and highlights errors returned by SHOW PLUGINS, making it easy to spot missing audit_log installations.
No. Ignoring it disables auditing and may violate compliance requirements. Always resolve the plugin installation.
.avif)
.avif){kind=logo}
