<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt"><div style="RIGHT: auto"><SPAN style="RIGHT: auto">Thank you for your prompt reply. I actually wanted to create an active/passive cluster, so if either the network or Asterisk fails these services could be migrated to the other server. As I already stated earlier, the current config notifies me if asterisk is down but does not start asterisk on the other server.<VAR id=yui-ie-cursor></VAR></SPAN></div>
<DIV style="FONT-FAMILY: times new roman, new york, times, serif; FONT-SIZE: 12pt">
<DIV style="FONT-FAMILY: times new roman, new york, times, serif; FONT-SIZE: 12pt">
<DIV style="RIGHT: auto" dir=ltr><FONT size=2 face=Arial>----- Forwarded Message -----<BR><B><SPAN style="FONT-WEIGHT: bold">From:</SPAN></B> Jake Smith <jsmith@argotec.com><BR><B><SPAN style="FONT-WEIGHT: bold">To:</SPAN></B> Tommy Cooper <tomcooper83@yahoo.com>; The Pacemaker cluster resource manager <pacemaker@oss.clusterlabs.org> <BR><B><SPAN style="FONT-WEIGHT: bold">Sent:</SPAN></B> Monday, March 4, 2013 9:29 PM<BR><B><SPAN style="FONT-WEIGHT: bold">Subject:</SPAN></B> Re: [Pacemaker] Cluster resources failing to move<BR></FONT></DIV><BR><BR>----- Original Message -----<BR>> From: "Tommy Cooper" <<A href="mailto:tomcooper83@yahoo.com" ymailto="mailto:tomcooper83@yahoo.com">tomcooper83@yahoo.com</A>><BR>> To: <A style="RIGHT: auto" href="mailto:pacemaker@oss.clusterlabs.org" ymailto="mailto:pacemaker@oss.clusterlabs.org">pacemaker@oss.clusterlabs.org</A><BR>> Sent: Monday, March 4, 2013 2:19:22 PM<BR>> Subject:
[Pacemaker] Cluster resources failing to move<BR>> <BR>> <BR>> <BR>> <BR>> Hi,<BR>> <BR>> <BR>> I am trying to configure a 2 node cluster using pac emaker 1.1.7 and<BR>> corosync 1.4.1. I. I want pacemaker to provide the virual IP<BR>> (192.168.1.115), monitor Asterisk (PBX) and failover to the othe<BR>> server. If I switch off pacemaker and/or corosync the cluster<BR>> resources switch to the other node. I have also configured<BR>> <A href="http://res_corosync.so/" target=_blank>res_corosync.so</A> module in Asterisk However if i either switch off<BR>> asterisk using service *service name* stop, the following error is<BR>> shown: Failed actions:<BR>> p_asterisk_monitor_10000 (node=node1.localdomain, call=10, rc=7,<BR>> status=complete): not running<BR>> <BR><BR>What do you want/expect to happen when you stop asterisk that doesn't? The monitor showing not running (failed) is expected if
some outside event stopped the resource.<BR><BR>> Corosync configuration:<BR>> <BR>> compatibility: whitetank<BR>> totem {<BR>> version: 2<BR>> secauth: off<BR>> interface {<BR>> member {<BR>> memberaddr: 192.168.1.113<BR>> }<BR>> member {<BR>> memberaddr: 192.168.1.114<BR>> }<BR>> ringnumber: 0<BR>> bindnetaddr: 192.168.1.0<BR>> mcastport: 5405<BR>> ttl: 1<BR>> }<BR>> transport: udpu<BR>> }<BR>> logging {<BR>> fileline: off<BR>> to_logfile: yes<BR>> to_syslog: yes<BR>> debug: on<BR>> logfile: /var/log/cluster/corosync.log<BR>> debug: off<BR>> timestamp: on<BR>> logger_subsys {<BR>> subsys: AMF<BR>> debug: off<BR>> }<BR>> }<BR>> <BR>> amf {<BR>> mode: disabled<BR>> }<BR>> quorum {<BR>> provider: corosync_votequorum<BR>> expected_votes: 3<BR>> }<BR>> <BR>> crm configure status:<BR>> <BR>> node node1.localdomain<BR>>
node node2.localdomain<BR>> primitive failover-ip ocf:heartbeat:IPaddr2 \<BR>> params ip="192.168.1.115" cidr_netmask="24" nic="eth6" \<BR>> op start interval="0" timeout="30" \<BR>> op monitor interval="1s" timeout="30" start-delay="0" \<BR>> op stop interval="0" timeout="30s" \<BR>> meta target-role="started"<BR>> primitive p_asterisk ocf:heartbeat:asterisk \<BR>> params user="root" group="root" maxfiles="65536" \<BR>> op start interval="0" timeout="30s" \<BR>> op monitor interval="10s" timeout="30s" \<BR>> op stop interval="0" timeout="30s"<BR>> group voip failover-ip p_asterisk<BR><BR>You don't need these colocation and order statements if you have the resources grouped - remove them. The group is a syntax shortcut for writing order and colocation statements so the above is enforcing an order of ip then asterisk and a colocation of asterisk with ip. Also the colocation below is backwards and *might* be
causing your issues.<BR><BR>HTH<BR>Jake<BR><BR>> colocation asterisk_cluster inf: failover-ip p_asterisk<BR>> order start_order inf: failover-ip p_asterisk<BR>> property $id="cib-bootstrap-options" \<BR>> dc-version="1.1.7-6.el6-148fccfd5985c5590cc601123c6c16e966b85d14" \<BR>> cluster-infrastructure="openais" \<BR>> expected-quorum-votes="2" \<BR>> stonith-enabled="false" \<BR>> no-quorum-policy="ignore"<BR>> rsc_defaults $id="rsc-options" \<BR>> resource-stickiness="100"<BR>> <BR>> <BR>> <BR>> <BR>> <BR>> _______________________________________________<BR>> Pacemaker mailing list: <A href="mailto:Pacemaker@oss.clusterlabs.org" ymailto="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</A><BR>> http://oss.clusterlabs.org/mailman/listinfo/pacemaker<BR>> <BR>> Project Home: http://www.clusterlabs.org<BR>> Getting started:<BR>>
http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf<BR>> Bugs: http://bugs.clusterlabs.org<BR>> <BR><BR><BR></DIV></DIV></div></body></html>