MySQL Forums
Forum List  »  NDB clusters

Another Error 6000, can't start ndbd nodes
Posted by: Jim Knows
Date: November 06, 2015 09:54AM

The "ERROR OS Signal recieved" makes me feel like it is something to do with Debian7-amd64 that I have an OS, but I don't know if there is a fix.

%%%%%%%%%%%%%%%% my.cnf on NDBD and MYSQLD nodes %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
[client]
port = 3306
socket = /var/run/mysqld/mysqld.sock

# This was formally known as [safe_mysqld]. Both versions are currently parsed.
[mysqld_safe]
socket = /var/run/mysqld/mysqld.sock
pid-file = /var/run/mysqld/mysqld_safe.pid

[mysqld]
socket = /var/run/mysqld/mysqld.sock
pid-file = /var/run/mysqld/mysqld.pid

#DB Stuff (use nbdcluster storage engine)
ndb_nodeid=19
ndbcluster
ndb-connectstring=192.168.0.111,192.168.0.112,192.168.0.113
default_storage_engine=ndbcluster
default_table_type=nbcluster

#Dir's
basedir = /usr/local/mysql
datadir = /opt1/mysql_databases
tmpdir = /tmp

#network
bind-address = 192.168.0.101
port = 3306
server_id=19

#logging
explicit_defaults_for_timestamp = 1
log_error = /opt1/mysql-error.log
general_log_file = /opt1/mysql-general.log
general_log = 1
log_bin
#log-bin=mysqld-bin

#performance tweaks
#innodb_buffer_pool_size = 1024M

[mysql_cluster]
ndb-connectstring=192.168.0.111,192.168.0.112,192.168.0.113

[ndbd]
connect-string=192.168.0.111,192.168.0.112,192.168.0.113

%%%%%%%%%%%%%%%% MGMT Nodes Config.ini %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
[ndbd default]
NoOfReplicas=2
DataMemory=300M
IndexMemory=128M

################# ndbd instances ##################################3
[ndbd]
NodeId=11
HostName=192.168.0.101
DataDir=/opt1/mysql_cluster/data

[ndbd]
NodeId=21
HostName=192.168.0.102
DataDir=/opt1/mysql_cluster/data

[ndbd]
NodeId=41
HostName=192.168.0.103
DataDir=/opt1/mysql_cluster/data


####################### ndb_mgmd instances ###################3
[ndb_mgmd default]
DataDir=/opt1/mysql_cluster #MGM node log files

[ndb_mgmd]
NodeId=15
HostName=192.168.0.111

[ndb_mgmd]
NodeId=25
HostName=192.168.0.112

[ndb_mgmd]
NodeId=35
HostName192.168.0.113

[mysqld]
NodeId=19
hostname=192.168.0.101

[mysqld]
NodeId=29
hostname=192.168.0.102

[mysqld]
NodeId=49
hostname=192.168.0.103

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%



