Hello Paul, On 27/02/2011, at 20:45, pub crawler wrote:
> We have a simple setup that we've been running with the Cherokee > FAILOVER balancer with a single information source - meaning no > failover. Just left it that way after prior testing issues. > > Attempting to add a second information source (a remote site server). > The source adds just fine. > > When I do the graceful restart however, all the traffic goes to this > second information source and nothing goes to the original source. If > I change the order of the sources to make the remote server first in > order, requests still end up at the remote server and not local > server. Adding the second remote information source makes all the > traffic go solely to the remote server. > > Both locations work just fine individually, it's only when I try > putting them together in failover balancer that I see any failure and > I suspect it's Cherokee. > > Our setup looks like this: > > Information sources: > balance proxy 127.0.0.1:8499 (balance load balancer in front of our > application server) > remote xx.xx.xx.xx:80 (ip of remote server) > > Balancer type: FAILOVER > > Any recommendations on debugging this? It could be due to bug #1072: http://code.google.com/p/cherokee/issues/detail?id=1072 One of the Javascript pieces of code we are using in Cherokee-admin fails when it's in a scrollable area. We easiest work-around is to decrease the zoom out on the browser until the scroll disappears. -- Octality http://www.octality.com/ _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
