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

httpd error_log reporting permissions issue. #578

Open
nathanlcarlson opened this issue Sep 21, 2018 · 5 comments
Open

httpd error_log reporting permissions issue. #578

nathanlcarlson opened this issue Sep 21, 2018 · 5 comments
Assignees

Comments

@nathanlcarlson
Copy link
Contributor

From /var/log/httpd/error_log

(13)Permission denied: mod_wsgi (pid=23841): Unable to connect to WSGI daemon process 'cog-site' on '/etc/httpd/run/wsgi.23829.0.3.sock' as user with uid=48.

It seems there is a permission issue.

@nathanlcarlson nathanlcarlson self-assigned this Sep 21, 2018
@nathanlcarlson
Copy link
Contributor Author

nathanlcarlson commented Sep 21, 2018

It appears there is a line the specifies the group for the process in /etc/httpd/conf/esgf-httpd.conf

WSGIProcessGroup cog-site

After commenting this line out the permissions message error went away.

@nathanlcarlson
Copy link
Contributor Author

After spending some more time on this I have not yet figured out why this httpd config works for 2.x and not 3.x. If it is not essential that this WSGIProcessGroup parameter be set, it may be best to remove it.

@nathanlcarlson
Copy link
Contributor Author

The WSGIProcessGroup parameter was removed in #591

@nathanlcarlson
Copy link
Contributor Author

nathanlcarlson commented Nov 15, 2018

This is reopened as this has been reinvestigated. The cause of this permission error is a result of this code in the installer:

os.chmod("/var/run", stat.S_IWRITE)
os.chmod("/var/run", stat.S_IWGRP)
os.chmod("/var/run", stat.S_IWOTH)

This results in only the o+w mode being set as each command turns only that bit on and all others off.

@nathanlcarlson
Copy link
Contributor Author

PR #676 has been made to resolve this.

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

No branches or pull requests

1 participant