Mailing-List: contact user-help@bloodhound.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@bloodhound.apache.org
Received-SPF: pass (nike.apache.org: domain of j@jdunk.com designates
 208.97.132.5 as permitted sender)
MIME-Version: 1.0
Date: Tue, 17 Sep 2013 01:25:41 -0700
Message-ID: 
 <CAKYe__M=VegUjH6GSgPNi3hyGyJ491C5gn_G7o79bwNmnLzFNQ@mail.gmail.com>
Subject: Running Bloodhound via apache: 404
From: Jared Duncan <j@jdunk.com>
To: user@bloodhound.apache.org
Content-Type: multipart/alternative; boundary=047d7b873d1a01d94c04e690118f

--047d7b873d1a01d94c04e690118f
Content-Type: text/plain; charset=UTF-8

Hi list.  I was successfully able to install and run bloodhound via tracd
just fine, but I'm getting a strange 404 situation when I try to access it
via apache instead.

I'm using the same VirtualHost block that was suggested by the installation
doc only with added directives for logging, and a ServerName and port 80
instead of 8000.

https://issues.apache.org/bloodhound/wiki/BloodhoundInstall#WebServer

My VirtualHost:

<VirtualHost *:80>
    ServerName bh.mydomain.com

    LogLevel warn
    ErrorLog /var/log/apache2/bh.mydomain.com-error.log
    CustomLog /var/log/apache2/bh.mydomain.com-access.log combined

    WSGIDaemonProcess bh_tracker user=bloodhound
python-path=/usr/local/bloodhound/installer/bloodhound/lib/python2.7/site-packages
    WSGIScriptAlias /bloodhound
/usr/local/bloodhound/installer/bloodhound/site/cgi-bin/trac.wsgi
    <Directory /usr/local/bloodhound/installer/bloodhound/site/cgi-bin>
        WSGIProcessGroup bh_tracker
        WSGIApplicationGroup %{GLOBAL}
        Order deny,allow
        Allow from all
    </Directory>
    <LocationMatch "/bloodhound/[^/]+/login">
        AuthType Digest
        AuthName "Bloodhound"
        AuthDigestDomain /bloodhound
        AuthUserFile
/usr/local/bloodhound/installer/bloodhound/environments/main/bloodhound.htdigest
        Require valid-user
    </LocationMatch>
</VirtualHost>

===

I ran trac-admin deploy and restarted apache of course.  What happens,
though, is any attempt to access that VirtualHost at any URI for that
subdomain it's configured for yields a 404, and the error log says this:

File does not exist: /etc/apache2/htdocs

I know that it's matching the VirtualHost block because the above error
gets written to the very file I uniquely specified in the ErrorLog
directive within that block.  (The unique access log gets hit also.)

So... anyone have an idea why it would be looking for an "htdocs" directory
within /etc/apache2/ instead of
/usr/local/bloodhound/installer/bloodhound/site/ ?

In case it's of any help, mod_wsgi emits the following "info" messages when
apache is started:

[info] mod_wsgi (pid=15156): Attach interpreter ''.
[info] mod_wsgi (pid=15156): Adding
'/usr/local/bloodhound/installer/bloodhound/lib/python2.7/site-packages' to
path.

===

Another thing: the Bloodhound installation doc says:

The user referred to in the WSGIDaemonProcess should be the user that you
> wish bloodhound to be run as and so that user must have the appropriate set
> of permissions to access the Bloodhound installation. Running with any
> special system level privileges should not be required and is not
> recommended.
>

...but it says nothing whatsoever about which permissions are needed on
which files/directories, so we are left to completely guess, and doing
something like

sudo chown -R bloodhound.www-data /usr/local/bloodhound; sudo chmod -R
ug+rwx /usr/local/bloodhound

...is ugly, inconvenient, and overly-permissive at best, and breaks things
at worst.  Is there a better way?

--047d7b873d1a01d94c04e690118f
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi list. =C2=A0I was successfully able to install and run =
bloodhound via tracd just fine, but I&#39;m getting a strange 404 situation=
 when I try to access it via apache instead.<div><br></div><div>I&#39;m usi=
