INVALID SUB_GCP_COMPLETE_REP
gci: 4194
sender: 1010004
count: 3
bucket count: 2
nodes: 3
mysqld got signal 6;
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=8388600
read_buffer_size=131072
max_used_connections=2
max_connections=100
threads_connected=2
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 225791 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=(nil)
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...
Cannot determine thread, fp=0x22cbd8, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x81d02a8
0xd17420
(nil)
0x84302a8
0x841d3a4
0x841c231
0x847203a
0x847ad4c
0x847959b
0x8472575
0x847245f
0x8462584
0xbfd341
0xa694ee
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.

Number of processes running now: 0
060922 02:50:47  mysqld restarted
060922  2:50:47  InnoDB: Started; log sequence number 0 46403
060922  2:50:53 [Note] Starting MySQL Cluster Binlog Thread
/opt/mysql/bin/mysqld: Table 'general_log' is marked as crashed and should be repaired
/opt/mysql/bin/mysqld: Table 'slow_log' is marked as crashed and should be repaired
060922  2:50:53 [Note] /opt/mysql/bin/mysqld: ready for connections.
Version: '5.1.11-beta'  socket: '/tmp/mysql.sock'  port: 3306  MySQL Community Server (GPL)
060922  2:50:53 [Note] SCHEDULER: Manager thread booting
060922  2:50:53 [Note] SCHEDULER: Loaded 0 events
060922  2:50:53 [Note] SCHEDULER: Suspending operations
INVALID SUB_GCP_COMPLETE_REP
gci: 4209
sender: 1010004
count: 3
bucket count: 2
nodes: 3
mysqld got signal 6;
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=8388600
read_buffer_size=131072
max_used_connections=0
max_connections=100
threads_connected=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 225791 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=(nil)
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...
Cannot determine thread, fp=0x349bd8, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x81d02a8
0xdce420
(nil)
0x84302a8
0x841d3a4
0x841c231
0x847203a
0x847ad4c
0x847959b
0x8472575
0x847245f
0x8462584
0xbc0341
0x9554ee
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.

Number of processes running now: 0
060922 02:51:19  mysqld restarted
060922  2:51:20  InnoDB: Started; log sequence number 0 46403
060922  2:51:26 [Note] Starting MySQL Cluster Binlog Thread
/opt/mysql/bin/mysqld: Table 'general_log' is marked as crashed and should be repaired
/opt/mysql/bin/mysqld: Table 'slow_log' is marked as crashed and should be repaired
060922  2:51:26 [Note] /opt/mysql/bin/mysqld: ready for connections.
Version: '5.1.11-beta'  socket: '/tmp/mysql.sock'  port: 3306  MySQL Community Server (GPL)
060922  2:51:26 [Note] SCHEDULER: Manager thread booting
060922  2:51:26 [Note] SCHEDULER: Loaded 0 events
060922  2:51:26 [Note] SCHEDULER: Suspending operations