-
Notifications
You must be signed in to change notification settings - Fork 789
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add GameServer troubleshooting guide #1003
Add GameServer troubleshooting guide #1003
Conversation
Build Succeeded 👏 Build Id: 3c527386-c24b-4831-afde-095242cd472d The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
Preview of the page in question: https://5c0a1f5-dot-preview-dot-agones-images.appspot.com/site/docs/guides/troubleshooting/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All of the example output shows things that are working, so they don't really illustrate a scenario where a gameserver is unhealthy or a pod is crashing or something. Given that the section is about troubleshooting something that has gone wrong, would it make sense to have some output that actually shows something going wrong?
I like it. Done - PTAL! |
Build Succeeded 👏 Build Id: b187976d-c7f0-474f-8d72-e5595be8b961 The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
Build Succeeded 👏 Build Id: 0a9948b5-8cd8-422f-9559-30ab47ca9f27 The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
2019/08/16 21:26:24 Marking this server as ready | ||
``` | ||
|
||
Do note that this will only give the most recent container's logs (so we won't get the previous crash). Usually this is |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you run kubectl logs -p simple-udp-zqppv -c simple-udp
it will give you the logs from the prior execution of the container so that you can see the previous crash.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wait. You can do what now? runs off to try 😮
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done!
One last comment that I think is worth fixing before this merges. |
Including: - Using kubectl describe on the GameServer - Using kubectl describe on the backing pod - Viewing the gameserver logs - Pointing to a k8s guide of other kubectl techniques as well.
40ed38f
to
7da366e
Compare
Build Succeeded 👏 Build Id: a519a473-416a-4225-b748-8f4222e22798 The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
Including: