Load Balancer stopped Balancing
-
I gitsynced. Instead of displaying "unknown" it says "Gathering Data"
I'll see what tomorrows snapshot does…
-
I used snapshost 2.0-BETA4 (i386) built on Sat Sep 18 22:12:31 EDT 2010
but Load Balancing outbound still error withSep 21 08:45:13 php: : Gateways status could not be determined, considering all as up/active.
and gateway information is
Tier 1
WANGW, Gathering data
OPT1GW, Gathering dataWait for good snapshost
-
Also having this issue.
Currently running:
2.0-BETA4 (i386)
built on Sat Sep 18 23:15:00 EDT 2010 -
Issues here too on the 18th snapshot. Some times it doesnt gather data,other times it gathers but loadbalancing still dont work and failover doesnt seem to be working either. Randomly it balances ok, but failover seems to be never working…
-
In my case, failover is working fine.
Both my GW's are set as Tire1 and when one of them fail (happens at least once a day >:( ) it keep on by sending all traffic on the other interface. -
Any news on this? Just an update would be good. ;)
-
It stopped working but again now seem to work fine.
I am now going to update to Tue Sep 21 23:29:56 EDT 2010 and will see after this. -
@roi:
It stopped working but again now seem to work fine.
I am now going to update to Tue Sep 21 23:29:56 EDT 2010 and will see after this.please keep us updated if Load Balance works on Sep 21 release :)
I reverted back to Aug 27 release. Anything after Aug 27 release seem to be a lot more buggy
-
Logs still fill up with…
Sep 22 23:15:01 php: : Gateways status could not be determined, considering all as up/active.
Sep 22 23:00:00 php: : Gateways status could not be determined, considering all as up/active.Gateway Group Status still displays "gathering data"...
-
Over here it seem to work.
It's not even 7am so as the day will pass there will be more traffic and I will have a better feedback.townsenk - are your interfaces configured using DHCP or static ?
-
one static and one DHCP. Loadbalancing seems to work. Just the group status isn't reported and I gwt my system log filled up with the previous message I posted.
-
Some promising code fixes has just been committed so try the next snapshot or gitsync
-
Go to routing–> Gateways and open a Gateway and click save. This activates apinger and the status will appear correctly. doesn't survive reboot though.. so there's still an issue