# SQL Error Log System Variables and Options

This page documents system variables and options related to the [SQL\_Error\_Log Plugin](/docs/server/server-management/server-monitoring-logs/sql-error-log-plugin.md). See [Server System Variables](/docs/server/server-management/variables-and-modes/server-system-variables.md) for a complete list of system variables and instructions on setting them.

See also the [Full list of MariaDB options, system and status variables](/docs/server/server-management/variables-and-modes/full-list-of-mariadb-options-system-and-status-variables.md).

## Options

#### `sql_error_log`

* Description: Controls how the server should treat the plugin when the server starts up.
  * Valid values are:
    * `OFF` - Disables the plugin without removing it from the [mysql.plugins](/docs/server/reference/system-tables/the-mysql-database-tables/mysql-plugin-table.md) table.
    * `ON` - Enables the plugin. If the plugin cannot be initialized, then the server will still continue starting up, but the plugin will be disabled.
    * `FORCE` - Enables the plugin. If the plugin cannot be initialized, then the server will fail to start with an error.
    * `FORCE_PLUS_PERMANENT` - Enables the plugin. If the plugin cannot be initialized, then the server will fail to start with an error. In addition, the plugin cannot be uninstalled with [UNINSTALL SONAME](/docs/server/reference/sql-statements/administrative-sql-statements/plugin-sql-statements/uninstall-soname.md) or [UNINSTALL PLUGIN](/docs/server/reference/sql-statements/administrative-sql-statements/plugin-sql-statements/uninstall-plugin.md) while the server is running.
  * See [Plugin Overview: Configuring Plugin Activation at Server Startup](/docs/server/reference/plugins/plugin-overview.md#configuring-plugin-activation-at-server-startup) for more information.
* Command line: `--sql-error-log=value`
* Data Type: `enumerated`
* Default Value: `ON`
* Valid Values: `OFF`, `ON`, `FORCE`, `FORCE_PLUS_PERMANENT`

## System Variables

#### `sql_error_log_filename`

* Description: The name (and optionally path) of the logfile containing the errors. Rotation will use a naming convention such as `sql_error_log_filename.001`. If no path is specified, the log file will be written to the [data directory](/docs/server/server-management/variables-and-modes/server-system-variables.md#datadir).
* Command line: `--sql-error-log-filename=value`
* Scope: Global
* Dynamic: No
* Data Type: `string`
* Default Value: `sql_errors.log`

#### `sql_error_log_rate`

* Description: The logging sampling rate. Setting to `10`, for example, means that one in ten errors will be logged. If set to zero, logging is disabled. The default, `1`, logs every error.
* Command line: `--sql-error-log-rate=#`
* Scope: Global
* Dynamic: Yes
* Data Type: `numeric`
* Default Value: `1`

#### `sql_error_log_rotate`

* Description: Setting to #1`forces log rotation.`
* Command line: `--sql-error-log-rate[={0|1}]`
* Scope: Global
* Dynamic: Yes
* Data Type: `boolean`
* Default Value: `OFF`

#### `sql_error_log_rotations`

* Description: Number of rotations before the log is removed. When rotated, the current log file is stored and a new, empty, log is created. Any rotations older than this setting are removed.
* Command line: `--sql-error-log-rotations=#`
* Scope: Global
* Dynamic: Yes
* Data Type: `numeric`
* Default Value: `9`
* Range: `1` to `999`

#### `sql_error_log_size_limit`

* Description: The log file size limit in bytes. After reaching this size, the log file is rotated.
* Command line: `--sql-error-log-size-limit=#`
* Scope: Global
* Dynamic: No
* Data Type: `numeric`
* Default Value: `1000000`
* Range: `100` to `9223372036854775807`

#### `sql_error_log_warnings`

* Description: If set, log warnings in addition to errors.
* Command line: `--sql-error-log-warnings={0,1}`
* Scope: Global
* Dynamic: Yes
* Data Type: `boolean`
* Default Value: `ON`
* Introduced: [MariaDB 10.11.5](/docs/release-notes/community-server/10.11/10.11.5.md)

#### `sql_error_log_with_db_and_thread_info`

* Description: If enabled, it prints the database name and the thread ID in the log in addition to already existing columns.
* Command line: `--sql-error-log-with-db-and-thread-info=value`
* Scope: Global
* Dynamic: No
* Data Type: `boolean`
* Default Value: `OFF`
* Introduced: [MariaDB 10.6.17](/docs/release-notes/community-server/10.6/10.6.17.md), [MariaDB 10.11.7](/docs/release-notes/community-server/10.11/10.11.7.md), [MariaDB 11.0.5](/docs/release-notes/community-server/old-releases/11.0/11.0.5.md), [MariaDB 11.1.4](/docs/release-notes/community-server/old-releases/11.1/11.1.4.md), [MariaDB 11.2.3](/docs/release-notes/community-server/old-releases/11.2/11.2.3.md)

<sub>*This page is licensed: CC BY-SA / Gnu FDL*</sub>

{% @marketo/form formId="4316" %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://mariadb.com/docs/server/ha-and-performance/optimization-and-tuning/system-variables/sql-error-log-system-variables-and-options.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.