Set ownership on mongo config files#2
Closed
DavidWittman wants to merge 2 commits intobennojoy:masterfrom
Closed
Conversation
Without setting the ownership of the config files properly, the mongo user is unable to read them and fails with the following message: > ERROR: could not read from config file Setting the ownership to the mongo user and group fixes this issue.
Contributor
Author
|
Looks like the same ownership is required for |
Otherwise, the mongod user won't be able to read it when attempting to initilize the replica set.
Contributor
Author
|
Whoops... f73ba00 wasn't necessary. I'm going to open a new PR without it. |
Contributor
Author
|
Closing in preference of #3 |
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
1 participant
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.
Without setting the ownership of the config files properly,
the mongo user is unable to read them and fails with the
following message:
Setting the ownership to the mongo user and group fixes this issue.