Load Balancer Status issue
-
I'm setting 2 pfSense servers (1.2.2) up for a Dual-WAN Load Balancer with CARP/Failover ability. Currently only using one DSL line currently, so there are fake IP addresses for the OPT1 (VLAN 1/WAN2) Interface.
Followed the guide and setup all of my pools and such. The problem is when I go to check the status of the LB Pools. They all say that they are offline for both WAN and WAN2 (It should only say offline for WAN2). Both pfSense units can ping the monitor IP's that I have chosen for each pool (first ISP hop after gateway) via WAN. I checked the logs and slbd seems to notice that everything is up. Something weird however is that each time slbd pings, it always crashes with the error below:
kernel: pid 32054 (slbd), uid 0: exited on signal 11 (core dumped)
I don't know if that is related to why my WAN connection (in Bridge mode to pfSense) isn't working, but I am just wondering if this is something wrong with my configuration or the pfSense install, or possibly my hardware (2 Dell PowerEdge 1850's)
UPDATE 1: Rebuilding my pools from scratch, I have determined that the error above happens when I try to add a failover pool. I saw something once that said that it might be because I'm using a VLAN for the WAN2 interface (both DSL modems are going to a switch where my WAN interface is connected to). I know that it's an end-run around using many NIC's, but is the fact that the Optional Interfaces are VLAN-based an issue in this case?
UPDATE 2: Tried upgrading to pfSense 1.2.3 RC1 to see if the problem is resolved. No go, error above and issue with Load-Balancer pools status remains.
-
I want to report the same problem with a much simpler configuration. I has a single PfSense box with 2 WAN links (WAN and OPT1), 1 single pool with the two links in gateway/failover mode. When one link goes down, BOTH are reported down with a (slbd), uid 0: exited on signal 11 (core dumped) error.
If there is a way to report more information, please ask me.
-
Try to use a different monitor ip !! Like www.google.com instead.
-
I did, the result is unfortunately exactly the same. I will now try with a new vanilla PfSense box to see if I can reproduce the core dump error.
-
Have you got this working? Me too I'm having problems with failover when I try to disconnect one of my three WAN connections. I don't use VLANs and all three modemsa are connected directly to the pfsense box.