When the Device Control Daemon (DCD) receives an error code from the kernel, the DCD does not know which resource is unavailable. The daemon will create a standard UNIX error string based on the error code.

When attempting to commit a configuration, the commit fails and the system logs messages similar to the following:

  • A write operation over the routing socket returned a bad status.
  • The error code received by the DCD cannot be resolved.
  • The error might be the result of an attempt to commit an unsupported configuration, such as too many schedulers configured.

When a daemon like dcd gets an error code (ENOMEM) from the kernel, it does not know what kind of resource is exhausted in the kernel. This results in an ifd/ifl/iff/ifa object creation failure, and it prints out the standard UNIX error string based on the error code. Only the kernel will know the exact failure and print out more information.

Perform these steps to determine the cause and resolve the problem (if any):

1. Collect the show command output to help determine the cause of this message.

Capture the output to a file (in case you have to open a technical support case). To do this, configure each SSH client/terminal emulator to log your session.

2. Analyze the show command output. Look for any related events that occurred at or just before the core syslog message.

About the author


Leave a Comment