Attempt to fix neo4j.conf permission errors #237
Merged
Conversation
This file contains 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
jennyowen
added a commit
that referenced
this pull request
Apr 15, 2020
folders mounted under neo4j home were only give read access to `root` instead of `neo4j`. Change #237 applied a chmod 700 to *all* files and folders under home instead of ones that were only owned by root. This meant that all mounted files under home which were not owned by neo4j became unreadable.
This was referenced Apr 15, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Some customers report permissions errors on start up, even when no volumes are mounted.
I haven't been able to replicate it, but I noticed this line was not actually setting ownership on the folders under neo4j_home. Perhaps fixing this will help??
#223