Thanks for following up. Amending the previous httpd.conf as shown below successfully invokes the mod_wsgi auth functions.
httpd.conf: CoreDumpDirectory /tmp/apache2-gdb-dump LogLevel debug listen 8080 <VirtualHost *:8080> ServerName svn.mydomain.org DocumentRoot /var/www <Location /index.html> WSGIAccessScript /var/lib/wsgi/access.wsgi </Location> </VirtualHost> <VirtualHost *:80> ServerName svn.mydomain.org DocumentRoot /var/www <Location /index.html> AuthType Basic AuthName "WSGIAuth" AuthBasicProvider wsgi WSGIAuthUserScript /var/lib/wsgi/access.wsgi Require valid-user WSGIAuthGroupScript /var/lib/wsgi/access.wsgi Require group authorized </Location> </VirtualHost> -- Larry Howard, Sr. Research Scientist Institute for Software Integrated Systems, Vanderbilt University On Oct 29, 2013, at 7:58 AM, Branko Čibej <br...@wandisco.com> wrote: > On 29.10.2013 13:45, Howard, Larry P wrote: >> An Apache configuration serving Subversion repositories, with mod_wsgi 3.3 >> authentication provider, causes per request segfaults in Apache 2.2.22 with >> mod_dav_svn from Subversion 1.7.13. If mod_wsgi auth directives are removed >> from the Apache configuration, then repositories are served properly. > > What if you remove the SVN configuration and just set up a plain server > with WSGI authentication? Given your description of the issue, and the > fact that the WSGI process crashes, I'd sooner suspect mod_wsgi or your > access script, even though I can't see anything obviously wrong with them. > > -- Brane > > > -- > Branko Čibej | Director of Subversion > WANdisco // Non-Stop Data > e. br...@wandisco.com
smime.p7s
Description: S/MIME cryptographic signature