Bug 611182 - Default configuration does not specify socket prefix
Summary: Default configuration does not specify socket prefix
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: mod_wsgi
Version: el5
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Orphan Owner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 974995 974997
TreeView+ depends on / blocked
 
Reported: 2010-07-04 06:48 UTC by Felix Schwarz
Modified: 2017-04-06 10:37 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 974995 974997 (view as bug list)
Environment:
Last Closed: 2017-04-06 10:37:03 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Felix Schwarz 2010-07-04 06:48:24 UTC
Currently mod_wsgi does not declare WSGISocketPrefix so mod_wsgi in daemon mode tries to create a socket in /etc/httpd/logs/ which will fail.

I propose to add these lines to /etc/httpd/conf.d/wsgi.conf:

<IfModule mod_wsgi.c>
   WSGISocketPrefix /var/run/mod_wsgi
</IfModule>

Therefore new users don't have to set it explicitely and mod_wsgi on EPEL will be a bit easier to use.

Comment 1 Joe Orton 2013-10-21 21:44:33 UTC
This was corrected by fixing httpd to export the correct run-time path.  mod_wsgi now uses "/run/httpd/wsgi" as the default hard-coded prefix.

mod_wsgi-3.4-6.fc18.x86_64

Comment 2 Joe Orton 2013-10-21 21:47:05 UTC
Sorry, wrong bug page!  It would be better to fix this by "correcting" the definition of DEFAULT_REL_RUNTIMEDIR in mod_wsgi.c in EPEL, there shouldn't be a need to fix the default config.  Arguably it is a RHEL httpd bug anyway, but it's unlikely we'd change the exported DEFAULT_REL_RUNTIMEDIR in an update.

Comment 3 Fedora End Of Life 2017-04-06 10:37:03 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.