Re: [Pacemaker] pcs equivalent of crm configure erase
On 19/04/2013, at 7:37 PM, T. wrote: > Hi Chris, > >> No, you're definitely not missing anything. The 'pcs cluster cib' >> output isn't pretty. > why there is an approach to build a new config-tool at all? > > Why not use the crmsh? Why it was dropped in the RHEL-build? Because the author wanted it removed from Pacemaker, at which point someone would have needed to navigate the red tape to get it back into the distribution. This is something anyone can do for Fedora, but despite a lot of hollering, it appears no-one has had sufficient motivation. > Does it have some relevant disadvantages? Yes, see the original announcement thread. > -- > To Answer please replace "invalid" with "de" ! > Zum Antworten bitte "invalid" durch "de" ersetzen ! > > > Chau y hasta luego, > > Thorolf > > > ___ > 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://bugs.clusterlabs.org ___ 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://bugs.clusterlabs.org
Re: [Pacemaker] pcs equivalent of crm configure erase
On 19/04/2013, at 8:18 PM, emmanuel segura wrote: > I don't know why redhat doesn't give to the users the alternatives to use > what they want Because they'd have to support both options which means double the engineering + QE effort. More actually because people would end up using both and there would surely be subtle interaction issues. > > sorry for my ugly english :-) > > Thanks > > > 2013/4/19 T. > Hi Chris, > > > No, you're definitely not missing anything. The 'pcs cluster cib' > > output isn't pretty. > why there is an approach to build a new config-tool at all? > > Why not use the crmsh? Why it was dropped in the RHEL-build? > Does it have some relevant disadvantages? > -- > To Answer please replace "invalid" with "de" ! > Zum Antworten bitte "invalid" durch "de" ersetzen ! > > > Chau y hasta luego, > > Thorolf > > > ___ > 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://bugs.clusterlabs.org > > > > -- > esta es mi vida e me la vivo hasta que dios quiera > ___ > 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://bugs.clusterlabs.org ___ 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://bugs.clusterlabs.org
Re: [Pacemaker] Pacemaker 1.1.8, Corosync, No CMAN, Promotion issues
> > Another user hit the same issue and was able to reproduce. > You can see the resolution at > https://bugzilla.redhat.com/show_bug.cgi?id=951340 > > Thanks much for letting me know. I will watch the "Fixed in version" field and upgrade as necessary. Pavan ___ 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://bugs.clusterlabs.org
Re: [Pacemaker] Pacemaker 1.1.8, Corosync, No CMAN, Promotion issues
Hi Andrew, is the bug fix in 1.1.9 for RHEL6.4? Have you an idea when 1.1.20 will be released? Best regards Andreas Mock -Ursprüngliche Nachricht- Von: Andrew Beekhof [mailto:and...@beekhof.net] Gesendet: Samstag, 20. April 2013 12:04 An: The Pacemaker cluster resource manager Betreff: Re: [Pacemaker] Pacemaker 1.1.8, Corosync, No CMAN, Promotion issues On 19/04/2013, at 11:28 AM, pavan tc wrote: > Yes, but looking at the code it should be impossible. > Would it be possible for you to add: > > export PCMK_trace_functions=peer_update_callback > > to /etc/sysconfig/pacemaker and re-test (and send me the new logs - probably in /var/log/pacemaker.log)? > > > Sorry about the delay. > > I have put these in place and am running tests now. The next time I hit this, I'll post the messages. Another user hit the same issue and was able to reproduce. You can see the resolution at https://bugzilla.redhat.com/show_bug.cgi?id=951340 ___ 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://bugs.clusterlabs.org ___ 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://bugs.clusterlabs.org
[Pacemaker] Failed actions message
Hi, I have a fully functional 2 node cluster of Asterisk servers. When one of the servers fail the message below shows up in crm_mon and stays there even if I fix the problem. I know that the message is supposed to show up. Is there a way to remove it after both nodes are up and running? Thank you. Failed actions: p_asterisk_monitor_1 (node=node1.localdomain, call=11, rc=7, status=comp lete): not running ___ 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://bugs.clusterlabs.org
Re: [Pacemaker] Pacemaker 1.1.8, Corosync, No CMAN, Promotion issues
On 19/04/2013, at 11:28 AM, pavan tc wrote: > Yes, but looking at the code it should be impossible. > Would it be possible for you to add: > > export PCMK_trace_functions=peer_update_callback > > to /etc/sysconfig/pacemaker and re-test (and send me the new logs - probably > in /var/log/pacemaker.log)? > > > Sorry about the delay. > > I have put these in place and am running tests now. The next time I hit this, > I'll post the messages. Another user hit the same issue and was able to reproduce. You can see the resolution at https://bugzilla.redhat.com/show_bug.cgi?id=951340 ___ 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://bugs.clusterlabs.org
