Oracle 5.0 Reference Manual page 1642

ndbd
Instructs not to start automatically. When this option is used,
ndbd
management server, obtains configuration data from it, and initializes communication objects.
However, it does not actually start the execution engine until specifically requested to do so by
the management server. This can be accomplished by issuing the proper
management client (see
generates a set of log files which are placed in the directory specified by
ndbd
configuration file.
config.ini
These log files are listed below.
the node's unique identifier. For example,
node whose node ID is 2.
•
ndb_node_id_error.log
process has encountered. Each record in this file contains a brief error string and a reference to a
trace file for this crash. A typical entry in this file might appear as shown here:
Date/Time: Saturday 30 July 2004 - 00:20:01
Type of error: error
Message: Internal program error (failed ndbrequire)
Fault ID: 2341
Problem data: DbtupFixAlloc.cpp
Object of reference: DBTUP (Line: 173)
ProgramName: NDB Kernel
ProcessID: 14909
TraceFile: ndb_2_trace.log.2
***EOM***
Listings of possible
ndbd
down prematurely can be found in
Important
The last entry in the error log file is not necessarily the newest one (nor is
it likely to be). Entries in the error log are not listed in chronological order;
rather, they correspond to the order of the trace files as determined in the
ndb_node_id_trace.log.next
overwritten in a cyclical and not sequential fashion.
•
ndb_node_id_trace.log.trace_id
before the error occurred. This information is useful for analysis by the MySQL Cluster development
team.
It is possible to configure the number of these trace files that will be created before old files are
overwritten.
trace_id
•
ndb_node_id_trace.log.next
assigned.
•
ndb_node_id_out.log
created only if
ndbd
•
ndb_node_id.pid
daemon. It also functions as a lock file to avoid the starting of nodes with the same identifier.
•
ndb_node_id_signal.log
trace all incoming, outgoing, and internal messages with their data in the
It is recommended not to use a directory mounted through NFS because in some environments this
can cause problems whereby the lock on the
terminated.
— The MySQL Cluster Data Node Daemon
Section 17.5.2, "Commands in the MySQL Cluster Management
is the node's unique identifier. Note that
node_id
ndb_2_error.log
is a file containing records of all crashes which the referenced
exit codes and messages generated when a data node process shuts
Error
ndbd
is a trace file describing exactly what happened just
is a number which is incremented for each successive trace file.
is the file that keeps track of the next trace file number to be
is a file containing any data output by the
is started as a daemon, which is the default behavior.
is a file containing the process ID of the
is a file used only in debug versions of ndbd, where it is possible to
1622
is the error log generated by the data
Messages.
file (see below). Error log entries are thus
ndbd
file remains in effect even after the process has
.pid
connects to the
ndbd
command in the
START
in the
DataDir
node_id
process. This file is
ndbd
process when started as a
process.
ndbd
Client").
represents
ndbd