Bug 118515 - How to use load balancer installed & configured by Redhat
Summary: How to use load balancer installed & configured by Redhat
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise CMS
Classification: Retired
Component: APLAWS
Version: nightly
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: ccm-bugs-list
QA Contact: Daniel Berrangé
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-03-17 11:47 UTC by Chris Kelly
Modified: 2007-04-18 17:04 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-03-17 16:00:26 UTC
Embargoed:


Attachments (Terms of Use)

Description Chris Kelly 2004-03-17 11:47:04 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; 
Q312461)

Description of problem:
On Tuesday 2/3/2004 Matthew Booth installed/configured Apache & Squid 
on a single RHEL 3 machine to act as a 'load balancer' for a pre-
existing 'staging server' on a separate machine on which APLAWS+ beta 
1 with Resin & postgres had been installed.

Our problem is that we don't how to change URLS for APLAWS+ which 
were previously used to access the staging server in order to use the 
load balancer.

I understood that if 

1. the IP address of the staging server was 128.1.5.110  
2. the load balancer was at 128.1.5.112

Then

A. http://128.1.5.110:8080 would be accessing the staging server 
directly 
B. http://128.1.5.112:8080 would be doing the same, except that the 
load balancer would be used 

A works to access APLAWS+, but B gives us a 'page cannot be 
displayed' error and has always done so

Have I misunderstood?
What URLS should be used to access the staging server directly and 
via the load balancer?

Thanks   

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Browse to http://128.1.5.112:8080
2.
3.
    

Additional info:

Comment 1 Daniel Berrangé 2004-03-17 16:00:26 UTC
Closing because this is a technical support query not a bug.



Note You need to log in before you can comment on or make changes to this bug.