Bug #30173 mysqld started failed with READ_ONLY in my.cnf
Submitted: 1 Aug 2007 9:13 Modified: 15 Oct 2007 14:50
Reporter: Gu Lei Email Updates:
Status: Duplicate Impact on me:
Category:MySQL Server: Packaging Severity:S2 (Serious)
Version:5.1.20 OS:Linux
Assigned to: CPU Architecture:Any
Tags: read_only, regression

[1 Aug 2007 9:13] Gu Lei
mysqld started failed with following messages in error log:

070801 16:26:59  InnoDB: Started; log sequence number 4 4256520094
070801 16:26:59 [ERROR] Event Scheduler: Failed to open table mysql.event
070801 16:26:59 [ERROR] Event Scheduler: Error while loading from disk.
070801 16:26:59 [Note] Event Scheduler: Purging the queue. 0 events
070801 16:26:59 [ERROR] Aborting

mysqld started successfully after I removed read_only from my.cnf

OS is Redhat Linux:
Linux lnxstby64.no.sohu.com 2.6.9-55.ELsmp #1 SMP Fri Apr 20 16:36:54 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux

How to repeat:
Just put read_only in my.cnf.
[1 Aug 2007 10:39] Sveta Smirnova
Thank you for the report.

Bug is not repeatable with current sources, although it is exists in version 5.1.20 Please wait next release.

If necessary, you can access the source repository and build the latest available version, including the bug fix. More information about accessing the source trees is available at

[30 Aug 2007 7:06] Matt Lohier

I confirm that issue with release 5.1.21.

It was very frustrating having that error since i believed the server had crashed in result of rebooting and upgrade from 5.1.17 to 5.1.21. There's been a lot of attempt to repair/import the event table in safe-mode before i found that bug report and remove the read-only entry from my slave replica.

Thank you for putting a fix for that asap.
[15 Oct 2007 14:50] Alexander Nozdrin
This is a duplicate of BUG#31111.

It is in the current 5.1 tree.
The bug depends on the configuration options.