So now that this is behind me, everything appears great for my load balancing setup.
Thanks for the help Bill...
-Josh
Bill thanks for the help and
On 4/18/06, Bill Marquette <[EMAIL PROTECTED]> wrote:
The slbd errors can be safely ignored for WAN load balancing - I've
replied that elsewhere (forum I believe) and will be cleaning up those
info messages for RC1. I'll need a copy of your /tmp/rules.debug,
/var/etc/slbd.conf, and /conf/config.xml and a netstat -rn output
would be useful to determine your routing table.
Thanks
--Bill
On 4/18/06, Josh <[EMAIL PROTECTED]> wrote:
>
> It appears that upgrading to beta3 has killed my load balancing. I originally had the monitor IPs the same for both gateways but have since corrected that. I am using the gateway on both interfaces as the monitor IP. With the failed load balancing I have also started to notice a failed message appearing in my logs.
>
> This is from my Load Balance Log section
>
> Apr 18 11:12:28 slbd[2134]: Service changed status, reloading filter policy
> Apr 18 11:12:28 slbd[2134]: Switching to sitedown for VIP 127.0.0.1:666
> Apr 18 11:12:28 slbd[2134]: TCP poll failed to start to 68.x.x.x:666 in default (Operation now in progress) (IP= WAN Gateway)
>
> Apr 18 11:12:28 slbd[2134]: TCP poll failed to start to 66.x.x.xx:666 in default (Operation now in progress) (IP=OPT1 Gateway)
>
> Apr 18 11:12:28 slbd[2134]: VIP 127.0.0.1:666 added real service 68.x.x.x:666 (IP= WAN Gateway)
> Apr 18 11:12:28 slbd[2134]: VIP 127.0.0.1:666 added real service 66.x.x.x:666 (IP=OPT1 Gateway)
> Apr 18 11:12:28 slbd[2134]: VIP 127.0.0.1:666 sitedown at 127.0.0.1:666
> Apr 18 11:12:28 slbd[2134]: VIP 127.0.0.1:666 configured as "127.0.0.1"
> Apr 18 11:12:28 slbd[2134]: Using configuration file /var/etc/slbd.conf
> Apr 18 11:12:28 slbd[2134]: Using r_refresh of 5000 milliseconds
>
>
> This is the log under system
>
>
> Apr 18 11:12:39 php: : There were error(s) loading the rules: /tmp/rules.debug:220: syntax error pfctl: Syntax error in config file: pf rules not loaded - The line in question reads [220]: label "USER_RULE"
> Apr 18 11:12:33 php: : FTP proxy disabled for interface opt1 - ignoring.
> Apr 18 11:12:28 slbd[2134]: Service changed status, reloading filter policy
> Apr 18 11:12:28 slbd[2134]: Switching to sitedown for VIP 127.0.0.1:666
> Apr 18 11:12:28 slbd[2134]: TCP poll failed to start to 68.x.x.x:666 in default (Operation now in progress) (IP= WAN Gateway)
> Apr 18 11:12:28 slbd[2134]: TCP poll failed to start to 66.x.x.x:666 in default (Operation now in progress) (IP=OPT1 Gateway)
>
>
>
> Most of the above log entry's I pasted are 'new' as in I didn't see these errors until after 2 reboots & recreating the load balanced rule from scratch with the gateways as the monitor IPs. Before I recreated the load balance rule and load balanced the only noticible error was.
> : There were error(s) loading the rules: /tmp/rules.debug:220: syntax error pfctl: Syntax error in config file: pf rules not loaded - The line in question reads [220]: label "USER_RULE
>
>
> Let me know of any suggestions you may have or if you need additional information from me.
> Wan interface = DHCP (with static gateway)
> Opt1 interface = static
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
