NGDR Error: Cannot fork() process . . . errno_description

The DR daemon could not fork off a process for the command to run in. A message in the form "running command" appears in the system logs prior to this error message, or any other error message about failed commands. 

The errno_description offers hints on how to fix the command that you want to run. Also check the man page for the command. It may have an explanation of the error.

DR Error: command has continued

While the DR daemon was running external commands, one of the commands failed or exited abnormally. The DR feature executes external commands (for example, drvconf) to configure the software subsystems. 

Run the program manually on the domain. If the command fails again, refer to the man page for the command. It may have an explanation of the error. 

DR Error: command stopped by signal signal_number

While the DR daemon was running external commands, one of the commands failed or exited abnormally. The DR feature executes external commands (for example, drvconf) to configure the software subsystems.

Run the program manually on the domain. If the command fails again, refer to the man page for the command. It may have an explanation of the error. 

DR Error: command terminated due to signal signal_number

While the DR daemon was running external commands, one of the commands failed or exited abnormally. The DR feature executes external commands (for example, drvconf) to configure the software subsystems.

Run the program manually on the domain. If the command fails again, refer to the man page for the command. It may have an explanation of the error. 

DR Error: command terminated due to signal signal_number. Core dumped.

While the DR daemon was running external commands, one of the commands failed or exited abnormally. The DR feature executes external commands (for example, drvconf) to configure the software subsystems.

Run the program manually on the domain. If the command fails again, refer to the man page for the command. It may have an explanation of the error. 

NGDR Error: dr_issue_ioctl: failed closing driver . . . errno_description

The DR daemon encountered a failure while it tried to close a DR driver entry point. A more detailed explanation of this failure accompanies the error message. 

Use the close(2) man page and the errno_description to determine what caused this error and how to solve it.

Cannot exec command (errno = errno_value).

The DR daemon could not execute the external command. A more detailed explanation of this failure accompanies the error message. 

Check the system logs to determine which command failed. See the exec(2) man page for more details about the specified errno_value. Use this information to solve the error.

dr_get_sysbrd_info: NULL parameter

An invalid pointer was given to the DR daemon during a query of the slot-to-memory address mapping. Either an RPC gave an incorrect value, or the DR daemon called itself with an invalid parameter. 

You should gather as much information about this problem as possible from the system logs so that you can determine the cause of the failure. Try stopping and starting the DR daemon and the SSP application. If this error persists, report it to your Sun service representative. 

update_cpu_info: bad board number

A problem within the DR daemon occurred, causing it to call its internal routines with incorrect values. 

You should gather as much information about this problem as possible from the system logs so that you can determine the cause of the failure. You should also report this problem, and if it persists, you may have to stop and restart the daemon. 

WARNING: Failed to update board board_number`s modification time [non-fatal].

Updating the board modification time has failed. After a board has been modified (for example, memory or CPUs added), it is probed or deprobed by OBP so that OBP can inform other programs of the change. Then, the modification time is updated. 

This error is non-fatal.