Troubleshooting

This section aids you in finding problems when working with Constellation.

Cloud logging

To provide information during early stages of the node's boot process, Constellation logs messages into the cloud providers' log systems. Since these offerings aren't confidential, only generic information without any sensitive values are stored. This provides administrators with a high level understanding of the current state of a node.

You can view these information in the follow places:

In your Azure subscription find the Constellation resource group.
Inside the resource group find the Application Insights resource called constellation-insights-*.
On the left-hand side go to Logs, which is located in the section Monitoring.
- Close the Queries page if it pops up.
In the query text field type in traces, and click Run.

To find the disk UUIDs use the following query: traces | where message contains "Disk UUID"

Select the project that hosts Constellation.
Go to the Compute Engine service.
On the right-hand side of a VM entry select More Actions (a stacked ellipsis)
- Select View logs

To find the disk UUIDs use the following query: resource.type="gce_instance" text_payload=~"Disk UUID:.*\n" logName=~".*/constellation-boot-log"

:::info

Constellation uses the default bucket to store logs. Its default retention period is 30 days.

:::

Open AWS CloudWatch
Select Log Groups
Select the log group that matches the name of your cluster.
Select the log stream for control or worker type nodes.

Connect to nodes via SSH

Debugging via a shell on a node is directly supported by Kubernetes.

Figure out which node to connect to:

kubectl get nodes
# or to see more information, such as IPs:
kubectl get nodes -o wide

Connect to the node:
```
kubectl debug node/constell-worker-xksa0-000000 -it --image=busybox
```
You will be presented with a prompt.

The nodes file system is mounted at /host.

Once finished, clean up the debug pod:

kubectl delete pod node-debugger-constell-worker-xksa0-000000-bjthj

2.6 KiB Raw Blame History

Troubleshooting

Cloud logging

Connect to nodes via SSH

2.6 KiB

Raw Blame History