070608 8:00:44 [Warning] Server variable data_file_path of plugin InnoDB was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flag 070608 8:00:44 [Warning] Server variable data_home_dir of plugin InnoDB was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flag 070608 8:00:44 [Warning] Server variable flush_method of plugin InnoDB was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flag 070608 8:00:44 [Warning] Server variable log_arch_dir of plugin InnoDB was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flag 070608 8:00:44 [Warning] Server variable log_group_home_dir of plugin InnoDB was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flag InnoDB: The first specified data file ./ibdata1 did not exist: InnoDB: a new database to be created! 070608 8:00:45 InnoDB: Setting file ./ibdata1 size to 10 MB InnoDB: Database physically writes the file full: wait... 070608 8:00:46 InnoDB: Log file ./ib_logfile0 did not exist: new to be created InnoDB: Setting log file ./ib_logfile0 size to 5 MB InnoDB: Database physically writes the file full: wait... 070608 8:00:47 InnoDB: Log file ./ib_logfile1 did not exist: new to be created InnoDB: Setting log file ./ib_logfile1 size to 5 MB InnoDB: Database physically writes the file full: wait... InnoDB: Doublewrite buffer not found: creating new InnoDB: Doublewrite buffer created InnoDB: Creating foreign key constraint system tables InnoDB: Foreign key constraint system tables created 070608 8:00:48 InnoDB: Started; log sequence number 0 0 070608 8:00:49 [Note] Starting MySQL Cluster Binlog Thread 070608 8:00:49 [Note] Event Scheduler: Loaded 0 events 070608 8:00:49 [Note] /usr/local/mysql/bin/mysqld: ready for connections. Version: '5.1.19-beta-debug-log' socket: '/tmp/mysql.sock' port: 3306 MySQL Community Server (GPL) NDB: Found 3 NdbTransaction's that have not been released NDB: Found 2 NdbReceiver's that have not been released NDB: Found 4 NdbTransaction's that have not been released NDB: Found 2 NdbReceiver's that have not been released 070608 8:05:24 - mysqld got signal 10; 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=16777216 read_buffer_size=258048 max_used_connections=1 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 = 132599 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Writing a core file 070608 8:24:37 [Warning] Server variable data_file_path of plugin InnoDB was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flag 070608 8:24:37 [Warning] Server variable data_home_dir of plugin InnoDB was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flag 070608 8:24:37 [Warning] Server variable flush_method of plugin InnoDB was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flag 070608 8:24:37 [Warning] Server variable log_arch_dir of plugin InnoDB was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flag 070608 8:24:37 [Warning] Server variable log_group_home_dir of plugin InnoDB was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flag 070608 8:24:38 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... 070608 8:24:38 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 46409. InnoDB: Doing recovery: scanned up to log sequence number 0 46409 070608 8:24:39 InnoDB: Started; log sequence number 0 46409 070608 8:24:39 [Note] Starting MySQL Cluster Binlog Thread 070608 8:24:39 [Note] Recovering after a crash using mysql-bin 070608 8:24:39 [Note] Starting crash recovery... 070608 8:24:39 [Note] Crash recovery finished. 070608 8:24:40 [Note] Event Scheduler: Loaded 0 events 070608 8:24:40 [Note] /usr/local/mysql/bin/mysqld: ready for connections. Version: '5.1.19-beta-debug-log' socket: '/tmp/mysql.sock' port: 3306 MySQL Community Server (GPL) 070608 8:25:26 - mysqld got signal 10; 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=16777216 read_buffer_size=258048 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 = 132599 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Writing a core file