MySQL Bugs: #24425: Unable to start event scheduler

Bug #24425	Unable to start event scheduler
Submitted:	19 Nov 2006 7:20	Modified:	22 Nov 2006 9:20
Reporter:	John Zastrow	Email Updates:
Status:	Duplicate
Category:	Server	Severity:	S2 (Serious)
Version:	5.1.12-beta-community-nt-log	OS:	Microsoft Windows (Windows XP sp2)
Assigned to:		Target Version:

Description:
Attempting to run through the event tutorial at
http://dev.mysql.com/tech-resources/articles/event-feature.html I found that I cannot
enable events in 5.1.12. Following the instructions in the guide crashes the server.

Multiple attempts to set the scheduler through:

SET GLOBAL event_scheduler = 1;

then
SHOW VARIABLES LIKE 'event_scheduler';

always crash the server

How to repeat:

1) Downloaded mysql server 5.1.12-beta-community-nt-log on 19-Nov-06. Installed with
defaults on Windows XP sp2. 

2) Downloaded and installed the GUI toolkit
2b) Enabled error, slow query, and update logs through MySQL Administrator.
2c) restarted mysql server

3) Executed the following SQL through SQLyog Community edition connecting as root:
SET GLOBAL event_scheduler = 1;

4) server service crashed.
4b) was unable to restart server from MySQL Administrator, restarted from Windows
services.

From the error log:

Version: '5.1.12-beta-community-nt-log'  socket: ''  port: 3306  MySQL Community Server
(GPL)
061119  2:09:02 [ERROR] SCHEDULER: Table mysql.event is damaged. Can not open
061119  2:09:02 [Note] SCHEDULER: Purging queue. 0 events
061119  2:09:02 [ERROR] SCHEDULER: Error while loading from disk.

Thank you for a problem report. If you used installer package, it is surely a duplicate of
bug #24022.

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/17201

ChangeSet@1.2357, 2006-12-20 10:54:41+01:00, joerg@trift2. +1 -0
  Disable test "im_deamon_life_cycle", Bug#24425, see note: [19 Dec 23:17] Trudy Pelzer

Sorry for the above note, it results just from a typing error in the commit message. That
test disabling has *no* relation to this bug here.