Bug #66564 mysql restars in middle of long run query

Description:
mysql shutdown and restarts in safe mode in middle of long running query exection  
mysql log is :

120827  8:31:20  InnoDB: Starting shutdown...
120827  8:31:21  InnoDB: Waiting for 200 pages to be flushed
120827  8:31:22  InnoDB: Shutdown completed; log sequence number 43224904608
120827  8:31:22 [Note] /usr/libexec/mysqld: Shutdown complete

120827 08:31:22 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
120827 08:31:25 mysqld_safe Starting mysqld daemon with databases from /ebsmnt/mysql
120827  8:31:25 [Warning] options --log-slow-admin-statements, --log-queries-not-using-indexes and --log-slow-slave-statements have no effect if --log_slow_queries is not set
120827  8:31:25 [Note] Plugin 'FEDERATED' is disabled.
120827  8:31:25 InnoDB: The InnoDB memory heap is disabled
120827  8:31:25 InnoDB: Mutexes and rw_locks use GCC atomic builtins
120827  8:31:25 InnoDB: Compressed tables use zlib 1.2.3
120827  8:31:25 InnoDB: Using Linux native AIO
120827  8:31:25 InnoDB: Initializing buffer pool, size = 128.0M
120827  8:31:25 InnoDB: Completed initialization of buffer pool
120827  8:31:25 InnoDB: highest supported file format is Barracuda.
120827  8:31:25  InnoDB: Waiting for the background threads to start
120827  8:31:26 InnoDB: 1.1.8 started; log sequence number 43224904608
120827  8:31:26 [Note] Event Scheduler: Loaded 0 events
120827  8:31:26 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.5.23'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MySQL Community Server (GPL) by Remi

How to repeat:
mysql restarted after one hour from query execution

log file of mysql

Attachment: log (application/octet-stream, text), 26.75 KiB.

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)?

i dont have any monitoring tool

Still I do not see any crash or any other indication of a bug. We need to know how to provoke this restart.

hi Kravchuk  i installed the MonYog tool to monitor MySql database could you pls guide me

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)

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,

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".