|
I was assuming that this line:
#SERVICE line format - proto port scheduler IP[,weight] [IP[,weight]]
meant that http was the service, rr the scheduler (round robin) and I
could insert the port myself. This is zope and apache proxies on port 80
but access to the zope content is on 8080 so therefore I am doing rr on
8080 (as shown below). I'm using ZEO on the backend so I have two Zope
webservers linked to a single ZEO server listening to intranet requests on
port 8080:
SERVICE=t 8080 rr 10.80.1.21 10.80.1.22
after changing this, the script worked. I'm sure I'll have more problems
in the future but for now I'm on wide-open :-) thanks.
-Matt
> SERVICE=t http 8080 rr 10.80.1.21 10.80.1.22
you've supplied the port twice there (one in text form 'http', one in
numerical, '8080'), so it thinks rr is the address of a real server
from the lvs docs, the format of the SERVICE line is:
proto port scheduler IP|name:port[,weight] [IP|name:port[weight]]
so I'm guessing you want
SERVICE=t 80 rr 10.80.1.21:8080 10.80.1.22:8080
This should assign your two real server's http processes (listening on
port
8080, right?), to the virtual service on port 80.
If your real servers are listening on port 80, just replace 8080 with 80.
I haven't used the configure script before, so I'm just reading this from
the
docs. So I may be grossy incorrect :D
Jeremy
_______________________________________________
LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
or go to http://www.in-addr.de/mailman/listinfo/lvs-users
|
