The MySQL Cluster API Developer Guide :: 6 MySQL Cluster Internals :: 6.2 DUMP Commands :: 6.2.3 DUMP Codes 2000 to 2999 :: 6.2.3.6 DUMP 2305
Section Navigation [Toggle]
- 6.2.3 DUMP Codes 2000 to 2999
- 6.2.3.1 DUMP 2300
- 6.2.3.2 DUMP 2301
- 6.2.3.3 DUMP 2302
- 6.2.3.4 DUMP 2303
- 6.2.3.5 DUMP 2304
- 6.2.3.6 DUMP 2305
- 6.2.3.7 DUMP 2308
- 6.2.3.8 DUMP 2315
- 6.2.3.9 DUMP 2350
- 6.2.3.10 DUMP 2352
- 6.2.3.11 DUMP 2400
- 6.2.3.12 DUMP 2401
- 6.2.3.13 DUMP 2402
- 6.2.3.14 DUMP 2403
- 6.2.3.15 DUMP 2404
- 6.2.3.16 DUMP 2405
- 6.2.3.17 DUMP 2406
- 6.2.3.18 DUMP 2500
- 6.2.3.19 DUMP 2501
- 6.2.3.20 DUMP 2502
- 6.2.3.21 DUMP 2503
- 6.2.3.22 DUMP 2504
- 6.2.3.23 DUMP 2505
- 6.2.3.24 DUMP 2506
- 6.2.3.25 DUMP 2507
- 6.2.3.26 DUMP 2508
- 6.2.3.27 DUMP 2509
- 6.2.3.28 DUMP 2510
- 6.2.3.29 DUMP 2511
- 6.2.3.30 DUMP 2512
- 6.2.3.31 DUMP 2513
- 6.2.3.32 DUMP 2514
- 6.2.3.33 DUMP 2515
- 6.2.3.34 DUMP 2550
- 6.2.3.35 DUMP 2600
- 6.2.3.36 DUMP 2601
- 6.2.3.37 DUMP 2602
- 6.2.3.38 DUMP 2603
- 6.2.3.39 DUMP 2604
| Code | Symbol | Kernel Block(s) |
| 2305 | --- |
DBLQH |
Description.
Show the states of all fragment log files (see
Section 6.2.3.5, “DUMP 2304”), then
kills the node.
Sample Output.
Time: Friday 16 February 2007 - 13:11:57 Status: Temporary error, restart node Message: System error, node killed during node restart by other node (Internal error, programming error or missing error message, please report a bug) Error: 2303 Error data: Please report this as a bug. Provide as much info as possible, expecially all the ndb_*_out.log files, Thanks. Shutting down node due to failed handling of GCP_SAVEREQ Error object: DBLQH (Line: 18619) 0x0000000a Program: ./libexec/ndbd Pid: 111 Time: Friday 16 February 2007 - 13:11:57 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 6 received; Aborted Error object: main.cpp Program: ./libexec/ndbd Pid: 11138 Trace: /usr/local/mysql-5.1/cluster/ndb_2_trace.log.2 Version: Version 5.1.16 (beta)
Additional Information. No error message written to cluster log when the node is killed. Node failure is made evident only by subsequent heartbeat failure messages.
