Bug #39164 Server crashes while it connects to cluster ("ndb_not_readonly.inc")
Submitted: 1 Sep 2008 16:22 Modified: 13 Apr 2010 6:36
Reporter: Joerg Bruehe Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S1 (Critical)
Version:mysql-5.1-telco-6.3 OS:Linux (RPM SuSE 9 x86_64)
Assigned to: Magnus BlÄudd CPU Architecture:Any
Tags: mysql-5.1-telco-6.3 -> 6.3.17

[1 Sep 2008 16:22] Joerg Bruehe
Description:
This bug happened during the tests of the cluster 6.3.17 build,
which is based on the main tree as of version 5.1.27.

Several times, the server "goes away" (error 2006) or crashes (2013).

It might be related to bugs 39159 and 39160,
but those bugs are signalled against NDB while this one affects the server:

=====
funcs_1.is_tables_ndb          [ fail ]

mysqltest: In included file "./include/ndb_not_readonly.inc": At line 25: query 'replace into mysql.ndb_schema
 values("","",0,"",0,0,0,0,0)' failed with wrong errno 2006: 'MySQL server has gone away', instead of 0...

Stopping All Servers
=====

=====
ndb.ndb_restore                [ fail ]

mysqltest: In included file "./include/ndb_not_readonly.inc": At line 25: query 'replace into mysql.ndb_schema
 values("","",0,"",0,0,0,0,0)' failed with wrong errno 2013: 'Lost connection to MySQL server during query', i
nstead of 0...

Stopping All Servers
=====

This showed up in tests "is_tables_ndb", "ndb_blob_partition", "ndb_bug31477", "ndb_cache2", "ndb_rename", "ndb_restore", "ndb_sp".

How to repeat:
Happened during a test suite run.