Error
Error Code: 1524

MariaDB Error 1524: Plugin Not Loaded

📦 MariaDB
📋

Description

Error 1524 indicates that the MariaDB server attempted to load a plugin, but the plugin was not found, correctly installed, or successfully initialized. This can happen when a server configuration specifies a plugin that doesn't exist or is inaccessible, preventing the associated functionality from being used.
💬

Error Message

Plugin '%s' is not loaded
🔍

Known Causes

4 known causes
⚠️
Plugin File Missing
The physical plugin file (.so or .dll) is not present in the expected MariaDB plugin directory on the server.
⚠️
Incorrect Configuration
The MariaDB configuration file (my.cnf or my.ini) specifies a plugin that is misspelled, has an incorrect path, or is not meant for the current server version.
⚠️
File System Permissions
The MariaDB server process lacks the necessary read permissions to access the plugin file or its directory, preventing it from being loaded.
⚠️
Incompatible Plugin Version
The plugin is incompatible with the current MariaDB server version or has unmet internal dependencies that prevent it from loading successfully.
🛠️

Solutions

3 solutions available

1. Verify Plugin Installation and Configuration easy

Ensure the required plugin is installed and correctly configured in MariaDB.

1
Identify the specific plugin name that is causing the error. The error message `Plugin '%s' is not loaded` will contain the plugin's name.
2
Check if the plugin is actually installed. You can do this by querying the `information_schema.PLUGINS` table.
SELECT PLUGIN_NAME, STATUS FROM information_schema.PLUGINS WHERE PLUGIN_NAME = 'plugin_name_from_error';
-- Replace 'plugin_name_from_error' with the actual plugin name.
3
If the plugin is not listed or its status is 'NOT INSTALLED', you need to install it. This usually involves placing the plugin's `.so` (Linux/macOS) or `.dll` (Windows) file in the MariaDB plugin directory. Consult your MariaDB version's documentation for the correct plugin directory location.
4
After placing the plugin file, restart the MariaDB server. This will allow MariaDB to detect and load the new plugin.
# Example for systemd-based Linux systems
sudo systemctl restart mariadb

# Example for older init.d systems
sudo service mariadb restart
5
Verify the plugin is loaded by running the `SHOW PLUGINS;` command or re-querying `information_schema.PLUGINS`.
SHOW PLUGINS;

-- OR --

SELECT PLUGIN_NAME, STATUS FROM information_schema.PLUGINS WHERE PLUGIN_NAME = 'plugin_name_from_error';

2. Enable Plugin in MariaDB Configuration medium

Explicitly enable the plugin in the MariaDB configuration file if it's not loaded automatically.

1
Locate your MariaDB configuration file. Common locations include `/etc/my.cnf`, `/etc/mysql/my.cnf`, or files within `/etc/my.cnf.d/`.
2
Open the configuration file with a text editor (e.g., `nano`, `vim`).
sudo nano /etc/my.cnf
3
Under the `[mysqld]` section, add a line to load the specific plugin. The syntax is `plugin_load_add = plugin_name`. Replace `plugin_name` with the actual name of the plugin.
[mysqld]
plugin_load_add = plugin_name_from_error
4
Save the configuration file and restart the MariaDB server.
# Example for systemd-based Linux systems
sudo systemctl restart mariadb

# Example for older init.d systems
sudo service mariadb restart
5
Confirm the plugin is loaded using `SHOW PLUGINS;`.
SHOW PLUGINS;

3. Update MariaDB to a Compatible Version advanced

Ensure your MariaDB version supports the plugin and its dependencies.

1
Determine the MariaDB version you are currently running.
SELECT VERSION();
2
Check the documentation for the specific plugin you are trying to use. It will often specify the minimum MariaDB version required for its functionality.
3
If your MariaDB version is too old, plan and execute an upgrade to a newer, supported version. This is a significant operation and should be performed with caution, including backups and thorough testing.
4
After upgrading MariaDB, repeat the steps in 'Verify Plugin Installation and Configuration' to ensure the plugin is correctly installed and loaded in the new environment.
🔗

Related Errors

5 related errors