OPS support
Emmanuel Seyman <[email protected]>
| Newsgroups | gmane.linux.keepalived.devel |
|---|---|
| Message-ID | <20150122103023.GA2103@orient> |
Hello, people. I'm setting up a syslog cluster using keepalived to make several servers redundant and I'm having issues with keepalived's support of ops. I'm using keepalived 1.2.13 on Debian wheezy servers. When I add the term 'ops' to the /etc/keepalived/keepalived.conf and start keepalived with 'keepalived -d', I see the following in syslog: Jan 22 11:02:38 d-manu-ipvsadm Keepalived_healthcheckers[16521]: ------< LVS Topology >------ Jan 22 11:02:38 d-manu-ipvsadm Keepalived_healthcheckers[16521]: System is compiled with LVS v1.2.1 Jan 22 11:02:38 d-manu-ipvsadm Keepalived_healthcheckers[16521]: VIP = 192.168.0.56, VPORT = 514 Jan 22 11:02:38 d-manu-ipvsadm Keepalived_healthcheckers[16521]: delay_loop = 6, lb_algo = rr Jan 22 11:02:38 d-manu-ipvsadm Keepalived_healthcheckers[16521]: protocol = UDP Jan 22 11:02:38 d-manu-ipvsadm Keepalived_healthcheckers[16521]: alpha is OFF, omega is OFF Jan 22 11:02:38 d-manu-ipvsadm Keepalived_healthcheckers[16521]: quorum = 1, hysteresis = 0 Jan 22 11:02:38 d-manu-ipvsadm Keepalived_healthcheckers[16521]: lb_kind = NAT Jan 22 11:02:38 d-manu-ipvsadm Keepalived_healthcheckers[16521]: RIP = 192.168.0.47, RPORT = 514, WEIGHT = 1 Jan 22 11:02:38 d-manu-ipvsadm Keepalived_healthcheckers[16521]: RIP = 192.168.0.35, RPORT = 514, WEIGHT = 1 Jan 22 11:02:38 d-manu-ipvsadm Keepalived_healthcheckers[16521]: Using LinkWatch kernel netlink reflector... No mention of ops and 'ipvsadm -S -n' shows that the server does not have ops enabled. Declaring the service via ipvsadm commands activates ops and from that point on, the syslog messages are spread out amongst the realservers. I'm probably doing something wrong but I can't see what. Can anybody help? Emmanuel ------------------------------------------------------------------------------ New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet