2 messages in com.mysql.lists.clusterProblem with MySQL client
FromSent OnAttachments
Bruce Robertson25 Sep 2004 13:00 
Magnus Svensson26 Sep 2004 01:02 
Subject:Problem with MySQL client
From:Bruce Robertson (bru@greatbasin.net)
Date:09/25/2004 01:00:34 PM
List:com.mysql.lists.cluster

My cluster setup seems to work perfectly, but I'm having trouble with the client side. I have three MySQL servers talking to one cluster, and occasionally the servers get into a state where they hang and cannot be killed. I end up with a SEGV fault as well, which I've attached. I have to "kill -9" both mysqld and mysqld_safe, and then restart. It seems to work fine after that, until next time. Each time it happens, it seems to be a different SQL command.

Below you will find the fault trace, and my config file. I can send more examples with different SQL commands, if you need 'em. Any ideas?

0x812f963 handle_segfault + 423 0x615458 (?) 0x83a8c15 addBlobTables__17NdbDictionaryImplR12NdbTableImpl + 109 0x83a8c22 addBlobTables__17NdbDictionaryImplR12NdbTableImpl + 122 0x83a776a fetchGlobalTableImpl__17NdbDictionaryImplPCc + 318 0x84502b8 get_local_table_info__17NdbDictionaryImplPCc + 44 0x83989af getNdbScanOperation__13NdbConnectionPCc + 55 0x81b02a5 ndb_get_table_statistics__FP3NdbPCcPUxT2 + 269 0x81ab90e records_update__13ha_ndbcluster + 54 0x81ae177 info__13ha_ndbclusterUi + 31 0x81be79d mysqld_extend_show_tables__FP3THDPCcT1 + 3293 0x8140fce mysql_execute_command__FP3THD + 10154 0x81435a9 mysql_parse__FP3THDPcUi + 169 0x813d96f dispatch_command__F19enum_server_commandP3THDPcUi + 1643 0x813d2f8 do_command__FP3THD + 188 0x813ca27 handle_one_connection + 615 0x60e98c (?) 0x56a16a (?)

Version: '4.1.5-gamma-max' socket: '/tmp/mysql.sock' port: 3306 Official
MySQL-max binary 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=8388600 read_buffer_size=131072 max_used_connections=1 max_connections=100 threads_connected=1 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 225791 K bytes of memory Hope that's ok; if not, decrease some variables in the equation.

thd=0x86df640 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=0x2a49dc, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x812f963 0x615458 0x83a8c15 0x83a8c22 0x83a776a 0x84502b8 0x83989af 0x81b02a5 0x81ab90e 0x81ae177 0x81be79d 0x8140fce 0x81435a9 0x813d96f 0x813d2f8 0x813ca27 0x60e98c 0x56a16a New value of fp=(nil) failed sanity check, terminating stack trace! Please read http://www.mysql.com/doc/en/Using_stack_trace.html and follow instru ctions 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 0x86eef90 = SHOW TABLE STATUS FROM `mysterol` thd->thread_id=9 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

# file "config.ini" - showing minimal setup with 1 DB node # This file is placed in the start directory of ndb_mgmd, # the management server.

[COMPUTER DEFAULT]

[DB DEFAULT] NoOfReplicas: 2

[API DEFAULT]

[TCP DEFAULT]

[COMPUTER] Id:1 HostName: sql0

[COMPUTER] id:2 HostName: sql1

[COMPUTER] id:3 HostName: web0

[COMPUTER] id:4 HostName: web1

[COMPUTER] id:5 HostName: web2

[MGM] Id:1 ExecuteOnComputer: 1 PortNumber: 2200

[MGM] Id:2 ExecuteOnComputer: 2 PortNumber: 2200

[DB] Id: 3 ExecuteOnComputer: 1 FileSystemPath: /var/lib/mysql-cluster/node3/

[DB] Id: 4 ExecuteOnComputer: 2 FileSystemPath: /var/lib/mysql-cluster/node4/

[DB] Id: 5 ExecuteOnComputer: 1 FileSystemPath: /var/lib/mysql-cluster/node5/

[DB] Id: 6 ExecuteOnComputer: 2 FileSystemPath: /var/lib/mysql-cluster/node6/

[API] Id: 7 ExecuteOnComputer: 3

[API] Id: 8 ExecuteOnComputer: 4

[API] Id: 9 ExecuteOnComputer: 5