I currently see that the mysql-nodes go away. The mysql log is below.

Why dies mysqld and tries to restart and dies again.

Thanks for any help appreciated.

- tom

080129 21:12:58 mysqld_safe Number of processes running now: 0 080129 21:12:58 mysqld_safe mysqld restarted 080129 21:12:58 InnoDB: Started; log sequence number 0 46409 080129 21:13:02 [Note] Starting MySQL Cluster Binlog Thread 080129 21:13:02 [Note] Event Scheduler: Loaded 0 events 080129 21:13:02 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.1.22-rc' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL) INVALID SUB_GCP_COMPLETE_REP gci: 41293 sender: 101000d count: 4 bucket count: 2 nodes: 3 080129 21:13:02 - 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_threads=151 threads_connected=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338151 K bytes of memory Hope that's ok; if not, decrease some variables in the equation.

thd: 0x0 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... frame pointer is NULL, did you compile with -fomit-frame-pointer? Aborting backtrace! 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. 080129 21:13:02 mysqld_safe Number of processes running now: 0 080129 21:13:02 mysqld_safe mysqld restarted 080129 21:13:02 InnoDB: Started; log sequence number 0 46409

-- www.tiri.li - www.1-search.de - www.linkarchiv.at

---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.