######################## ndb_error.log############################
Time: Friday 6 November 2015 - 10:40:47
Status: Temporary error, restart node
Message: Error OS signal received (Internal error, programming error or missing error message, please report a bug)
Error: 6000
Error data: Signal 8 received; Floating point exception
Error object: /export/home/pb2/build/sb_0-16730888-1444648756.12/mysql-cluster-gpl-7.4.8/storage/ndb/src/kernel/ndbd.cpp
Program: ndbd
Pid: 4241
Version: mysql-5.6.27 ndb-7.4.8
Trace: /opt1/mysql_cluster/data/ndb_11_trace.log.18 [t1..t1


####################### ndb_out.log #########################33
2015-11-06 10:40:29 [ndbd] INFO -- Phase 0 has made some file system initialisations
2015-11-06 10:40:29 [ndbd] INFO -- Starting QMGR phase 1
2015-11-06 10:40:29 [ndbd] INFO -- DIH reported initial start, now starting the Node Inclusion Protocol
2015-11-06 10:40:44 [ndbd] INFO -- Include node protocol completed, phase 1 in QMGR completed
2015-11-06 10:40:44 [ndbd] INFO -- Start phase 1 completed
2015-11-06 10:40:44 [ndbd] INFO -- Phase 1 initialised some variables and included node in cluster, locked memory if configured to do so
2015-11-06 10:40:44 [ndbd] INFO -- Asking master node to accept our start (we are master, GCI = 0)
2015-11-06 10:40:44 [ndbd] INFO -- NDBCNTR master accepted us into cluster, start NDB start phase 1
2015-11-06 10:40:44 [ndbd] INFO -- We are performing initial start of cluster
2015-11-06 10:40:44 [ndbd] INFO -- LDM(0): Starting REDO log initialisation
2015-11-06 10:40:47 [ndbd] INFO -- LDM(0): Completed REDO log initialisation of logPart = 0
2015-11-06 10:40:47 [ndbd] INFO -- LDM(0): Completed REDO log initialisation of logPart = 3
2015-11-06 10:40:47 [ndbd] INFO -- LDM(0): Completed REDO log initialisation of logPart = 2
2015-11-06 10:40:47 [ndbd] INFO -- LDM(0): Completed REDO log initialisation of logPart = 1
2015-11-06 10:40:47 [ndbd] INFO -- LDM(0): Completed REDO initialisation
2015-11-06 10:40:47 [ndbd] INFO -- Schema file initialisation Starting
2015-11-06 10:40:47 [ndbd] INFO -- Schema file initialisation Completed
2015-11-06 10:40:47 [ndbd] INFO -- NDB start phase 1 completed
2015-11-06 10:40:47 [ndbd] INFO -- Start phase 2 completed
2015-11-06 10:40:47 [ndbd] INFO -- Phase 2 did more initialisations, master accepted our start, we initialised the REDO log
2015-11-06 10:40:47 [ndbd] INFO -- Grant nodes to start phase: 3, nodes: 0000000000000800
2015-11-06 10:40:47 [ndbd] INFO -- setting nodeGroup = ZNIL for node 11
2015-11-06 10:40:47 [ndbd] INFO -- setting nodeGroup = ZNIL for node 21
2015-11-06 10:40:47 [ndbd] INFO -- setting nodeGroup = ZNIL for node 41
2015-11-06 10:40:47 [ndbd] INFO -- Start NDB start phase 2
2015-11-06 10:40:47 [ndbd] INFO -- NDB start phase 2 completed
2015-11-06 10:40:47 [ndbd] INFO -- Start phase 3 completed
2015-11-06 10:40:47 [ndbd] INFO -- Phase 3 performed local connection setups
2015-11-06 10:40:47 [ndbd] INFO -- Grant nodes to start phase: 4, nodes: 0000000000000800
2015-11-06 10:40:47 [ndbd] INFO -- Start NDB start phase 3
2015-11-06 10:40:47 [ndbd] INFO -- Start invalidating: Part 0, Head: file: 0, page: 1, Invalidation start: file: 0, page: 1, actual start invalidate: file: 0 page: 1
2015-11-06 10:40:47 [ndbd] INFO -- Start invalidating: Part 1, Head: file: 0, page: 1, Invalidation start: file: 0, page: 1, actual start invalidate: file: 0 page: 1
2015-11-06 10:40:47 [ndbd] INFO -- Start invalidating: Part 3, Head: file: 0, page: 1, Invalidation start: file: 0, page: 1, actual start invalidate: file: 0 page: 1
2015-11-06 10:40:47 [ndbd] INFO -- LDM(0): Completed old Redo head invalidation on log part 1
2015-11-06 10:40:47 [ndbd] INFO -- LDM(0): Completed old Redo head invalidation on log part 0
2015-11-06 10:40:47 [ndbd] INFO -- Start invalidating: Part 2, Head: file: 0, page: 1, Invalidation start: file: 0, page: 1, actual start invalidate: file: 0 page: 1
2015-11-06 10:40:47 [ndbd] INFO -- LDM(0): Completed old Redo head invalidation on log part 3
2015-11-06 10:40:47 [ndbd] INFO -- LDM(0): Completed old Redo head invalidation on log part 2
2015-11-06 10:40:47 [ndbd] INFO -- LDM(0): All redo actions complete (apply, invalidate)
2015-11-06 10:40:47 [ndbd] INFO -- NDB start phase 3 completed
2015-11-06 10:40:47 [ndbd] INFO -- Start phase 4 completed
2015-11-06 10:40:47 [ndbd] INFO -- Phase 4 continued preparations of the REDO log
2015-11-06 10:40:47 [ndbd] INFO -- Grant nodes to start phase: 5, nodes: 0000000000000800
2015-11-06 10:40:47 [ndbd] INFO -- NDB start phase 4 completed
2015-11-06 10:40:47 [ndbd] INFO -- Creating System Tables Starting as part of initial start
2015-11-06 10:40:47 [ndbd] INFO -- Received signal 8. Running error handler.
2015-11-06 10:40:47 [ndbd] INFO -- Signal 8 received; Floating point exception
2015-11-06 10:40:47 [ndbd] INFO -- /export/home/pb2/build/sb_0-16730888-1444648756.12/mysql-cluster-gpl-7.4.8/storage/ndb/src/kernel/ndbd.cpp
2015-11-06 10:40:47 [ndbd] INFO -- Error handler signal shutting down system
2015-11-06 10:40:47 [ndbd] INFO -- Error handler shutdown completed - exiting
2015-11-06 10:40:47 [ndbd] DEBUG -- Angel got child 4241
2015-11-06 10:40:47 [ndbd] DEBUG -- error: 6000, signal: 8, sphase: 5
2015-11-06 10:40:47 [ndbd] ALERT -- Node 11: Forced node shutdown completed. Occured during startphase 5. Initiated by signal 8. Caused by error 6000: 'Error OS signal received(Internal error, programming error or missing error message, please report a bug). Temporary error, restart node'.

%%%%%%%%%%%%%%%%%%%%% ndb trace log %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

Options: ReplyQuote


Subject
Views
Written By
Posted
Another Error 6000, can't start ndbd nodes
3092
November 06, 2015 09:54AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.