-
-
Notifications
You must be signed in to change notification settings - Fork 2
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
Resumable issue pushing a new project #515
Comments
One thing that might be causing permissions issues is that the project directories in /var/vcs/public are all owned by root with group owner www-data, and mode rwxr-x---. Meaning that the Apache process running as www-data cannot create new files (such as If we can get the process creating those directories to run as umask 002 rather than 022, so that it doesn't strip the group-writable bit, then www-data would be able to modify hgRunner.log. Alternately, we could set file permissions on the directories after creating them. The appropriate permissions are already set on the .hg folder inside: rwsrws---; the group "sticky bit" on the directory ensures that the appropriate group ownership will be created on files under that directory. But when we create a new project, we need to ensure that the top-level directory also gets the rwsrws--- permissions applied, so that PHP will be able to create a new hgRunner.log file in there. |
Correction: the two s's in the permissions are the "set user ID" and "set group ID" bits, respectively. The sticky bit, which is usually set on temp directories, shows as a The chmod command for setting rwsrws--- permissions is |
After testing this I created a new issue for resumable: sillsdev/hgresume#10 |
An admin reported this issue. I grabbed the logs. The project code has been changed from the original.
everything seems to be going fine (though there's warnings about php content length limits), until
04:18:31.385911
and then there's a permission issue opening hgRunner.log in the repo. After that the session fails until the client gives up.This is an intermitent issue. The user was able to send the project again later and it worked fine.
The text was updated successfully, but these errors were encountered: