|
Justin Albstmeijer wrote:
>
> Hi,
>
> I have a working lvs_dr http setup.
> As soon as I change http to https in the SERVICE line, the configure
> script seems to do something wrong.
> #ipvsadm
> IP Virtual Server version 1.0.10 (size=4096)
> Prot LocalAddress:Port Scheduler Flags
> -> RemoteAddress:Port Forward Weight ActiveConn InActConn
> TCP 192.168.1.210:0 rr persistent 360
> -> 192.168.1.101:0 Route 1 0 0
> -> 192.168.1.102:0 Route 1 0 0
> -> 192.168.1.103:0 Route 1 0 0
>
> ----------------------------------------------------------------------
>
> I would expect ip:https or ip:443 instead of ip:0
> Also tried SERVICE=t 443 rr 192.168.1.101 192.168.1.102 192.168.1.103
443 and https are interchangeable via /etc/services, so you aren't doing
anything different by changing "https" to "443".
It's (ahem) a feature. The script is mainly designed for my testing
and is out there to help newbies setting up LVS. It does a lot
of checking and gives hints as to the problem when it fails.
It also has some "smarts" - if you're running https, you want persistence
to keep the client on the same realserver. Back when I wrote the
script, port 0 was the way of handling this. If you're going into
production today with an https/http site, you'd probably use persistent
fwmarks.
If you want to setup a non-persistent service on port 443 and have got the hang
of how LVS works, then you should just set it up from the command
line with ipvsadm
Joe
--
Joseph Mack PhD, High Performance Computing & Scientific Visualization
SAIC, Supporting the EPA Research Triangle Park, NC 919-541-0007
Federal Contact - John B. Smith 919-541-1087 - smith.johnb@xxxxxxx
|
