Critical Messages

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:

Legal options for both ocd and ocdebug are -n, -f, -b, p, -c, and -l.
Option -d is a legal option only for ocdebug.
Options -n and -f are mandatory for both ocd and ocdebug.
Each option requires an argument.

ERROR: Invalid node name <node_name>: system error <system_error>: <system_message>

Level: (100)

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:

The node name specified with the -n option must be defined in a name database.
The node name specified with the -n option must have an IP address assigned to it in that name database.
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.

ERROR: Invalid board number <board_number>

Level: (101)

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".

ERROR: Invalid port number <port_number>

Level: (102)

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".

ERROR: Pseudonym has become invalid

Level: (103)

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.

ERROR: Pseudonym <pseudonym_name> no longer exists

Level: (104)

CAUSE: The pseudonym specified ceased to exist (most likely because another process deleted it).

ACTION: Restart ocd or ocdebug.

ERROR: Pseudonym <pseudonym_name> unavailable

Level: (105)

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).

ERROR: Pseudonym <pseudonym_name> in use but not by DDFA

Level: (106)

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).

ERROR: Pseudonym <pseudonym_name> in use by DDFA with process identifier <process_identifier>

Level: (107)

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).

ERROR: Received SIGINT signal

Level: (108)

ERROR: Cleaning up daemon for pseudonym <pseudonym_name> and device at node <node_name> board <board_number> port <port_number>

Level: (109)

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.

ERROR: Unable to allocate pty because no pty available for use

Level: (150)

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.

ERROR: Unable to obtain file information for pty <slave_pty_name>: system error <system_error>: <system_message>

Level: (151)

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.

ERROR: Unable to create pseudonym <pseudonym_name> with device identifier <device_identifier>: system error <system_error>: <system_message>

Level: (152)

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.

ERROR: Pseudonym <pseudonym_name> does not belong to this daemon

Level: (153)

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).

ERROR: Unable to obtain information concerning availability of pseudonym <pseudonym_name>: system error <system_error>: <system_message>

Level: (154)

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.

ERROR: Unable to free pseudonym <pseudonym_name>: system error <system_error>: <system_message>

Level: (155)

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.

ERROR: Pseudonym <pseudonym_name> is not pty slave

Level: (156)

CAUSE: The pseudonym specified was not a device special file.

ACTION: Delete the pseudonym and restart the ocd or ocdebug.

ERROR: Unable to delete pseudonym <pseudonym_name> left by previously run process: system error <system_error>: <system_message>

Level: (157)

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

ERROR: Terminating daemon

Level: (199)

CAUSE: Ocd or ocdebug was shutdown due to a critical error.

ACTION: Take action based on cause indicated by preceding error messages.

Critical Messages

Technical documentation

» Table of Contents

» Index

Message(s) that Accompany ALL Critical Error Messages