Troubleshoot Runtime Instances

Out of sync runtime instance

Occasionally, a Kong Gateway runtime instance might get out of sync with the Konnect control plane. If this happens, you will see the status Out of sync on the Runtime Instances page, meaning the control plane can’t communicate with the instance.

Troubleshoot the issue using the following methods:

• Ensure the runtime instance is running. If it’s not running, start it; if it is running, restart it.

  Check the sync status in the Runtime Manager.

• Check the logs of the runtime that’s appearing as Out of sync. The default directory for Kong Gateway logs is /usr/local/kong/logs.

  If you find any of the following errors:

  • Runtime instance failed to connect to the control plane.
  • Runtime instance failed to ping the control plane.
  • Runtime instance failed to receive a ping response from the control plane.

  You may have an issue on the host network where the instance resides. Diagnose and resolve the issue, then restart the instance and check the sync status in the Runtime Manager.

• If the logs show a license issue, contact Kong Support.

If you are unable to resolve sync issues using the above methods, contact Kong Support.

Missing functionality

If a Konnect feature isn’t working on your runtime instance, the version may be out of date.

Verify that your instance versions are up to date:

1. Open Runtime Manager, then open your runtime group.

2. Click + Add runtime instance and check the Kong Gateway version in the code block. This is the version that the Konnect control plane is running.

3. Return to the runtime instances page.

4. Check the runtime instance versions in the table. If you see an instance running an older version of Kong Gateway, your runtime instance may need upgrading.

If your version is up to date but the feature still isn’t working, contact Kong Support.