Re: Running Roundup on RedHat 7 Enterprise

Tonu Mikk <[email protected]>
Newsgroups gmane.comp.bug-tracking.roundup.user
Message-ID <CABDFm8hHdB9u1SeJ_Dxfdc_MLBpjS2WbK-BE6bnxbTaJDLFEgw@mail.gmail.com>
I have some progress to report!

When I replaced this line in the Apache virtual config file
ProxyPass /support/ http://drcweb-prd.oit.umn.edu:8080/support/

To this:
ProxyPass /support/ http://localhost:8080/support/
<http://drcweb-prd.oit.umn.edu:8080/support/>

It started to work.  I noticed that when I used the server's DNS name, the
proxy requests were made to 127.0.1.1:8080 instead of 127.0.0.1:8080 for
some reason.  This led me to use "localhost" instead.

Now I will try to set up an https connection.

On Thu, Sep 6, 2018 at 2:13 PM, Tonu Mikk <[email protected]> wrote:

> Thanks Matthieu!
>
> I tried the reverse proxy solution with Apache, but haven't gotten it to
> work so far.  Here are the details.
>
> I setup the tracker in /swadm/roundup/trackers/support
>
> I started the tracker with
> $roundup-server -p 8080 support=/swadm/roundup/trackers/support
>
> And I can see it running.  I can see the tracker service on localhost by
> going to
> $lynx localhost:8080
>
> I configured the support trackers web in config.ini to:
> web = http://drcweb-prd.oit.umn.edu/support/
>
> And my virtual host file looks like this.  I tried both the ProxyPass
> method and the RewriteRule.  Following the FAQ documentation -
> http://www.roundup-tracker.org/docs/FAQ.html#how-do-i-
> put-roundup-behind-apache
>
> <VirtualHost *:80>
>         ServerName drcweb-prd.oit.umn.edu
>         DocumentRoot /var/www/html/drcweb-prd
>         <Directory /var/www/html/drcweb-prd>
>                 Require all granted
>                 DirectoryIndex index.html
>         </Directory>
> #       <IfModule mod_proxy.c>
> #               ProxyPass /support/ http://drcweb-prd.oit.umn.edu:
> 8080/support/
> #
>         RewriteEngine on
>
>         ## Handle Support Issues
>         RewriteRule ^/support$  support/    [R]
>         RewriteRule ^/support/(.*)$ http://drcweb-prd.oit.umn.edu:
> 8080/support/$1 [P,L]
>
> </VirtualHost>
>
> I see the following error in Apache error log:
>
> [Thu Sep 06 13:54:35.344701 2018] [proxy:error] [pid 2665] (111)Connection
> refused: AH00957: HTTP: attempt to connect to 127.0.1.1:8080 (*) failed
> [Thu Sep 06 13:54:35.344772 2018] [proxy_http:error] [pid 2665] [client
> 160.94.228.6:55278] AH01114: HTTP: failed to make connection to backend:
> drcweb-prd.oit.umn.edu
>
> What may be wrong?
>
> Thanks!
>
> On Mon, Aug 27, 2018 at 7:54 AM, Matthieu Guionnet <
> [email protected]> wrote:
>
>> Hi,
>> I'm not using apache for roundup but I believe the solution with
>> virtualhost and mod_wsgi should work.
>>
>> I'm using nginx in reverse proxy mode in front of roundup server or
>> wsgi roundup with chaussette.
>>
>> For the wsgi server I've got one python script by instance and I gave
>> new server port if there's more than one instance by server. See the
>> gist links :
>> https://gist.github.com/gmat/e74098377126df2ef67cc9ab54375ea1
>>
>> This file should be also work with apache mod_wsgi.
>>
>> For reverse proxy solution with httpd, keep trying mod_proxy it should
>> work. No need of libproxy.
>>
>> Matthieu Guionnet.
>>
>>
>>
>>
>> Le mercredi 22 août 2018 à 10:44 -0500, Tonu Mikk a écrit :
>> > Hello Roundup users!
>> >
>> > I am looking for advice on how to implement Roundup web interface on
>> > RedHat 7 Enterprise.  I am currently running Roundup on RedHat 6
>> > using mod_python.  I have also integrated Roundup's user
>> > authentication with Shibboleth as documented in the wiki.  The
>> > support for RedHat 6 is expiring and we are being asked to move our
>> > Roundup installation to RedHat 7.  Ideally I would like to implement
>> > Roundup with Shibboleth on RedHat 7, but I have ran into obstacles.
>> >
>> > The mod_python is no longer supported in RedHat 7.  The
>> > recommendation is to use mod_wsgi, but I am not at all sure how to
>> > configure Apache virtual host with mod_wsgi to serve Roundup web
>> > interface.
>> >
>> > I also explored running Roundup's own web server and proxying it
>> > through Apache using the libproxy setup as described in the
>> > documentation.  However I noticed that libproxy module is not
>> > available to us in Apache.  We can use mod_proxy module but I haven't
>> > figured out the right configuration using mod_proxy module.  I have
>> > also not been successful in adding libproxy module to Apache.
>> >
>> > How should I try configure Roundup's web interface in RedHat 7 and
>> > Apache?
>> >
>> > Thanks!
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> > --
>> > Tonu Mikk
>> > Adaptive Technologist | Disability Resource Center |
>> > diversity.umn.edu/disability
>> > University of Minnesota | umn.edu
>> > [email protected] | 612-625-3307
>> > -------------------------------------------------------------------
>> > -----------
>> > Check out the vibrant tech community on one of the world's most
>> > engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> > _______________________________________________
>> > Roundup-users mailing list
>> > [email protected]
>> > https://lists.sourceforge.net/lists/listinfo/roundup-users
>
>
>
>
> --
> 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

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

_______________________________________________
Roundup-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/roundup-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.