|
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=134217728
read_buffer_size=2093056
max_used_connections=3
max_connections=100
threads_connected=3
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size +
sort_buffer_size)*max_connections = 540271 K
bytes of memory
Hope that's ok; if not, decrease some variables in the
equation.
Number of processes running now: 0
050526 03:20:48 mysqld restarted
050526 3:20:48 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...
050526 3:20:48 InnoDB: Starting log scan based on checkpoint
at
InnoDB: log sequence number 0 43644.
InnoDB: Doing recovery: scanned up to log sequence number 0
43644
050526 3:20:48 InnoDB: Flushing modified pages from the buffer
pool...
050526 3:20:48 InnoDB: Started; log sequence number 0 43644
/usr/local/mysql/bin/mysqld: ready for connections.
Version: '4.1.11-cluster' socket: '/tmp/mysql.sock' port: 3306
MySQL Cluster (Commercial)
위의 내용을 [노드이름].err에 뿌리면서 어플리케이션에서는
커넥션을 못하는데요..
로그상에서는 mysqld가 죽었다가 다시 살아나는 것 같습니다..
버전은 4.1.11에 엔진은 클러스터(ndb)를 사용하고있구요..
데이타 베이스에 테이블의 갯수가 80개 좀 안되구요.. 각 테이블마다
TINYBLOB필드가 2개씩 있습니다.
테이블에 TINYBLOB필드가 없을때는 괜찮았는데, 2필드를 추가하면서
이런 현상이 벌어졌는데요..
|
