Reworked the Troubleshooting guide and added#316
Merged
prashanthpai merged 2 commits intogluster:masterfrom Jan 2, 2018
nbalacha:b2
Merged
Reworked the Troubleshooting guide and added#316prashanthpai merged 2 commits intogluster:masterfrom nbalacha:b2
prashanthpai merged 2 commits intogluster:masterfrom
nbalacha:b2
Conversation
added 2 commits
December 30, 2017 11:46
component specific troubleshooting steps. Signed-off-by: N Balachandran <nbalacha@redhat.com>
doc file. Signed-off-by: N Balachandran <nbalacha@redhat.com>
prashanthpai
reviewed
Jan 2, 2018
| This guide lists issues you may run into on your Gluster setup and provides information on how to recover from them. | ||
| You can also reach out to the Gluster community for help. | ||
| This guide describes some commonly seen issues and steps to recover from them. | ||
| If that doesn’t help, you can also reach out to the [Gluster community](https://www.gluster.org/community/), in which case the guide also describes what information needs to be provided in order to debug the issue. At minimum, we need the version of gluster running and, in most cases, the output of `gluster volume info`. |
Contributor
There was a problem hiding this comment.
How about ask for logs too ? And mention their default location.
Author
There was a problem hiding this comment.
The logs will be added as a separate topic and in addition to their location, will also contain information on log levels and msgids
|
|
||
| When things go wrong, identifying the problem and getting the necessary information in order to diagnose it is the first step in troubleshooting your Gluster setup. As Gluster operations involve interactions between multiple processes, this can involve multiple steps. | ||
|
|
||
| ### What Happened? |
Contributor
There was a problem hiding this comment.
Suggestion: This section doesn't seem to contain much yet. You may find it hard to reason about generic failure such as "an operation failed" and map it to a specific troubleshooting guide. The high memory usage link can be part of the list described above.
Author
There was a problem hiding this comment.
I plan to include information as to how to determine the logs to look at as well as what information to provide.
prashanthpai
approved these changes
Jan 2, 2018
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
component specific troubleshooting steps.
Signed-off-by: N Balachandran nbalacha@redhat.com