Re: Roundup setup with mod_wsgi

Thanks Tom ...

I tried adding user=roundup in the apache config which now looked like this:

        WSGIScriptAlias / /swadm/roundup/trackers/oranges.py
        WSGIDaemonProcess support.roundup user=roundup group=support
threads=25
        WSGIProcessGroup support.roundup

The Apache restart failed probably because there is no user called
"roundup" on the server.  I then changed the directives to

        WSGIScriptAlias / /swadm/roundup/trackers/oranges.py
        WSGIDaemonProcess support.swadm user=swadm group=support threads=25
        WSGIProcessGroup support.swadm
This allowed me to restart the server.  But results in the same permission
denied error when I access the oranges.drc.umn.edu .

The Apache error log says:
[Thu Jan 24 15:47:39.334956 2019] [authz_core:error] [pid 38908] [client
160.94.228.13:49159] AH01630: client denied by server configuration:
/swadm/roundup/trackers/oranges.py
[Thu Jan 24 15:47:39.857760 2019] [authz_core:error] [pid 38908] [client
160.94.228.13:49159] AH01630: client denied by server configuration:
/swadm/roundup/trackers/oranges.py, referer: https://oranges.drc.umn.edu/




On Thu, Jan 24, 2019 at 3:39 PM Tom Ekberg <[email protected]> wrote:

> Tonu,
>
>
> Your WSGI file - oranges.py - closely matches mine. Mine differs only that
> it uses shibboleth, python3, xapian and venv. You apache config differs
> from mine. I have a user specified in in the WSGIDaemonProcess:
> user=roundup. I create a roundup user to run roundup. At least the
> permissions in the db subdirectories need to be such that the roundup user
> can create files in them. I made the whole tracker directory, where
> schema.py and config.ini are located, subdirectories too, owned by the
> roundup user. Another difference is I'm using <location> instead of
> <directory> (probably not important). Mine specifies Order deny,allow. Not
> sure what that means (I'd have to look it up). Here is my apache config
> lmit_oncall.conf:
>
>
> LogLevel info
>
> # Make sure trailing / is there.
> RedirectMatch           permanent ^/(lmit_oncall)$ /$1/
>
> WSGIDaemonProcess       tracker_lmit_oncall_pg user=roundup group=roundup\
>     processes=5 threads=1 \
>     home=/opt/roundup/trackers/lmit_oncall
> python-home=/usr/local/share/virtualenvs/tracker-env
>
> WSGIScriptAlias         /lmit_oncall
> /opt/roundup/trackers/lmit_oncall/apache/wsgi.py
>
> <location               /lmit_oncall>
>   WSGIProcessGroup      tracker_lmit_oncall_pg
>
>   AuthType              Shibboleth
>   ShibRequireSession    On
>   ShibUseEnvironment    On
>   Order                 deny,allow
>   Require               shib-attr isMemberOf ~ urn:mace:washington.edu:
> groups:(u_labmed_app_tracker-admin|u_labmed_div_informatics)
>
> </location>
>
> Not sure what AuthType defaults to if not specified. The
> apache documentation doesn't say. Did you look in the apache logs. Sometime
> you can find useful details there.
>
>
>
>
>
>
> ------------------------------
> *From:* Tonu Mikk <[email protected]>
> *Sent:* Thursday, January 24, 2019 12:52 PM
> *To:* [email protected]
> *Subject:* [Roundup-users] Roundup setup with mod_wsgi
>
> Hello,
>
> I am trying to configure roundup with Apache mod_wsgi, but so far I
> haven't succeeded.  Here is what my setup looks like.
>
> Tracker is installed in /swadm/roundup/trackers/support
> In the config.ini the tracker web is set to oranges.drc.umn.edu
> I have a file called oranges.py in /swadm/roundup/trackers with the
> following content:
> ---
> from roundup.cgi.wsgi_handler import RequestDispatcher
> tracker_home = '/swadm/roundup/trackers/support'
> application = RequestDispatcher(tracker_home)
> ---
> The Apache virtual config has the following:
>
> <VirtualHost *:443>
>         ServerName oranges.drc.umn.edu
>
>         WSGIScriptAlias / /swadm/roundup/trackers/oranges.py
>         WSGIDaemonProcess support.roundup group=support threads=25
>         WSGIProcessGroup support.roundup
>
>     <Directory /swadm/roundup/trackers>
>         <Files oranges.py>
>             Order allow,deny
>             Allow from all
>         </Files>
>     </Directory>
>
> # SSL directives omitted for brevity
> </VirtualHost>
>
> When I try to access https://oranges.drc.umn.edu I get a 403 message:
> Forbidden
> You don't have permission to access / on this server.
>
> I have created a group called "support" with the following content:
> support:x:1006:tmikk,swadm,apache,mail
>
> In the Roundup installation documentation for UNIX
> <http://roundup.sourceforge.net/docs/installation.html#unix-environment-steps> it
> says:
>
> "The tracker “db” directory should be chmod’ed g+sw so that the group can
> write to the database, and any new files created in the database will be
> owned by the group.
>
> This is something I have not done yet.  Can someone tell me what this
> command would look like in my case.  I am not entirely sure if I need to
> run it against a folder or a file.
>
> Is there anything else I need to change?  Thank you!
>
>
>
>
> --
> Tonu Mikk
> Adaptive Technologist | Disability Resource Center |
> diversity.umn.edu/disability
> University of Minnesota | umn.edu
> [email protected] | 612-625-3307
>


-- 
Tonu Mikk
Adaptive Technologist | Disability Resource Center |
diversity.umn.edu/disability
University of Minnesota | umn.edu
[email protected] | 612-625-3307

_______________________________________________
Roundup-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/roundup-users