Details
Description
The server throws a somewhat nonsensical error message if an event is created when event_scheduler = DISABLED. For example:
MariaDB [(none)]> SHOW GLOBAL VARIABLES LIKE 'event_scheduler';
|
+-----------------+----------+
|
| Variable_name | Value |
|
+-----------------+----------+
|
| event_scheduler | DISABLED |
|
+-----------------+----------+
|
1 row in set (0.00 sec)
|
|
MariaDB [(none)]> CREATE EVENT db1.myevent
|
-> ON SCHEDULE AT CURRENT_TIMESTAMP + INTERVAL 1 HOUR
|
-> DO SELECT NOW();
|
ERROR 1577 (HY000): Cannot proceed because system tables used by Event Scheduler were found damaged at server start
|
The same nonsensical error message is thrown if SHOW EVENTS is executed or if information_schema.EVENTS is queried. For example:
MariaDB [db1]> SHOW GLOBAL VARIABLES LIKE 'event_scheduler';
|
+-----------------+----------+
|
| Variable_name | Value |
|
+-----------------+----------+
|
| event_scheduler | DISABLED |
|
+-----------------+----------+
|
1 row in set (0.01 sec)
|
|
MariaDB [db1]> SHOW EVENTS;
|
ERROR 1577 (HY000): Cannot proceed because system tables used by Event Scheduler were found damaged at server start
|
MariaDB [db1]> SELECT EVENT_SCHEMA, EVENT_NAME FROM information_schema.EVENTS;
|
ERROR 1577 (HY000): Cannot proceed because system tables used by Event Scheduler were found damaged at server start
|
The error message should say something like "Cannot proceed because event scheduler is DISABLED."
Attachments
Issue Links
- causes
-
MDEV-29827 Misleading error messages about event scheduler when using --skip-grant-tables
- Closed
- is duplicated by
-
MDEV-17718 Setting event_scheduler to DISABLED causes bogus corruption errors
- Closed
- relates to
-
MDEV-19265 Server should throw warning if event is created and event_scheduler = OFF
- Closed