The RTLOGD_LOG_BIND_ERROR message is reported into the system message file whenever the J-series Services Router (JSR) log daemon fails to bind to the JSR log forwarder. This article documents an approach to troubleshoot this problem.

This message is generated by the system log utility for real-time processing of packets for security control (rtlogd) on routers running the Junos software with Enhanced Services. Enhanced services is currently only supported on J-series and SRX routers.

The RTLOGD_LOG_BIND_ERROR message is logged each time the JSR log daemon fails to bind to the JSR log forwarder. Junos JSR log daemon receives JSR log from a JSR log forwarder. The JSR log daemon failed to connect to the forwarder.

When the RTLOGD_LOG_BIND_ERROR event occurs, a message similar to the following is reported:

The message includes the error returned by the bind call.

The cause is possibly a hardware fault in the Packet Forwarding Engine (PFE) or a software issue with the JSR log daemon.

Examine the following output to help determine the cause of this message:

Look for any related events that occurred at or just before the RTLOGD_LOG_BIND_ERROR message. If there are messages indicating a hardware problem, then the cause is likely due to a hardware fault. Any other events may have caused this message, such as a commit. If so, the rtlogd error may be due to that one type of event occurring.

Perform these steps:

  1. If the message is due to a hardware fault, open a case with your technical support representative to resolve the hardware issue.
  2. During a maintenance window, as it will impact transit traffic, try restarting the router with the command: request system reboot. For more information on this command, see the request system reboot command reference.

About the author


Leave a Comment