bloodhound-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Branko ─îibej <br...@wandisco.com>
Subject Re: Installation Problems
Date Tue, 07 May 2013 20:23:37 GMT
On 07.05.2013 21:49, Dan Warburton wrote:
> If this is not the correct forum for installation questions, just point me in
> the right direction.
>
> I am installing bloodhound on Fedora 18.
>
> I have installed to : /var/www/bloodhound/..... in the path of apache, is this
> ok?

I don't know what the default Apache config looks like on Fedora, but I
suspect this will publish the whole Bloodhound installation (i.e.,
sources etc.) through your default *.80 virtual host, so you may want to
think twice about installing it there.

> Running tracd directly works:
> $ tracd ./bloodhound/environments/main --port=8000
>
>
> I've added this stanza to the /etc/httpd/conf/
>
> # try out wsgi
>
> WSGIScriptAlias /bloodhoundt
> /var/www/bloodhound/apache-bloodhound-0.5.3/installer/bloodhound/site/cgi-bin/trac.wsgi
>
> ### start bloodhound in a Virtural Host
>
>  <VirtualHost *:8080>
>   WSGIDaemonProcess bloodhound_tracker user=apache
> python-path=/var/www/bloodhound/apache-bloodhound-0.5.3/installer/bloodhound/lib/python2.7
>    WSGIScriptAlias /bloodhound
> /var/www/bloodhound/apache-bloodhound-0.5.3/installer/bloodhound/site/cgi-bin/trac.wsgi
>    <Directory
> /var/www/bloodhound/apache-bloodhound-0.5.3/installer/bloodhound/site/cgi-bin>
>      WSGIProcessGroup bloodhound_tracker
>      WSGIApplicationGroup %{GLOBAL}
>      Order deny,allow
>      Allow from all
>    </Directory>
>    <LocationMatch "/bloodhound/[^/]+/login">
>      AuthType Digest
>      AuthName "Bloodhound"
>      AuthDigestDomain /bloodhound
>      AuthUserFile
> /var/www//bloodhound/apache-bloodhound-0.5.3/installer/bloodhound/environments/main/bloodhound.htdigest
>      Require valid-user
>    </LocationMatch>
>  </VirtualHost>
>
> The virtualHost on 8080 does not answer.
>
> Going directly to http://localhost/bloodhoundt produces an internal server
> error:
> This is in the error_log:
>
> [Tue May 07 14:25:18.356745 2013] [:error] [pid 18846] [client 127.0.0.1:57835]
> mod_wsgi (pid=18846): Exception occurred processing WSGI script
> '/var/www/bloodhound/apache-bloodhound-0.5.3/installer/bloodhound/site/cgi-bin/trac.wsgi'.
> [Tue May 07 14:25:18.356787 2013] [:error] [pid 18846] [client 127.0.0.1:57835]
> Traceback (most recent call last):
> [Tue May 07 14:25:18.356804 2013] [:error] [pid 18846] [client 127.0.0.1:57835]
>   File
> "/var/www/bloodhound/apache-bloodhound-0.5.3/installer/bloodhound/site/cgi-bin/trac.wsgi",
> line 30, in application
> [Tue May 07 14:25:18.356849 2013] [:error] [pid 18846] [client 127.0.0.1:57835]
>     from trac.web.main import dispatch_request
> [Tue May 07 14:25:18.356864 2013] [:error] [pid 18846] [client 127.0.0.1:57835]
> ImportError: No module named trac.web.main
>
>
> Thanks for any Help.

I believe the problem is that /var/www/bloodhound is a Python virtual
environment, but your mod_wsgi configuration does not take that into
account. Perhaps this document on using mod_wsgi with virtualenv can help:

    https://code.google.com/p/modwsgi/wiki/VirtualEnvironments

We should probably add a link to that in our docs somewhere.

-- Brane

-- 
Branko ─îibej
Director of Subversion | WANdisco | www.wandisco.com


Mime
View raw message