NTP Service Showing Failure for serviceLog.sh in Status after Reboot in Okta

After rebooting an Okta Access Gateway (OAG) node, the Network Time Protocol (NTP) status displays a failure for the serviceLog.sh script. This occurs because the NTP service attempts to log the start process while the syslog-ng service is still starting. Administrators can ignore this error or restart the NTP service to clear the failure status. The ntpd service displays an active status without other issues, but the following error message appears in the status:

Process: <pid> ExecStartPre=/opt/oag/bin/serviceLog.sh ntpd start (code=exited, status=1/FAILURE)

• Okta Identity Engine (OIE)
• Okta Classic Engine
• Okta Access Gateway (OAG)

The Network Time Protocol (NTP) service attempts to log the start process while the syslog-ng service is still starting.

How is the serviceLog.sh failure resolved?

Administrators can safely ignore this error. To remove the error from the status, restart the Network Time Protocol service from the Okta Access Gateway management console.

1. Log in to the Okta Access Gateway management console.
2. Select 2 - Services > 3 - NTP > 4 - Restart NTPD.
3. Verify the status by selecting 2 - Services > 3 - NTP > 5 - Check status.