Re: [Pacemaker] How to set up logging for CTSlab

> > On Mon, Jan 10, 2011 at 5:40 PM, Dejan Muhamedagic > wrote: > > Hi, > > > > On Mon, Jan 10, 2011 at 10:46:58AM +0100, Simon Jansen wrote: > >> Hi, > >> > >> I would like to test my cluster with the cluster test suite. I followed > the &

[Pacemaker] How to set up logging for CTSlab

09:01 Restarting logging on: ['192.168.200.10', '192.168.200.20'] Jan 10 10:11:37 Restarting logging on: ['192.168.200.10', '192.168.200.20'] Jan 10 10:15:02 Restarting logging on: ['192.168.200.10', '192.168.200.20'] Jan 10 10:19:02 ERROR

Re: [Pacemaker] Multistate resources ignore constraints

I solved the problem by changing the constraints to colocation colIPNTP inf: msNTP:Master resIP order orderIPNTP inf: resIP msNTP -- Regards Simon Jansen --- Simon Jansen 64291 Darmstadt ___ Pacemaker mailing list

[Pacemaker] Both nodes restart with external/ssh STONITH agent

node1 node2" I tried to clone the resource but without success. The system acts in the same way. Is this the normal behaviour of the ssh agent or did I misconfigured the agent? -- Regards, Simon Jansen ------- Simon Jansen 64291

[Pacemaker] Multistate resources ignore constraints

Hi Florian, It would help if you shared your ntp resource agent so we can understand > how it updates its master preference. > > See also: > http://www.linux-ha.org/doc/dev-guides/_specifying_a_master_preference.html > ok, it is attached. -- Regard

[Pacemaker] Multistate resources ignore constraints

resNTP The problem is that the multistate resource msNTP tries to promote anyways even if the resources resIP and resFSys are not running on a cluster node. So the constraints do not take effect at all. Is there a solution to control the promotion of multistate resou

Re: [Pacemaker] pingd location constraints

1 location locIP0PingErr resIP0 \ rule $id="locIP0PingErr-rule" -inf: not_defined pingd or pingd number:lte 1000 location locIP1Node2 resIP1 \ rule $id="locIP1Node2-rule" inf: #uname eq node2 location locIP1PingErr resIP1 \ rule $id="locIP

Re: [Pacemaker] pingd location constraints

again. -- Regards, Simon Jansen --- Simon Jansen 64291 Darmstadt ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting

Re: [Pacemaker] pingd location constraints

rrives the destination. -- Regards, Simon Jansen ------- Simon Jansen 64291 Darmstadt ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clust

[Pacemaker] pingd location constraints

le=Master -inf: not_defined pingd or pingd lte 1 But with this constraint the cluster does not go into normal operation again. Maybe someone has implemented an assimilable configuration. Thanks for any answers. -- Regards, Simon Jansen --- Simon

Re: [Pacemaker] crmd exits and restarts after failback

Hi Andrew, thank you for your answer. I meanwhile deleted the configuration and set it up again. Now the error does not occur any more. -- Regards, Simon Jansen --- Simon Jansen 64291 Darmstadt ___ Pacemaker mailing list

Re: [Pacemaker] crmd exits and restarts after failback

. -- Regards, Simon Jansen --- Simon Jansen 64291 Darmstadt ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting

[Pacemaker] crmd exits and restarts after failback

. -- Regards, Simon Jansen --- Simon Jansen 64291 Darmstadt ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting

[Pacemaker] crmd exits and restarts after failback

0 colocation colIP0Syslog inf: msSyslog:Master resIP0 colocation colIP0VPN inf: groupIPVPN resIP0 colocation colIP1Sendmail inf: resSendmail resIP1 colocation colIP1Squid inf: resSquid resIP1 colocation colIP1VMPS inf: resVMPS resIP1 colocation colVPNSyslog 1000: msSyslog:Master groupIPVPN order orderDR

Re: [Pacemaker] Multistate Resources is not promoted automatically

define a custom namespace? -- Regards, Simon Jansen ------- Simon Jansen 64291 Darmstadt ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clust

[Pacemaker] Multistate Resources is not promoted automatically

nf" \ op monitor interval="10" role="Master" timeout="30" start-delay="1" \ op monitor interval="12" timeout="31" \ op start interval="0" timeout="120" \ op stop interval="0

Re: [Pacemaker] HA DHCP3 server on Ubuntu

e inspiration. I tried dhcping. But as you mentioned, it doesn't work on the localhost. So maybe I can use nmap to check if the port is open and the dhcpd service is listening... Thanks for the input. Perhaps I will try to write a RA for the dhcpd service using nmap to check the status. Regards,

Re: [Pacemaker] HA DHCP3 server on Ubuntu

. It's a very good help in many situations. ;) @Christian: Thanks for the advice. I've seen the builtin failover mechanism before but with Pacemaker I have a central management interface. So it's easier to manage. Further we don't want to spli

[Pacemaker] HA DHCP3 server on Ubuntu

#x27;. Maybe somone has a clue to fix this problem. In addition I would like to know if it is recommended to use the anything RA or should I change the paths in the init script and use the lsb RA? Regards, Simon -- Simon Jansen 64293 Darmstadt ___