[Linux-HA] heartbeat and squid
Hi all, I've got a question for heartbeat. How can I made this : If squid stop or be killed on node1, how make node2 be master ? Actually, node2 become master only when node1 is down, or heartbeat service on node1 is down, but if I kill squid, nothing happen. I'm using Centos 6 and last heartbeat version. Thanks a lot for your responses ! -- Nicolas ___ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
Re: [Linux-HA] heartbeat and squid
Hi, On Thu, Sep 01, 2011 at 06:30:46PM +0200, Nicolas Repentin wrote: Hi all, I've got a question for heartbeat. How can I made this : If squid stop or be killed on node1, how make node2 be master ? Actually, node2 become master only when node1 is down, or heartbeat service on node1 is down, but if I kill squid, nothing happen. I'm using Centos 6 and last heartbeat version. Using just heartbeat and no pacemaker? Only pacemaker has service monitoring. Thanks, Dejan Thanks a lot for your responses ! -- Nicolas ___ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems ___ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
Re: [Linux-HA] Heartbeat with squid, need help
Nick Duda schrieb: I am new to Heartbeat all over a couple days. Goal: Two Squid cache servers running in failover mode. When the squid process dies on one server, failover to the other. OS: RHEL5 Squid: 2.6Stable18 Heartbeat: 2.1.3 compiled from source Server #1 Name: Squid1 eth0 = IP address on the local LAN, this is the IP that people should use for squid, lets say 10.95.1.1 (this should be the same IP as the failover, yes?) eth1 = interface for heartbeats to the failover. This is using a x-over cable to the eth1 on the other server. 192.168.1.1 /24 Server #2 Name: Squid2 eth0 = IP address on the local LAN, this is the IP that people should use for squid, lets say 10.95.1.1 (this should be the same IP as the failover, yes?) eth1 = interface for heartbeats to the failover. This is using a x-over cable to the eth1 on the other server. 192.168.1.2 /24 Both servers can ping each other over the xover I currently have heartbeat fully running as per Alan's first Installing Heartbeat screencast ha.cf use_logd yes bcast eth1 node squid1 squid2 crm on My haresources is blank for now , until i know how to do what I need. crm_mon says: Last updated: Fri Apr 18 14:50:58 2008 Current DC: squid1 (1691d699-2a81-4545-8242-b00862431514) 2 Nodes configured. 0 Resources configured. Node: squid1 (1691d699-2a81-4545-8242-b00862431514): online Node: squid2 (2422b230-22f2-451b-aa95-0b783eccab8d): online Read: http://www.linux-ha.org/GettingStartedV2 and http://www.linux-ha.org/GettingStartedV2/Apache Michael. ___ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
