mirror of
https://github.com/edgelesssys/constellation.git
synced 2024-12-12 09:24:24 -05:00
76 lines
2.6 KiB
Markdown
76 lines
2.6 KiB
Markdown
|
# 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:
|
||
|
|
|
||
|
|
<tabs groupId="csp">
|
||
|
|
<tabItem value="azure" label="Azure">
|
||
|
|
|
||
|
|
1. In your Azure subscription find the Constellation resource group.
|
||
|
|
2. Inside the resource group find the Application Insights resource called `constellation-insights-*`.
|
||
|
|
3. On the left-hand side go to `Logs`, which is located in the section `Monitoring`.
|
||
|
|
+ Close the Queries page if it pops up.
|
||
|
|
5. 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"`
|
||
|
|
|
||
|
|
</tabItem>
|
||
|
|
<tabItem value="gcp" label="GCP">
|
||
|
|
|
||
|
|
1. Select the project that hosts Constellation.
|
||
|
|
2. Go to the `Compute Engine` service.
|
||
|
|
3. 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](https://cloud.google.com/logging/quotas#logs_retention_periods).
|
||
|
|
|
||
|
|
:::
|
||
|
|
|
||
|
|
</tabItem>
|
||
|
|
<tabItem value="aws" label="AWS">
|
||
|
|
|
||
|
|
1. Open [AWS CloudWatch](https://console.aws.amazon.com/cloudwatch/home)
|
||
|
|
2. Select [Log Groups](https://console.aws.amazon.com/cloudwatch/home#logsV2:log-groups)
|
||
|
|
3. Select the log group that matches the name of your cluster.
|
||
|
|
4. Select the log stream for control or worker type nodes.
|
||
|
|
|
||
|
|
</tabItem>
|
||
|
|
</tabs>
|
||
|
|
|
||
|
|
## Connect to nodes
|
||
|
|
|
||
|
|
Debugging via a shell on a node is [directly supported by Kubernetes](https://kubernetes.io/docs/tasks/debug/debug-application/debug-running-pod/#node-shell-session).
|
||
|
|
|
||
|
|
1. Figure out which node to connect to:
|
||
|
|
|
||
|
|
```sh
|
||
|
|
kubectl get nodes
|
||
|
|
# or to see more information, such as IPs:
|
||
|
|
kubectl get nodes -o wide
|
||
|
|
```
|
||
|
|
|
||
|
|
2. Connect to the node:
|
||
|
|
|
||
|
|
```sh
|
||
|
|
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`.
|
||
|
|
|
||
|
|
3. Once finished, clean up the debug pod:
|
||
|
|
|
||
|
|
```sh
|
||
|
|
kubectl delete pod node-debugger-constell-worker-xksa0-000000-bjthj
|
||
|
|
```
|