Skip to content
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

Incorrect permissions #11

Open
RobertPaasche opened this issue Mar 17, 2018 · 4 comments
Open

Incorrect permissions #11

RobertPaasche opened this issue Mar 17, 2018 · 4 comments
Labels

Comments

@RobertPaasche
Copy link

RobertPaasche commented Mar 17, 2018

Not sure if git4c bug or confluence bug.

After Updateing Confluence from 6.7.1 to 6.7.2 The folder "/opt/atlassian/confluence/temp/git_source_plugin_cache" had wrong ownership. The ownership of ""/opt/atlassian/confluence/temp" was correct.

The ownership was root:root instead of the confluence user.

I think at least the errormessage shown in confluence should be improved in this case.

@bartoszbednarek
Copy link
Contributor

Hello, we will analize possibilities of checking. Plugin itself is not managing path to the temp directory as it is received from Confluence. However for sure there may be some option to check access rights. We will back with solution after internal talk about this problem. Thank you for contact with us!

@RobertPaasche
Copy link
Author

Thats the logentry which occured until the ownership was fixed:
-- referer: https://confluence.pripares.com/plugins/servlet/git4c/admin | url: /rest/doc/1.0/documentation/predefine | traceId: 7cd6cf6ff7a4873d | userName: rpaasche
2018-03-17 15:29:46,437 ERROR [pool-26-thread-5] [git4c.infrastructure.git.GitDiskCache] error LOCK - ERROR - Lock will be released for RepositoryPath=ssh://git@bitbucket.pripares.com:7999/dl/datalibrary.gitConDocException: Couldn't create a temp dir! at com.networkedassets.git4c.infrastructure.git.GitDiskCache:38

Adding the temp-path to "Couldn't create a temp dir" would have save some time ;)

@RobertPaasche
Copy link
Author

Sorry wrong button, the close wasn't intented.

@RobertPaasche
Copy link
Author

By the upgrade from 6.7.2 to 6.8.0 it happend again.
But by the upgrade from 6.8.0 to 6.8.1 it doesn't happend.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants