 |
» |
|
|
|
Critical logging messages are issued when quitting ocd or
ocdebug is caused by the use of invalid options, argument values,
or pseudonyms, or the reception of SIGINT (signal interrupt). Usage logging messages are caused by syntax errors. |
usage: ocd -n<node_name> -f<pseudonym> [-b<board_no>] [-p<port_no>] [-c<pc_file_path>]
[-l<log_level>]
usage: ocdebug -n<node_name> -f<pseudonym> [-b<board_no>] [-p<port_no>] [-c<pc_file_path>]
[-l<log_level>] [-d<level>]
CAUSE: Ocd or ocdebug was executed with an illegal or missing option.
ACTION: Restart ocd or ocdebug using the correct syntax and note that:
1. Legal options for both ocd and ocdebug are -n, -f, -b, p, -c, and -l.
2. Option -d is a legal option only for ocdebug.
3. Options -n and -f are mandatory for both ocd and ocdebug.
4. Each option requires an argument.
(100) ERROR: Invalid node name <node_name>: system error <system_error>: <system_message>
CAUSE: The node name argument specified with the -n option could not be
resolved into an IP address due to the system error given.
ACTION: Restart ocd or ocdebug using a valid node name and note that:
1. The node name specified with the -n option must be defined in a name database.
2. The node name specified with the -n option must have an IP address assigned to it in that
name database.
3. The access to that name database must not be impeded in any way.
One way of validating the node name is to execute the nslookup command. |
|
|
(101) ERROR: Invalid board number <board_number>
CAUSE: The board number argument specified with the -b option was not in
the range 0 to 7 for a DTC, or it was not a string consisting of "X" or "x".
ACTION: Restart ocd or ocdebug using a DTC board number in the range 0 to 7, or a string
consisting of "X" or "x".
(102) ERROR: Invalid port number <port_number>
CAUSE: The port number argument specified with the -p option was not correct as follows:
If the board number argument contained a value 0 to 7 for a DTC,
then the port number argument was not in the range 0 to 31.
If the board number argument was a string consisting of "X" or "x",
then the port number argument was not an integer value representing
a TCP service port, or a string consisting of "X" or "x" (which
refers to the default TCP port address of 23 for the node name specified).
ACTION: Restart ocd or ocdebug using a port number that is an integer value
of a valid DTC port number in the range 0 to 31 or a TCP service port
number, or a port number that is a string consisting of "X" or "x".
(103) ERROR: Pseudonym has become invalid
CAUSE: The pseudonym in use ceased to exist (most likely because another
process deleted it) or was not in use by ocd or ocdebug and possibly
was in use by another process.
NOTE: This message is followed by message (403).
ACTION: Make sure that no other process is using the pseudonym and restart ocd or ocdebug.
(104) ERROR: Pseudonym <pseudonym_name> no longer exists
CAUSE: The pseudonym specified ceased to exist (most likely because another process deleted it).
ACTION: Restart ocd or ocdebug. |
|
|
(105) ERROR: Pseudonym <pseudonym_name> unavailable
CAUSE: The pseudonym specified was in use by another process and was not
available for use by ocd or ocdebug.
ACTION: Determine if the process using the pseudonym is necessary and
restart ocd or ocdebug if it is not (after stopping that process and
removing the pseudonym).
(106) ERROR: Pseudonym <pseudonym_name> in use but not by DDFA
CAUSE: The pseudonym specified was in use by or created by a process other
than ocd or ocdebug.
ACTION: Determine if the process using the pseudonym is
necessary and restart ocd or ocdebug if it is not
(after stopping that process and removing the pseudonym).
(107) ERROR: Pseudonym <pseudonym_name> in use by DDFA with
process identifier <process_identifier>
CAUSE: The pseudonym specified was in use by another ocd or ocdebug.
ACTION: Determine if the process using the pseudonym is necessary and restart ocd
or ocdebug if it is not (after stopping that process and removing the pseudonym).
(108) ERROR: Received SIGINT signal
(109) ERROR: Cleaning up daemon for pseudonym <pseudonym_name> and device
at node <node_name> board <board_number> port <port_number>
CAUSE: Ocd or ocdebug received a SIGINT signal and closed its connection
and deleted its pseudonym.
NOTE: These messages are followed by messages (403) and (432).
ACTION: Restart ocd or ocdebug. |
|
|
(150) ERROR: Unable to allocate pty because no pty available for use
CAUSE: There were no ptys available for use on the system.
ACTION: Allocate more ptys on the system or wait to restart ocd or ocdebug
until there are fewer processes running.
(151) ERROR: Unable to obtain file information for pty <slave_pty_name>:
system error <system_error>: <system_message>
CAUSE: There was no information available for the pty specified due to the
system error given.
ACTION: Look up what the stat(2) man page states about the system error
given and make the correction as appropriate.
(152) ERROR: Unable to create pseudonym <pseudonym_name> with device
identifier <device_identifier>: system error <system_error>: <system_message>
CAUSE: The pseudonym specified was not created due to the system error given.
ACTION: Look up what the mknod(2) man page states about the system error
given and make the correction as appropriate.
(153) ERROR: Pseudonym <pseudonym_name> does not belong to this daemon
CAUSE: The pseudonym specified was not in use by ocd or ocdebug and possibly
was in use by another process.
ACTION: Determine if the process using the pseudonym is necessary and restart ocd or
ocdebug if it is not (after stopping that process and removing the pseudonym).
(154) ERROR: Unable to obtain information concerning availability of
pseudonym <pseudonym_name>: system error <system_error>: <system_message>
CAUSE: There was no information available for the pseudonym specified due to
the system error given.
ACTION: Look up what the stat(2) man page states about the system error given and
make the correction as appropriate. |
|
|
(155) ERROR: Unable to free pseudonym <pseudonym_name>:
system error <system_error>: <system_message>
CAUSE: The pseudonym specified was not freed from use by another process due
to the system error given.
ACTION: Look up what the kill(2) man page states about the system error
given and make the correction as appropriate.
(156) ERROR: Pseudonym <pseudonym_name> is not pty slave
CAUSE: The pseudonym specified was not a device special file.
ACTION: Delete the pseudonym and restart the ocd or ocdebug.
(157) ERROR: Unable to delete pseudonym <pseudonym_name> left by previously
run process: system error <system_error>: <system_message>
CAUSE: The pseudonym specified was not deleted for use by a fresh ocd or
ocdebug due to the system error given.
ACTION: Delete the pseudonym and restart ocd or ocdebug.
MESSAGE(S) THAT ACCOMPANY ALL CRITICAL ERROR MESSAGES:
(199) ERROR: Terminating daemon
CAUSE: Ocd or ocdebug was shutdown due to a critical error.
ACTION: Take action based on cause indicated by preceding error messages. |
|
|
