|
I use lynx.
lynx http://192.168.0.233 or 234 are just working fine. I got the test page.
Everything looks normal. Only if I lynx <vip> on load balancer machine, I
only gets the load balancer's test page, meaning it is not load balanced.
Don't know why. Maybe the load balancer is not supposed to process local
generated requests.
You see, if I put sslproxy and load balancer on different machine, the
sslproxy works just fine and I got load balanced pages too. But the problem
is if I put them together on one machine, it gets problem.
Theoretically, the first setup should be correct, because sslproxy is
supposed to switch the port from 443 to 80. Only if the load balancer
intercepts the packets first. Any idea?
Thanks again
Longhua
-----Original Message-----
From: lvs-users-bounces@xxxxxxxxxxxxxxxxxxxxxx
[mailto:lvs-users-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Mark
Sent: Wednesday, October 12, 2005 4:48 PM
To: 'LinuxVirtualServer.org users mailing list.'
Subject: RE: LVS problem with SSLProxy
Your first setup seems correct to me.
Do you have lynx or curl or some other text-based web-browser on the
loadbalancer machine?
What do you get when you load http://192.168.0.233/index.html into that
browser (e.g. "lynx http://192.168.0.233";)?
You can also just "telnet 192.168.0.233 80" and enter:
GET /index.html<ENTER><ENTER>
The response needs to have the string "Test Page" somewhere in the HTML
source.
What do you see in the ldirectord log files? It should say something like:
Deleted fallback server: 127.0.0.1:80
Added real server: 192.168.0.233:80
MARK
|
