浅山です。いつもお世話になります。

  一旦は解決したと思ったんですが、また発生してしまいました。
  メモリ使用量を減らす方向で考えていますが、それ以外に何か手立てがあ
りましたら教えてください。


【エラー・ログ】
090528  6:46:26 - mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this 
binary
or one of the libraries it was linked against is corrupt, improperly 
built,
or misconfigured. This error can also be caused by malfunctioning 
hardware.
We will try our best to scrape up some info that will hopefully help 
diagnose
the problem, but since we have already crashed, something is 
definitely wrong
and this may fail.

key_buffer_size=536870912
read_buffer_size=2097152
max_used_connections=27
max_threads=200
threads_connected=2
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 
1344758 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x7ec0c220
Attempting backtrace. You can use the following information to find 
out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0x804563b8 thread_stack 0x30000
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x7eb7f2c0 is an invalid pointer
thd->thread_id=723
thd->killed=NOT_KILLED
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html 
contains
information that should help you find out what is causing the crash.
090528 06:46:26 mysqld_safe Number of processes running now: 0
090528 06:46:26 mysqld_safe mysqld restarted
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
090528  6:46:28  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...
090528  6:46:29  InnoDB: Started; log sequence number 0 468460087
090528  6:46:29 [Note] Event Scheduler: Loaded 0 events
090528  6:46:29 [Note] /opac/pp/mysql/bin/bin/mysqld: ready for 
connections.
Version: '5.1.32'  socket: '/tmp/mysql.sock'  port: 3306  MySQL 
Community Server (GPL)


In message "[mysql 14888] Re: バッチ処理のUPDATEでmysqld got signal  
11が発生する",
浅山雄三様wrote...
 >  浅山です。いつもお世話になります。
 >
 > >key_buffer_size=2147483648　←2GB
 > >
 > >このkey_buffer_sizeを1.5GBあるいは1GBくらいに減らして
 > >見てはどうでしょう。
 >
 >  512MBにしてみたところ、SIGNAL11は発生しませんでした。
 >
 >  ということで解決しました。皆様ありがとうございました。
 >
 >（※バッチを何本もはしらせたので返事がおそくなってしまいました。）
 >
 >
 > 2009年5月27日 09:19:43 (^o^)浅山雄三
 >
 >
 >
 >
 >


 2009年5月28日 12:46:16 (^o^)浅山雄三