Bug #66564 | mysql restars in middle of long run query | ||
---|---|---|---|
Submitted: | 28 Aug 2012 6:05 | Modified: | 30 Sep 2012 14:51 |
Reporter: | ramakrishna v | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server | Severity: | S2 (Serious) |
Version: | 5.5.23 | OS: | Linux (ubuntu) |
Assigned to: | CPU Architecture: | Any | |
Tags: | log was like this at next time execution |
[28 Aug 2012 6:05]
ramakrishna v
[28 Aug 2012 6:19]
ramakrishna v
log file of mysql
Attachment: log (application/octet-stream, text), 26.75 KiB.
[28 Aug 2012 6:59]
Valeriy Kravchuk
Sorry, but I see just normal shutdown: 120827 11:32:08 [Note] /usr/libexec/mysqld: Normal shutdown that was caused externally by some person or software. This is not a crash. Do you have any monitoring software that checks MySQL server status or something like that? How exactly to repeat this problem on a clean, just installed MySQL server (better of a recent version, 5.5.27)?
[28 Aug 2012 7:17]
ramakrishna v
i dont have any monitoring tool
[28 Aug 2012 8:23]
Valeriy Kravchuk
Still I do not see any crash or any other indication of a bug. We need to know how to provoke this restart.
[28 Aug 2012 12:38]
ramakrishna v
hi Kravchuk i installed the MonYog tool to monitor MySql database could you pls guide me
[28 Aug 2012 14:56]
ramakrishna v
120112 20:21:59 [Note] Plugin 'FEDERATED' is disabled. 120112 20:21:59 InnoDB: Initializing buffer pool, size = 8.0M 120112 20:21:59 InnoDB: Completed initialization of buffer pool InnoDB: The log sequence number in ibdata files does not match InnoDB: the log sequence number in the ib_logfiles! 120112 20:22:00 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... 120112 20:22:03 InnoDB: Started; log sequence number 0 111674556 120112 20:22:04 [Note] Event Scheduler: Loaded 0 events 120112 20:22:04 [Note] C:\Program Files (x86)\acquia-drupal\mysql\bin\mysqld.exe: ready for connections. Version: '5.1.59-community' socket: '' port: 33066 MySQL Community Server (GPL)
[31 Aug 2012 14:51]
MySQL Verification Team
Looks like something kill mysqld process. Most probable is configuration tries to over-allocate memory, and kernel terminates it. Please halve the innodb_buffer_pool_size and key_buffer_size and if the problem re-occurs, upload /var/log/messages* in compressed format. Thanks,
[1 Oct 2012 1: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".