Bug #18278 | Server crashes when EVENT parameters are changed | ||
---|---|---|---|
Submitted: | 16 Mar 2006 12:45 | Modified: | 26 May 2006 9:13 |
Reporter: | NOT_FOUND NOT_FOUND | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server | Severity: | S3 (Non-critical) |
Version: | 5.1.7-beta-nt | OS: | Windows (Windows 2000) |
Assigned to: | CPU Architecture: | Any |
[16 Mar 2006 12:45]
NOT_FOUND NOT_FOUND
[16 Mar 2006 13:52]
Valeriy Kravchuk
Thank you for a problem report. Please, send the CREATE EVENT statement, for completeness of your test. As MySQL server spontaneously shutted down, according to your description, there should be something written to the error log. Please, send the appropriate part of the error log.
[16 Mar 2006 22:52]
NOT_FOUND NOT_FOUND
Here is ravine, but in him nor word is said about that that MySQL terminated its work... Day several times contract was received removing MySQL from building, but now is not received ( strange, vastly strange... 060316 10:18:44 [Note] SCHEDULER: Executing event megacms.megacms_content_mtime of root@localhost [EXPR:1] 060316 10:18:44 [Note] SCHEDULER: Executing event megacms.megacms_sessions_purge of root@localhost [EXPR:1] 060316 10:18:44 [Note] SCHEDULER: Executed event megacms.megacms_sessions_purge of root@localhost [EXPR:1]. RetCode=0 060316 10:18:44 [Note] SCHEDULER: Executing event megacms.megacms_sessions_ctime of root@localhost [EXPR:1] 060316 10:18:44 [Note] SCHEDULER: Executed event megacms.megacms_sessions_ctime of root@localhost [EXPR:1]. RetCode=0 060316 10:18:44 [Note] SCHEDULER: Executing event megacms.megacms_content_ctime of root@localhost [EXPR:1] 060316 10:18:44 [Note] SCHEDULER: Executed event megacms.megacms_content_ctime of root@localhost [EXPR:1]. RetCode=0 060316 10:18:44 [Note] SCHEDULER: Executed event megacms.megacms_content_mtime of root@localhost [EXPR:1]. RetCode=0 060316 11:18:50 [Note] SCHEDULER: Executing event megacms.megacms_content_ctime of root@localhost [EXPR:1] 060316 11:18:50 [Note] SCHEDULER: Executing event megacms.megacms_sessions_purge of root@localhost [EXPR:1] 060316 11:18:50 [Note] SCHEDULER: Executed event megacms.megacms_sessions_purge of root@localhost [EXPR:1]. RetCode=0 060316 11:18:50 [Note] SCHEDULER: Executing event megacms.megacms_content_mtime of root@localhost [EXPR:1] 060316 11:18:50 [Note] SCHEDULER: Executing event megacms.megacms_sessions_ctime of root@localhost [EXPR:1] 060316 11:18:50 [Note] SCHEDULER: Executed event megacms.megacms_sessions_ctime of root@localhost [EXPR:1]. RetCode=0 060316 11:18:50 [Note] SCHEDULER: Executed event megacms.megacms_content_ctime of root@localhost [EXPR:1]. RetCode=0 060316 11:18:50 [Note] SCHEDULER: Executed event megacms.megacms_content_mtime of root@localhost [EXPR:1]. RetCode=0 060316 12:18:55 [Note] SCHEDULER: Executing event megacms.megacms_sessions_ctime of root@localhost [EXPR:1] 060316 12:18:55 [Note] SCHEDULER: Executing event megacms.megacms_sessions_purge of root@localhost [EXPR:1] 060316 12:18:55 [Note] SCHEDULER: Executing event megacms.megacms_content_ctime of root@localhost [EXPR:1] 060316 12:18:55 [Note] SCHEDULER: Executing event megacms.megacms_content_mtime of root@localhost [EXPR:1] 060316 12:18:55 [Note] SCHEDULER: Executed event megacms.megacms_sessions_purge of root@localhost [EXPR:1]. RetCode=0 060316 12:18:55 [Note] SCHEDULER: Executed event megacms.megacms_sessions_ctime of root@localhost [EXPR:1]. RetCode=0 060316 12:18:55 [Note] SCHEDULER: Executed event megacms.megacms_content_ctime of root@localhost [EXPR:1]. RetCode=0 060316 12:18:55 [Note] SCHEDULER: Executed event megacms.megacms_content_mtime of root@localhost [EXPR:1]. RetCode=0 060316 13:19:44 [Note] SCHEDULER: Executing event megacms.megacms_content_mtime of root@localhost [EXPR:1] 060316 13:19:44 [Note] SCHEDULER: Executing event megacms.megacms_sessions_purge of root@localhost [EXPR:1] 060316 13:19:44 [Note] SCHEDULER: Executing event megacms.megacms_sessions_ctime of root@localhost [EXPR:1] 060316 13:19:44 [Note] SCHEDULER: Executing event megacms.megacms_content_ctime of root@localhost [EXPR:1] 060316 13:19:45 [Note] SCHEDULER: Executed event megacms.megacms_sessions_purge of root@localhost [EXPR:1]. RetCode=0 060316 13:19:45 [Note] SCHEDULER: Executed event megacms.megacms_sessions_ctime of root@localhost [EXPR:1]. RetCode=0 060316 13:19:46 [Note] SCHEDULER: Executed event megacms.megacms_content_ctime of root@localhost [EXPR:1]. RetCode=0 060316 13:19:46 [Note] SCHEDULER: Executed event megacms.megacms_content_mtime of root@localhost [EXPR:1]. RetCode=0 060316 14:20:07 [Note] SCHEDULER: Executing event megacms.megacms_content_ctime of root@localhost [EXPR:1] 060316 14:20:07 [Note] SCHEDULER: Executing event megacms.megacms_sessions_purge of root@localhost [EXPR:1] 060316 14:20:07 [Note] SCHEDULER: Executing event megacms.megacms_sessions_ctime of root@localhost [EXPR:1] 060316 14:20:07 [Note] SCHEDULER: Executing event megacms.megacms_content_mtime of root@localhost [EXPR:1] 060316 14:20:08 [Note] SCHEDULER: Executed event megacms.megacms_sessions_ctime of root@localhost [EXPR:1]. RetCode=0 060316 14:20:08 [Note] SCHEDULER: Executed event megacms.megacms_content_mtime of root@localhost [EXPR:1]. RetCode=0 060316 14:20:08 [Note] SCHEDULER: Executed event megacms.megacms_sessions_purge of root@localhost [EXPR:1]. RetCode=0 060316 14:20:08 [Note] SCHEDULER: Executed event megacms.megacms_content_ctime of root@localhost [EXPR:1]. RetCode=0
[16 Mar 2006 22:53]
NOT_FOUND NOT_FOUND
The Source description of the event: CREATE EVENT `megacms`.`megacms_content_mtime` ON SCHEDULE EVERY 1 HOUR ON COMPLETION NOT PRESERVE ENABLE COMMENT 'MEGAcms content Modify time' DO UPDATE `megacms`.`megacms_content` SET `MD5` = MD5(`xml`), `CRC32` = CRC32(`xml`), `mtime` = UNIX_TIMESTAMP(NOW()) WHERE CRC32(`xml`) <> `CRC32`;
[26 Apr 2006 9:13]
Valeriy Kravchuk
Please, send the SHOW CREATE TABLE and SHOW TABLE STATUS results for the `megacms`.`megacms_content` table. Also try to repeat with a newer version, 5.1.9 beat, and inform about the results.
[26 May 2006 23:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".