The RTLOGD_DAEMONIZE_FAILED message is reported into the system message file whenever the J-series Services Router (JSR) log daemon could not create a version of itself to run in the background as a daemon. 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_DAEMONIZE_FAILED message is logged each time the JSR log daemon could not create a version of itself to run in the background as a daemon.
When the RTLOGD_DAEMONIZE_FAILED event occurs, a message similar to the following is reported:
RTLOGD_DAEMONIZE_FAILED: Aborting, unable to run in the background as a daemon: <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_DAEMONIZE_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.