Re: [Pacemaker] Error when managing network with ping/pingd.

2013-09-19 Thread Francis SOUYRI
Hi Andreas, You are right and I am blind, the fail-over work now when the network failed, thank you very much !! I just have to set now the "best" parameters for the ping monitor. With your help I just finish to migrate with the same "services" our test cluster from hearbeat(crm 1)/drbd (v

Re: [Pacemaker] Error when managing network with ping/pingd.

2013-09-18 Thread Andreas Kurz
On 2013-09-18 16:26, Francis SOUYRI wrote: > Hello, > > I take an example from Internet without monitor... Do you have a > suggestion ? There are a lot of examples ... like this one http://goo.gl/ZfKZeq Regards, Andreas -- Need help with Pacemaker? http://www.hastexo.com/now > > Best reg

Re: [Pacemaker] Error when managing network with ping/pingd.

2013-09-18 Thread Andreas Kurz
On 2013-09-18 16:56, Francis SOUYRI wrote: > Hello, > > I updated ping-gateway like this but nothing change... Hmm ... well, there is still no monitor operation you only added some more attributes. Try: crm configure monitor ping-gateway 20 ... or the equivalent in your preferred cluster manag

Re: [Pacemaker] Error when managing network with ping/pingd.

2013-09-18 Thread Francis SOUYRI
Hello, I updated ping-gateway like this but nothing change... type="ping"> name="host_list" value="192.168.1.1"/> name="multiplier" value="1000"/> name="depth" value="0"/> name="timeout" value="20s"/> name="interval

Re: [Pacemaker] Error when managing network with ping/pingd.

2013-09-18 Thread Francis SOUYRI
Hello, I take an example from Internet without monitor... Do you have a suggestion ? Best regards. Francis On 09/18/2013 03:54 PM, Andreas Kurz wrote: On 2013-09-18 15:44, Francis SOUYRI wrote: Hello Andreas, I do not see what is wrong in my config. You have no "monitor" operation defin

Re: [Pacemaker] Error when managing network with ping/pingd.

2013-09-18 Thread Andreas Kurz
On 2013-09-18 15:44, Francis SOUYRI wrote: > Hello Andreas, > > I do not see what is wrong in my config. You have no "monitor" operation defined for your "ping-gateway" resource, so in fact it does never execute the connectivity check but only updates the "pingd" attriute value once on start. Re

Re: [Pacemaker] Error when managing network with ping/pingd.

2013-09-18 Thread Francis SOUYRI
Hello Andreas, I do not see what is wrong in my config. validate-with="pacemaker-1.2" crm_feature_set="3.0.6" update-origin="noeud2.apec.fr" update-client="cibadmin" cib-last-written="Sat Sep 14 10:53:58 2013" have-quorum="1" dc-uuid="2"> value="1.1.7-2.fc17-ee0730e13d1

Re: [Pacemaker] Error when managing network with ping/pingd.

2013-09-18 Thread Andreas Kurz
On 2013-09-17 16:25, Francis SOUYRI wrote: > Hello, > > Thank for your reply Andreas, I set the multiplier to 1000, cut the > netword nothing append. Well, the ping resource-agent updates the value on every monitor event looking again on your configuration, guess what operation is missing? ;

Re: [Pacemaker] Error when managing network with ping/pingd.

2013-09-17 Thread Francis SOUYRI
Hello, Thank for your reply Andreas, I set the multiplier to 1000, cut the netword nothing append. I have these score: Resource Score Node Stickiness #Fail IPaddr2_dhcpd 1000 noeud2.apec.fr 1000 IPaddr2_dhcpd 1350 noeud1.apec.fr 1000

Re: [Pacemaker] Error when managing network with ping/pingd.

2013-09-17 Thread Andreas Kurz
On 2013-09-17 09:45, Francis SOUYRI wrote: > Hello, > > Some help about my problem ? > > I have a corosync/pacemaker with 2 nodes and 2 nets by nodes, > 192.168.1.0/24 for cluster access, 10.1.1.0/24 for drbd in bond, both > used by corosync. > I try to used ocf:pacemaker:ping to monitor the 192.

Re: [Pacemaker] Error when managing network with ping/pingd.

2013-09-17 Thread Francis SOUYRI
Hello, Some help about my problem ? I have a corosync/pacemaker with 2 nodes and 2 nets by nodes, 192.168.1.0/24 for cluster access, 10.1.1.0/24 for drbd in bond, both used by corosync. I try to used ocf:pacemaker:ping to monitor the 192.168.1.0/24 I have the configuration below, but when I r

Re: [Pacemaker] Error when managing network with ping/pingd.

2013-09-04 Thread Francis SOUYRI
Hello Andrew, I removed it :( below the complete cib.xml. validate-with="pacemaker-1.2" crm_feature_set="3.0.6" update-origin="noeud2.apec.fr" update-client="cibadmin" cib-last-written="Wed Sep 4 09:30:26 2013" have-quorum="1" dc-uuid="2"> value="1.1.7-2.fc17-ee0730e13

Re: [Pacemaker] Error when managing network with ping/pingd.

2013-09-03 Thread Andrew Beekhof
Where did the status section go? On 02/09/2013, at 5:46 PM, Francis SOUYRI wrote: > Hello Andrew, > > Now I understand, below the complete configuration. > > validate-with="pacemaker-1.2" crm_feature_set="3.0.6" > update-origin="noeud2.apec.fr" update-client="cibadmin" cib-last-written

Re: [Pacemaker] Error when managing network with ping/pingd.

2013-09-02 Thread Francis SOUYRI
Hello Andrew, Now I understand, below the complete configuration. validate-with="pacemaker-1.2" crm_feature_set="3.0.6" update-origin="noeud2.apec.fr" update-client="cibadmin" cib-last-written="Mon Sep 2 09:23:58 2013" have-quorum="1" dc-uuid="2"> value="1.1.7-

Re: [Pacemaker] Error when managing network with ping/pingd.

2013-09-01 Thread Andrew Beekhof
On 30/08/2013, at 5:32 PM, Francis SOUYRI wrote: > Hello Andrew, > > Sorry I do not understand your comment after "Please don't do this.", What I > need to do ? Cut off relevant parts of the config and replace them with "". > > For my test system I have a cluster with 2 nodes and 4 res

Re: [Pacemaker] Error when managing network with ping/pingd.

2013-08-30 Thread Francis SOUYRI
Hello Andrew, Sorry I do not understand your comment after "Please don't do this.", What I need to do ? For my test system I have a cluster with 2 nodes and 4 resources group (named, dhcpd, named2, samba) with each group an ip resource, drbd resource, filesystem resource, start application r

Re: [Pacemaker] Error when managing network with ping/pingd.

2013-08-29 Thread Andrew Beekhof
On 29/08/2013, at 5:36 PM, Francis SOUYRI wrote: > Hello, > > I have a corosync/pacemaker with 2 nodes and 2 nets by nodes, 192.168.1.0/24 > for cluster access, 10.1.1.0/24 for drbd in bond, both used by corosync. > I try to used ocf:pacemaker:ping to monitor the 192.168.1.0/24 I have the > c

Re: [Pacemaker] Error when managing network with ping/pingd.

2013-08-29 Thread Francis SOUYRI
Hello, Below the result of the scoreshow script (https://github.com/ClusterLabs/pacemaker/blob/master/extra/showscores.sh) and in attachment the output of "pcs config" drbd ocf:redhat:drbd.sh Filesystem: ocf:heartbeat:Filesystem IPaddr2: ocf:heartbeat:Ipaddr2 ping: ocf:pacemaker:ping # ./sco

Re: [Pacemaker] Error when managing network with ping/pingd.

2013-08-29 Thread emmanuel segura
Read this link http://www.woodwose.net/thatremindsme/2011/04/the-pacemaker-ping-resource-agent/ 2013/8/29 Francis SOUYRI > Hello Emmanuel, > > Yes I think also but why... that the question, I checked the Net for > information about how the score is calculated without success. > > I retrieved a

Re: [Pacemaker] Error when managing network with ping/pingd.

2013-08-29 Thread Francis SOUYRI
Hello Emmanuel, Yes I think also but why... that the question, I checked the Net for information about how the score is calculated without success. I retrieved a "schoreshow" script but I do not understand the result. Best regards. Francis On 08/29/2013 10:32 AM, emmanuel segura wrote: I t

Re: [Pacemaker] Error when managing network with ping/pingd.

2013-08-29 Thread emmanuel segura
I think your score is wrong in your rule expression 2013/8/29 Francis SOUYRI > Hello, > > I have a corosync/pacemaker with 2 nodes and 2 nets by nodes, > 192.168.1.0/24 for cluster access, 10.1.1.0/24 for drbd in bond, both > used by corosync. > I try to used ocf:pacemaker:ping to monitor the 1

[Pacemaker] Error when managing network with ping/pingd.

2013-08-29 Thread Francis SOUYRI
Hello, I have a corosync/pacemaker with 2 nodes and 2 nets by nodes, 192.168.1.0/24 for cluster access, 10.1.1.0/24 for drbd in bond, both used by corosync. I try to used ocf:pacemaker:ping to monitor the 192.168.1.0/24 I have the configuration below, but when I remove the cable of the noeud1