MySQL Forums
Forum List  »  NDB clusters

ndb cluster 7.5 SQL node start failed
Posted by: Ryan tse
Date: June 19, 2018 04:59AM

Hi, due to the disk space full, the redo log files corrupted.
Executed "ndbmt --initial" in the Failed data node, it can solved the issues.
But I cannot start the sql node in the following sql log.
Anyone can help would be appreciate, thanks.

2018-06-19T18:50:16.409943+08:00 0 [ERROR] /usr/sbin/mysqld: Incorrect information in file: './mysql/user.frm'
2018-06-19T18:50:16.410153+08:00 0 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.user' doesn't exist

SQL Node - mysqld.log
---------------------
2018-06-19T18:50:13.976967+08:00 0 [Note] /usr/sbin/mysqld (mysqld 5.7.21-ndb-7.5.9-cluster-gpl-log) starting as process 16106 ...
2018-06-19T18:50:13.990127+08:00 0 [Note] InnoDB: PUNCH HOLE support available
2018-06-19T18:50:13.990408+08:00 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-06-19T18:50:13.990470+08:00 0 [Note] InnoDB: Uses event mutexes
2018-06-19T18:50:13.990520+08:00 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2018-06-19T18:50:13.990564+08:00 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-06-19T18:50:13.990606+08:00 0 [Note] InnoDB: Using Linux native AIO
2018-06-19T18:50:13.994764+08:00 0 [Note] InnoDB: Number of pools: 1
2018-06-19T18:50:13.995568+08:00 0 [Note] InnoDB: Using CPU crc32 instructions
2018-06-19T18:50:14.002428+08:00 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2018-06-19T18:50:14.043675+08:00 0 [Note] InnoDB: Completed initialization of buffer pool
2018-06-19T18:50:14.051646+08:00 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2018-06-19T18:50:14.068756+08:00 0 [Note] InnoDB: Highest supported file format is Barracuda.
2018-06-19T18:50:14.262074+08:00 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2018-06-19T18:50:14.262665+08:00 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2018-06-19T18:50:14.507610+08:00 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2018-06-19T18:50:14.515841+08:00 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2018-06-19T18:50:14.516291+08:00 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2018-06-19T18:50:14.522487+08:00 0 [Note] InnoDB: Waiting for purge to start
2018-06-19T18:50:14.573316+08:00 0 [Note] InnoDB: 5.7.21 started; log sequence number 3054184
2018-06-19T18:50:14.574026+08:00 0 [Note] InnoDB: Loading buffer pool(s) from /data/mysql/ib_buffer_pool
2018-06-19T18:50:14.576979+08:00 0 [Note] Plugin 'FEDERATED' is disabled.
2018-06-19T18:50:14.581606+08:00 0 [Note] InnoDB: Buffer pool(s) load completed at 180619 18:50:14
2018-06-19T18:50:14.829960+08:00 0 [Note] NDB: NodeID is 4, management server '192.168.125.224:1186'
2018-06-19T18:50:15.231490+08:00 0 [Note] NDB[0]: NodeID: 4, all storage nodes connected
2018-06-19T18:50:15.231663+08:00 0 [Warning] NDB: server id set to zero - changes logged to bin log with server id zero will be logged with another server id by slave mysqlds
2018-06-19T18:50:15.232276+08:00 0 [Note] NDB Binlog: Starting...
2018-06-19T18:50:15.232475+08:00 0 [Note] NDB Util: Starting...
2018-06-19T18:50:15.232502+08:00 1 [Note] NDB Binlog: Started
2018-06-19T18:50:15.232668+08:00 1 [Note] NDB Binlog: Setting up
2018-06-19T18:50:15.232739+08:00 2 [Note] NDB Util: Wait for server start completed
2018-06-19T18:50:15.232958+08:00 0 [Note] NDB Index Stat: Starting...
2018-06-19T18:50:15.233042+08:00 1 [Note] NDB Binlog: Created schema Ndb object, reference: 0x80040004, name: 'Ndb Binlog schema change monitoring'
2018-06-19T18:50:15.233043+08:00 0 [Note] NDB Index Stat: Wait for server start completed
2018-06-19T18:50:15.233620+08:00 1 [Note] NDB Binlog: Created injector Ndb object, reference: 0x80050004, name: 'Ndb Binlog data change monitoring'
2018-06-19T18:50:15.233705+08:00 1 [Note] NDB Binlog: Setup completed
2018-06-19T18:50:15.233741+08:00 1 [Note] NDB Binlog: Wait for server start completed
2018-06-19T18:50:15.480913+08:00 0 [Note] Server hostname (bind-address): '*'; port: 3306
2018-06-19T18:50:15.481078+08:00 0 [Note] IPv6 is available.
2018-06-19T18:50:15.481175+08:00 0 [Note] - '::' resolves to '::';
2018-06-19T18:50:15.481344+08:00 0 [Note] Server socket created on IP: '::'.
2018-06-19T18:50:16.409943+08:00 0 [ERROR] /usr/sbin/mysqld: Incorrect information in file: './mysql/user.frm'
2018-06-19T18:50:16.410153+08:00 0 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.user' doesn't exist
2018-06-19T18:50:16.410683+08:00 0 [ERROR] Aborting


MGM Node - mysqld.log
---------------------
2018-06-19 18:50:14 [MgmtSrvr] INFO -- Alloc node id 4 succeeded
2018-06-19 18:50:14 [MgmtSrvr] INFO -- Nodeid 4 allocated for API at 192.168.125.135
2018-06-19 18:50:14 [MgmtSrvr] INFO -- Node 4: mysqld --server-id=0
2018-06-19 18:50:15 [MgmtSrvr] INFO -- Node 2: Node 4 Connected
2018-06-19 18:50:15 [MgmtSrvr] INFO -- Node 3: Node 4 Connected
2018-06-19 18:50:15 [MgmtSrvr] INFO -- Node 2: Node 4: API mysql-5.7.21 ndb-7.5.9
2018-06-19 18:50:15 [MgmtSrvr] INFO -- Node 3: Node 4: API mysql-5.7.21 ndb-7.5.9
2018-06-19 18:50:19 [MgmtSrvr] ALERT -- Node 3: Node 4 Disconnected
2018-06-19 18:50:19 [MgmtSrvr] INFO -- Node 2: Communication to Node 4 closed
2018-06-19 18:50:19 [MgmtSrvr] INFO -- Node 3: Communication to Node 4 closed
2018-06-19 18:50:19 [MgmtSrvr] ALERT -- Node 2: Node 4 Disconnected
2018-06-19 18:50:23 [MgmtSrvr] INFO -- Node 2: Communication to Node 4 opened
2018-06-19 18:50:23 [MgmtSrvr] INFO -- Node 3: Communication to Node 4 opened

Options: ReplyQuote


Subject
Views
Written By
Posted
ndb cluster 7.5 SQL node start failed
1318
June 19, 2018 04:59AM


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.