Troubleshoot application startup failures - Application Real-Time Monitoring Service

If an application fails to start in a Container Service for Kubernetes (ACK) cluster with Application Real-Time Monitoring Service (ARMS) enabled, check the ack-onepilot logs to identify the cause.

Note

In the following commands, k is an alias for kubectl. If this alias is not configured in your environment, replace k with kubectl.

Step 1: Get the ack-onepilot pod name

Each ack-onepilot pod name includes a random suffix. List all pods in the ack-onepilot namespace:

k get pod -n ack-onepilot

Example output:

NAME                                             READY   STATUS    RESTARTS   AGE
ack-onepilot-ack-onepilot-5b7d4c8f9a-xk9mn      1/1     Running   0          3d

Note the full pod name (including the suffix such as 5b7d4c8f9a-xk9mn).

Step 2: View the ack-onepilot logs

Stream the pod logs with the following command. Replace XXXX-XXXX with the suffix from Step 1.

k logs -f ack-onepilot-ack-onepilot-XXXX-XXXX -n ack-onepilot

Review the output for errors related to the startup failure.