Great!

Please follow the instruction at http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html

And resolve the stack trace. One you have that, please go to http://bugs.mysql.com/ And file a bug report. Please include as much detailed information as possible.

Thanks,

Jonathan Miller Austin, Texas USA Senior Lead Quality Assurance Developer MySQL AB www.mysql.com __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / / /|_/ / // /\ \/ /_/ / /__ /_/ /_/\_, /___/\___\_\___/ <___/ www.mysql.com

Jumpstart your cluster! http://www.mysql.com/consulting/packaged/cluster.html

Get training on clusters http://www.mysql.com/training/courses/mysql_cluster.html

All-in-one Enterprise-grade Database, Support and Services http://www.mysql.com/network/

-> -----Original Message----- -> From: Christian Schramm [mailto:mail...@dretschler.com] -> Sent: Friday, July 28, 2006 8:47 AM -> To: Jonathan Miller -> Cc: clus...@lists.mysql.com -> Subject: Re: Strange error on cluster logs -> -> It's very strange because it only happens sometimes. Here is what i -> found in the error log: -> -> 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=16777216 -> read_buffer_size=258048 -> max_used_connections=354 -> max_connections=1000 -> threads_connected=4 -> It is possible that mysqld could use up to -> key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections -> = 780376 -> K -> bytes of memory -> Hope that's ok; if not, decrease some variables in the equation. -> -> thd=0xab06b928 -> 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=0xa9b9bbd4, backtrace may not be correct. -> Stack range sanity check OK, backtrace follows: -> 0x818282d -> 0xffffe420 -> 0xf31acc8 -> 0x8232edc -> 0x8232966 -> 0x8236dd9 -> 0x81bb699 -> 0x81bc684 -> 0x81b9622 -> 0x8192f20 -> 0x8198f97 -> 0x8191ac2 -> 0x81915bb -> 0x8190ca4 -> 0xb7dc3aba -> 0xb7c3c1fe -> 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 -> Trying to get some variables. -> Some pointers may be invalid and cause the dump to abort... -> thd->query at 0xab44288 = SELECT *, -> `TABLE_SCHEMA` AS `Db`, -> `TABLE_NAME` AS `Name`, -> `ENGINE` AS `Engine`, -> `ENGINE` AS `Type`, -> `VERSION` AS `Version`, -> `ROW_FORMAT` AS `Row_format`, -> `TABLE_ROWS` AS `Rows`, -> `AVG_ROW_LENGTH` AS `Avg_row_length`, -> `DATA_LENGTH` AS `Data_length`, -> `MAX_DATA_LENGTH` AS `Max_data_length`, -> `INDEX_LENGTH` AS `Index_length`, -> `DATA_FREE` AS `Data_free`, -> `AUTO_INCREMENT` AS `Auto_increment`, -> `CREATE_TIME` AS `Create_time`, -> `UPDATE_TIME` AS `Update_time`, -> `CHECK_TIME` AS `Check_time`, -> `TABLE_COLLATION` AS `Collation`, -> `CHECKSUM` AS ` -> thd->thread_id=13100143 -> 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 -> 060728 10:52:58 mysqld restarted -> 060728 10:52:58 [Warning] No argument was provided to --log-bin, and --lo -> ndex was not used; so replication may break when this MySQL server acts a -> ter and has his hostname changed!! Please use '--log-bin=myapi1-bin' to a -> is problem. -> 060728 10:52:58 InnoDB: Started; log sequence number 1 3405068341 -> 060728 10:53:02 [Note] Recovering after a crash using myapi1-bin -> 060728 10:53:12 [Note] Starting crash recovery... -> 060728 10:53:12 [Note] Crash recovery finished. -> 060728 10:53:13 [Note] /usr/sbin/mysqld: ready for connections. -> Version: '5.0.18-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 -> Linux mysql-5.0.18 -> -> Jonathan Miller schrieb: -> > Usually, "Lost connection to MySQL server" means that a MySQLD process -> has -> > crashed. Can you check your MySQLD error log for a stack trace? -> > -> > Thanks, -> > -> > Jonathan Miller -> > Austin, Texas USA -> > Senior Lead Quality Assurance Developer -> > MySQL AB www.mysql.com -> > __ ___ ___ ____ __ -> > / |/ /_ __/ __/ __ \/ / -> > / /|_/ / // /\ \/ /_/ / /__ -> > /_/ /_/\_, /___/\___\_\___/ -> > <___/ www.mysql.com -> > -> > Jumpstart your cluster! -> > http://www.mysql.com/consulting/packaged/cluster.html -> > -> > Get training on clusters -> > http://www.mysql.com/training/courses/mysql_cluster.html -> > -> > All-in-one Enterprise-grade Database, Support and Services -> > http://www.mysql.com/network/ -> > -> -----Original Message----- -> > -> From: Christian Schramm [mailto:mail...@dretschler.com] -> > -> Sent: Friday, July 28, 2006 4:14 AM -> > -> To: clus...@lists.mysql.com -> > -> Subject: Strange error on cluster logs -> > -> -> > -> Hi! -> > -> -> > -> We're using a mySQL-Cluster consisting of 2 API servers and 2 nodes -> for -> > -> production since some months. -> > -> So far we don't have problems since all queries are optimized. -> > -> -> > -> Today I noticed some strange messages in the log: -> > -> -> > -> 2006-07-28 10:52:18 [MgmSrvr] INFO -- Node 10: Local checkpoint -> 30064 -> > -> started. Keep GCI = 6591020 oldest restorable GCI = 6591173 -> > -> 2006-07-28 10:52:58 [MgmSrvr] ALERT -- Node 11: Node 20 -> Disconnected -> > -> 2006-07-28 10:52:58 [MgmSrvr] INFO -- Node 11: Communication to -> Node -> > -> 20 closed -> > -> 2006-07-28 10:52:58 [MgmSrvr] ALERT -- Node 10: Node 20 -> Disconnected -> > -> 2006-07-28 10:52:58 [MgmSrvr] INFO -- Node 10: Communication to -> Node -> > -> 20 closed -> > -> 2006-07-28 10:52:58 [MgmSrvr] INFO -- Mgmt server state: nodeid -> 20 -> > -> freed, m_reserved_nodes 0000000000200002. -> > -> 2006-07-28 10:52:58 [MgmSrvr] WARNING -- Allocate nodeid (20) -> failed. -> > -> Connection from ip 192.168.95.11. Returned error string "Id 20 -> already -> > -> allocated by another node." -> > -> 2006-07-28 10:52:58 [MgmSrvr] INFO -- Mgmt server state: node -> id's -> > -> 10 11 20 connected but not reserved -> > -> 2006-07-28 10:52:58 [MgmSrvr] INFO -- Mgmt server state: node -> id's 1 -> > -> not connected but reserved -> > -> 2006-07-28 10:53:01 [MgmSrvr] INFO -- Node 11: Communication to -> Node -> > -> 20 opened -> > -> 2006-07-28 10:53:01 [MgmSrvr] INFO -- Node 10: Communication to -> Node -> > -> 20 opened -> > -> 2006-07-28 10:53:01 [MgmSrvr] INFO -- Mgmt server state: nodeid -> 20 -> > -> reserved for ip 192.168.95.11, m_reserved_nodes 0000000000300002. -> > -> 2006-07-28 10:53:02 [MgmSrvr] INFO -- Node 10: Node 20 Connected -> > -> 2006-07-28 10:53:02 [MgmSrvr] INFO -- Node 11: Node 20 Connected -> > -> 2006-07-28 10:53:02 [MgmSrvr] INFO -- Node 10: Node 20: API -> version -> > -> 5.0.18 -> > -> 2006-07-28 10:53:02 [MgmSrvr] INFO -- Node 11: Node 20: API -> version -> > -> 5.0.18 -> > -> 2006-07-28 10:57:47 [MgmSrvr] INFO -- Node 10: Local checkpoint -> 30065 -> > -> started. Keep GCI = 6591174 oldest restorable GCI = 6591329 -> > -> -> > -> I noticed that there have been some mySQL errors in this time: -> > -> Error code: 2013 -> > -> Error description: Lost connection to MySQL server during query -> > -> Server: CLUSTER -> > -> -> > -> Does anyone know what may have caused this error? -> > -> I noticed that this does not happen very often, but i'd like to know -> why -> > -> this happens. -> > -> -> > -> We are using mySQL version 5.0.18 (OS: Gentoo) on the API servers; -> > -> RedHat Enterprise as OS on the nodes. -> > -> -> > -> Regards -> > -> -> > -> Christian Schramm -> > -> -> > -> -> > -> -- -> > -> MySQL Cluster Mailing List -> > -> For list archives: http://lists.mysql.com/cluster -> > -> To unsubscribe: -> > -> http://lists.mysql.com/cluster?unsub=jbmi...@mysql.com -> > -> > -> > -> -> -> -- -> MySQL Cluster Mailing List -> For list archives: http://lists.mysql.com/cluster -> To unsubscribe: -> http://lists.mysql.com/cluster?unsub=jbmi...@mysql.com