[Pacemaker] pacemaker/corosync on CentOS 6.4/6.5 node offline after update

-gateway:1 ]           Any help would be appreciated   thanks in advance   fatcharly     ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org

Re: [Pacemaker] pacemaker/corosync on CentOS 6.4/6.5 node offline after update

Hi Andrew,   so the only solution is to migrate from openais to cman ? Is there a less painful way ?   Kind regards   fatcharly       Gesendet: Donnerstag, 20. Februar 2014 um 23:54 Uhr Von: "Andrew Beekhof" An: "The Pacemaker cluster resource manager" Bet

[Pacemaker] CentOS pacemaker heartbeat

'heartbeat' cluster infrastructure. Terminating. Did I missed something ? I thought heart 3x and pacemaker 1x won´t be a problem ? Any suggestions are welcome. Kind regards fatcharly -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- E

[Pacemaker] ping resource

re="openais" \ expected-quorum-votes="2" \ stonith-enabled="false" \ no-quorum-policy="ignore" rsc_defaults $id="rsc-options" \ resource-stickiness="100" Any Suggestions are welcome kind regards fa

[Pacemaker] problem with pacemaker/corosync on CentOS 6.3

fatcharly ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http

Re: [Pacemaker] problem with pacemaker/corosync on CentOS 6.3

Hi, a part of the logfile of a start of the pacemaker can be found here: http://pastebin.com/qMUzf2Lm Kind regards fatcharly Original-Nachricht > Datum: Fri, 20 Jul 2012 12:08:45 +0200 > Von: fatcha...@gmx.de > An: pacemaker@oss.clusterlabs.org > Betreff

Re: [Pacemaker] problem with pacemaker/corosync on CentOS 6.3

Hi Jake, I erased the files as mentioned und started the services. This is what I get on pilotpound after crm_mon : Last updated: Fri Jul 20 17:45:58 2012 Last change: Current DC: NONE 0 Nodes configured, unknown expected votes 0 Resources configured. Looks like the s

Re: [Pacemaker] problem with pacemaker/corosync on CentOS 6.3

.join_count=5 runtime.totem.pg.mrp.srp.members.425699520.status=joined So I think I´ve got to swollow the bitter pill and restart the whole cluster. I will report about the result. Kind regards fatcharly Original-Nachricht > Datum: Fri, 20 Jul 2012 12:21:47 -0400 (EDT) &g

Re: [Pacemaker] problem with pacemaker/corosync on CentOS 6.3

Hi, I´m glad to report that after a restart of all corosync and pacemaker services the cluster is back on normal operation. A manuel failover is working fine and eveything shifts smoothly. Thanks to everyone for their support ! Kind regards fatcharly Original-Nachricht

[Pacemaker] set the timeout

ion ip2-with-ip3 inf: HA_IP3 HA_IP2 colocation website-with-ip inf: Apache HA_IP order HA_IP2-after-HA_IP inf: HA_IP HA_IP2 order WebSite-after-WebdataFS inf: WebdataFS Apache order WebdataFS-after-Webdata inf: Webdata:promote WebdataFS:start order apache-after-ip inf: HA_IP Apache property $id=&q

[Pacemaker] cluster failover under load

/counter ? Any Suggestions are welcome kind regards fatcharly -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org

[Pacemaker] cloned pingd resource problem

lib/pacemaker/pengine/pe-input-355.bz2): Complete Mar 30 12:32:13 localhost crmd[12986]: notice: State transition S_TRANSITION_ENGINE -> S_IDLE [ input=I_TE_SUCCESS cause=C_FSA_INTERNAL origin=notify_crmd ] What can I do to resolve the problem ? Any suggestions are welcome Kind regards fat