Bug 717404
Summary: | python26-imaging MemoryError exception | ||
---|---|---|---|
Product: | [Fedora] Fedora EPEL | Reporter: | jspam |
Component: | python26 | Assignee: | Adrien Devresse <adev88> |
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | el5 | CC: | dmalcolm, fschwarz, zart |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-04-06 10:03:28 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
jspam
2011-06-28 18:39:10 UTC
I've configured mod_wsgi to run in daemon mode. This forces app to run under specified uid/gid with it's own writable home. First, make runtime directory for unix sockets. It must be writable only by root (mod_wsgi docs warn against using /tmp) but accessible by others, so default logs directory won't do since it has o-x. # mkdir /var/run/mod_wsgi # restorecon /var/run/mod_wsgi /etc/httpd/conf.d/z.conf: (could be wsgi.conf as well) <IfModule wsgi_module> WSGISocketPrefix /var/run/mod_wsgi/wsgi WSGIDaemonProcess wsgi user=username group=username ...other settings here... WSGIProcessGroup wsgi </IfModule> And to solve final bit (assuming selinux is enabled): # setsebool -P httpd_tmp_exec 1 Worked for me on Fedora 15 with python 2.7. Fedora EPEL 5 changed to end-of-life (EOL) status on 2017-03-31. Fedora EPEL 5 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora or Fedora EPEL, please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |