The DCD_RTSOCK_READ_SYNC_NOBUF message is reported into the system message file whenever the interface-control process (dcd) could not obtain memory to read a message from kernel. This article documents an approach to troubleshoot this problem.
The DCD_RTSOCK_READ_SYNC_NOBUF message is logged each time the dcd process is not able to obtain memory to read messages from the kernel.
When the DCD_RTSOCK_READ_SYNC_NOBUF event occurs, a message similar to the following is reported:
DCD_RTSOCK_READ_SYNC_NOBUF: Can't get buffer for sync routing socket read
The cause of this message is usually an internal issue in the dcd process. It may also be due to a lack of system memory. Normally this is a transient issue, but the lack of memory could be due to a hardware failure.
Examine the following output to help determine the cause of this message:
show log messages show log chassisd
Look for any related events that occurred at or just before the DCD_RTSOCK_READ_SYNC_NOBUF message. Messages showing memory issues or memory hardware failures indicate that the DCD_RTSOCK_READ_SYNC_NOBUF message is likely due to hardware failure.
If there are no messages relating to memory issues, look for any related events that occurred at or just before the DCD_RTSOCK_READ_SYNC_NOBUF message that may have contributed to this error.
Perform these steps:
- Upgrade the Junos to JTAC recommended version
- If there are messages indicating memory hardware failure, open a case with your technical support representative to resolve the hardware failure.
- During a maintenance window, as it will impact transit traffic, try restarting the dcd process with the command: restart interface-control. For more information on restarting a process, refer to Restart a Junos Software Process.
- If restarting the dcd process does not resolve the issue, open a case with your technical support representative to investigate the issue further.