github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-08-01 07:47:56 +00:00
Code Issues Projects Releases Wiki Activity

Add instructions on how to debug a crashed pod

Browse Source 
When I was using `kubeadm init`, I ran into an issue where I had passed an
invalid flag through the kubeadm config file. The flag was being passed into
apiserver and preventing it from launching with a "unknown flag" error.

The flag in question is (other flags elided for clarity):

```
admission-control: ...,GenericAdmissionWebhook,...
```

Since this prevented the apiserver from coming up, the setup timed out
and gave me the error message I just modified.

It would be better if the config was vetted more thoroughly, but I think
documenting the backup strategy for viewing logs in case of failure is
also valuable.
This commit is contained in:
Andrew Z Allen 2018-02-11 12:59:26 -07:00 committed by GitHub
parent 19829a24f1
commit bb5cfa8d55
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 7 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
cmd/kubeadm/app/cmd/init.go
View File

@ -103,6 +103,13 @@ var (
If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands: If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:
- 'systemctl status kubelet' - 'systemctl status kubelet'
- 'journalctl -xeu kubelet' - 'journalctl -xeu kubelet'
Additionally a service may not have come up in docker. If that's the case, you can enumerate all docker
containers that have been started (including ones that have crashed and exited) by running the following commands:
- 'docker ps -a'
Once you have that list, you can inspect the logs for any job with:
- 'docker logs $INSTANCEID'
`))) `)))
) )