The RTLOGD_GET_TNP_ADDRESS_FAILED message is reported into the system message file whenever the J-series Services Router (JSR) log daemon failed to determine local TNP address used to receive JSR log. 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_GET_TNP_ADDRESS_FAILED message is logged each time the JSR log daemon fails to determine the local TNP address used to receive the JSR log.
When the RTLOGD_GET_TNP_ADDRESS_FAILED event occurs, a message similar to the following is reported:
RTLOGD_GET_TNP_ADDRESS_FAILED: Failed to get local TNP adress: <error-message>
The message includes the error returned by the function call.
The cause is likely due to a software issue within the JSR log daemon.
Examine the following output to help determine the cause of this message:
show log messages
show log rtlogd
Look for any related events that occurred at or just before the RTLOGD_GET_TNP_ADDRESS_FAILED message. 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:
- 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.