RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

+++ This bug was initially created as a clone of Bug #611182 +++

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.

Noticed in mod_wsgi-3.2-3.el6

Thanks for the report.

It looks like the best fix for this is to have the internal (hard-coded) default correct, rather than configuring an over-ride for that internal default.

*** This bug has been marked as a duplicate of bug 966311 ***