ng the same VirtualHost block that was suggested by the installation doc on=
ly with added directives for logging, and a ServerName and port 80 instead =
of 8000.</div>
<div><br></div><div><a href=3D"https://issues.apache.org/bloodhound/wiki/Bl=
oodhoundInstall#WebServer">https://issues.apache.org/bloodhound/wiki/Bloodh=
oundInstall#WebServer</a><br></div><div><br></div><div>My VirtualHost:</div=
>
<div><br></div><div><div><font face=3D"courier new, monospace">&lt;VirtualH=
ost *:80&gt;</font></div><div><font face=3D"courier new, monospace">=C2=A0 =
=C2=A0 ServerName <a href=3D"http://bh.mydomain.com">bh.mydomain.com</a></f=
ont></div><div>
<font face=3D"courier new, monospace"><br></font></div><div><font face=3D"c=
ourier new, monospace">=C2=A0 =C2=A0 LogLevel warn<br></font></div><div><fo=
nt face=3D"courier new, monospace">=C2=A0 =C2=A0 ErrorLog /var/log/apache2/=
bh.mydomain.com-error.log</font></div>
<div><font face=3D"courier new, monospace">=C2=A0 =C2=A0 CustomLog /var/log=
/apache2/bh.mydomain.com-access.log combined</font></div><div><font face=3D=
"courier new, monospace"><br></font></div><div><font face=3D"courier new, m=
onospace">=C2=A0 =C2=A0 WSGIDaemonProcess bh_tracker user=3Dbloodhound pyth=
on-path=3D/usr/local/bloodhound/installer/bloodhound/lib/python2.7/site-pac=
kages</font></div>
<div><font face=3D"courier new, monospace">=C2=A0 =C2=A0 WSGIScriptAlias /b=
loodhound /usr/local/bloodhound/installer/bloodhound/site/cgi-bin/trac.wsgi=
</font></div><div><font face=3D"courier new, monospace">=C2=A0 =C2=A0 &lt;D=
irectory /usr/local/bloodhound/installer/bloodhound/site/cgi-bin&gt;</font>=
</div>
<div><font face=3D"courier new, monospace">=C2=A0 =C2=A0 =C2=A0 =C2=A0 WSGI=
ProcessGroup bh_tracker</font></div><div><font face=3D"courier new, monospa=
ce">=C2=A0 =C2=A0 =C2=A0 =C2=A0 WSGIApplicationGroup %{GLOBAL}</font></div>=
<div><font face=3D"courier new, monospace">=C2=A0 =C2=A0 =C2=A0 =C2=A0 Orde=
r deny,allow</font></div>
<div><font face=3D"courier new, monospace">=C2=A0 =C2=A0 =C2=A0 =C2=A0 Allo=
w from all</font></div><div><font face=3D"courier new, monospace">=C2=A0 =
=C2=A0 &lt;/Directory&gt;</font></div><div><font face=3D"courier new, monos=
pace">=C2=A0 =C2=A0 &lt;LocationMatch &quot;/bloodhound/[^/]+/login&quot;&g=
t;</font></div>
<div><font face=3D"courier new, monospace">=C2=A0 =C2=A0 =C2=A0 =C2=A0 Auth=
Type Digest</font></div><div><font face=3D"courier new, monospace">=C2=A0 =
=C2=A0 =C2=A0 =C2=A0 AuthName &quot;Bloodhound&quot;</font></div><div><font=
 face=3D"courier new, monospace">=C2=A0 =C2=A0 =C2=A0 =C2=A0 AuthDigestDoma=
in /bloodhound</font></div>
<div><font face=3D"courier new, monospace">=C2=A0 =C2=A0 =C2=A0 =C2=A0 Auth=
UserFile /usr/local/bloodhound/installer/bloodhound/environments/main/blood=
hound.htdigest</font></div><div><font face=3D"courier new, monospace">=C2=
=A0 =C2=A0 =C2=A0 =C2=A0 Require valid-user</font></div>
<div><font face=3D"courier new, monospace">=C2=A0 =C2=A0 &lt;/LocationMatch=
&gt;</font></div><div><font face=3D"courier new, monospace">&lt;/VirtualHos=
t&gt;</font></div></div><div><br></div><div>=3D=3D=3D</div><div><br></div><=
div>I ran trac-admin deploy and restarted apache of course. =C2=A0What happ=
ens, though, is any attempt to access that VirtualHost at any URI for that =
subdomain it&#39;s configured for yields a 404, and the error log says this=
:</div>
<div><br></div><div><font face=3D"courier new, monospace">File does not exi=
st: /etc/apache2/htdocs</font><br></div><div><br></div><div>I know that it&=
#39;s matching the VirtualHost block because the above error gets written t=
o the very file I uniquely specified in the ErrorLog directive within that =
block. =C2=A0(The unique access log gets hit also.)</div>
<div><br></div><div>So... anyone have an idea why it would be looking for a=
n &quot;htdocs&quot; directory within <font face=3D"courier new, monospace"=
>/etc/apache2/</font> instead of <font face=3D"courier new, monospace">/usr=
/local/bloodhound/installer/bloodhound/site/</font> ?</div>
<div><br></div><div>In case it&#39;s of any help, mod_wsgi emits the follow=
ing &quot;info&quot; messages when apache is started:</div><div><br></div><=
div><div><font face=3D"courier new, monospace">[info] mod_wsgi (pid=3D15156=
): Attach interpreter &#39;&#39;.</font></div>
<div><font face=3D"courier new, monospace">[info] mod_wsgi (pid=3D15156): A=
dding &#39;/usr/local/bloodhound/installer/bloodhound/lib/python2.7/site-pa=
ckages&#39; to path.</font></div></div><div><br></div><div>=3D=3D=3D</div><=
div><br>
</div><div>Another thing: the Bloodhound installation doc says:=C2=A0</div>=
<div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0p=
x 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-lef=
t-style:solid;padding-left:1ex">
<span style=3D"color:rgb(51,51,51);font-family:&#39;Helvetica Neue&#39;,Hel=
vetica,Arial,sans-serif;font-size:14px;line-height:20px">The user referred =
to in the WSGIDaemonProcess should be the user that you wish bloodhound to =
be run as and so that user must have the appropriate set of permissions to =
access the Bloodhound installation. Running with any special system level p=
rivileges should not be required and is not recommended.</span><br>
</blockquote><div><br></div><div>...but it says nothing whatsoever about wh=
ich permissions are needed on which files/directories, so we are left to co=
mpletely guess, and doing something like=C2=A0</div><div><br></div><div><fo=
nt face=3D"courier new, monospace">sudo chown -R bloodhound.www-data /usr/l=
ocal/bloodhound; sudo chmod -R ug+rwx /usr/local/bloodhound</font></div>
<div><br></div><div>...is ugly, inconvenient, and overly-permissive at best=
, and breaks things at worst. =C2=A0Is there a better way?</div></div>

--047d7b873d1a01d94c04e690118f--