MySQL Bugs: #10595: Server crash on insert

Bug #10595	Server crash on insert
Submitted:	12 May 2005 13:26	Modified:	10 Jul 2005 3:21
Reporter:	Joerg Bruehe	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S1 (Critical)
Version:	4.1.12	OS:	HP/UX (HP-UX 11.23 (ia64))
Assigned to:	Assigned Account	CPU Architecture:	Any

Description:
Release build of 4.1.12, based on ChangeSet
  1.2261 05/05/10 14:44:03 lenz@mysql.com +2 -0
  Applied two patches already commited to the main tree to resolve bugs found
during the build:
   - removed an "#error PRAGMA" from sql/item_strfunc.h (msvensson)
   - Fixed BUG#10070 (range test failed if InnoDB is not available) (sergefp)

Crash on "hpita2", both "cluster" + "max" build, both "default" +
"--ps-protocol" test run:

ndb_limit                      [ fail ]

Errors are (from /var/tmp/hpita2-64bit/test/mysql-cluster-4.1.12-hp-hpux11.23-ia64-64bit/mysql-test/var/log/mysqltest-time) :
/var/tmp/hpita2-64bit/test/mysql-cluster-4.1.12-hp-hpux11.23-ia64-64bit/bin/mysqltest: At line 60: query 'INSERT INTO `t2` VALUES
(  1,0,'2004-09-17', 5,100,100,''),
(  1,0,'2004-09-18', 7,100,100,''),
( 17,0,'2004-09-27',20,132,100,''),
(  4,0,'2004-09-16',23,132,100,''),
( 86,0,'2004-09-18', 7,196,196,''),
( 11,0,'2004-09-16',16,132,100,''),
(140,0,'2004-09-18', 0,100,164,''),
(  2,0,'2004-09-17', 7,132,100,''),
(846,0,'2004-09-27',11,132,164,''),
(  1,0,'2004-09-18', 8,132,100,''),
( 22,0,'2004-09-27', 9,164,132,''),
(711,0,'2004-09-27', 9,100,164,''),
( 11,0,'2004-09-18', 0,196,132,''),
( 41,0,'2004-09-27',15,196,132,''),
( 57,0,'2004-09-18', 2,164,196,'')' failed: 2013: Lost connection to MySQL server during query
(the last lines may be the most important ones)

Ending Tests
Shutting-down MySQL daemon

master not cooperating with mysqladmin, will try manual kill
kill: 465: The specified process does not exist.
master refused to die. Sending SIGKILL
kill: 465: The specified process does not exist.
Master shutdown finished

How to repeat:
Test suite should produce it.

Looking at custom 4.1.13 build done June 7 this problem
was not there on hpita2. Can you confirm problem still exist?

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".