The syslog-ng service in Okta Access Gateway fails to restart due to an underlying configuration or syntax error. Resolve this issue by accessing the appliance shell, identifying the specific failing command from the service status, and executing it manually to pinpoint the exact file and line number causing the failure.

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

1. Login to the appliance using the launch shell and check the syslog-ng status.

   sudo systemctl status syslog-ng
   

   • Status should show which command specified with ExecStart is failing, and that can be executed on the terminal to see any error if it is not visible in journalctl

   • (Output from systemctl status above) ExecStart= /usr/sbin/syslog-ng -F -p /var/run/syslogd.pid (code=exited, status=1/FAILURE)

2. Execute the same command to check the actual error. 

sudo /usr/sbin/syslog-ng -F -p /var/run/syslogd.pid

The output will show the file name or line number where the service failed. Once the reported issue has been fixed, restart the service.
 

Related References

• Launch Shell