Bug 21221
Summary: | secondary load balancer doesn't lose vips after pulse is stopped | ||
---|---|---|---|
Product: | [Retired] Red Hat High Availability Server | Reporter: | Dan Reed <dreed> |
Component: | piranha | Assignee: | Phil Copeland <copeland> |
Status: | CLOSED RAWHIDE | QA Contact: | Phil Copeland <copeland> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | beta | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2001-07-31 18:38:30 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Red Hat Bugzilla
2000-11-22 03:25:35 UTC
There are circumstances where this can happen and not be a bug. The active system should always be the last one that performed arp broadcasts so arp tables should reflect the correct system. In order to analyze this further, we would need a copy of your config file. service = lvs primary = 63.236.a.x backup = 63.236.a.y backup_active = 1 heartbeat = 1 heartbeat_port = 1050 keepalive = 3 deadtime = 9 rsh_command = rsh network = nat nat_router = 192.168.100.5 eth1:0 virtual web_server { scheduler = wlc persistent = 0 pmask = 255.255.255.255 address = 63.236.a.z eth0:0 active = 1 port = 80 load_monitor = ruptime timeout = 5 reentry = 10 protocol = tcp server web_ftp_1 { address = 192.168.100.10 active = 1 weight = 100 } server web_ftp_2 { address = 192.168.100.11 active = 1 weight = 100 } server web_only { address = 192.168.100.12 active = 1 weight = 30 } } virtual https_server { scheduler = wlc persistent = 0 pmask = 255.255.255.255 address = 63.236.a.z eth0:0 active = 1 port = 443 load_monitor = ruptime timeout = 5 reentry = 10 protocol = tcp server web_ftp_1 { address = 192.168.100.10 active = 1 weight = 40 } server web_ftp_2 { address = 192.168.100.11 active = 1 weight = 40 } server web_ftp_3 { address = 192.168.100.12 active = 1 weight = 100 } } Hope this helps, let me know if you need any more info... Note: this is the same person as dreed How was pluse shutdown on the secondary server? The correct and automated way to do this is to always start pulse on the primary server with the force active option. This option will automatically kill the secondary server when the primary takes control. Fixed in upcoming release (piranha-0.6.x) |