On Sun, Jun 22, 2014 at 1:51 AM, Digimer wrote:
> Excellent.
>
> Please note; With IPMI-only fencing, you may find that killing all power
> to the node will cause fencing to fail, as the IPMI's BMC will lose power
> as well (unless it has it's own battery, but most don't).
>
> If you find thi
Hello,
On 25 June 2014 18:45, Riccardo Murri wrote:
> We would like to co-locate STONITH with a functional ethernet
> interface on the IPMI network (`eth0.617`). So we have the following
> rules::
> [...]
> However, STONITH resources appear as "Stopped", and `crm_simulate`
> says they cannot be
On 25/06/14 12:45 PM, Riccardo Murri wrote:
Hello,
we are using IPMI to fence off nodes in the cluster (yes, we know it's
a bad idea but we do not yet have proper STONITH HW so we have to
sitck with it).
IPMI is just fine as a fence method. It's probably the most commonly
used one, actually.
Hello,
we are using IPMI to fence off nodes in the cluster (yes, we know it's
a bad idea but we do not yet have proper STONITH HW so we have to
sitck with it).
We would like to co-locate STONITH with a functional ethernet
interface on the IPMI network (`eth0.617`). So we have the following
rules
I think your Terracotta script needs to be installed on every node,
because pacemaker look if the resource is running in more then one
node, anyway you the script should be present in all nodes
2014-06-25 17:17 GMT+02:00 Digimer :
> The reason I mentioned it now is that, many times, strange proble
The reason I mentioned it now is that, many times, strange problems go
away once stonith is working. I always recommend the build order of
'configure nodes -> configure/test stonith -> everything else'. It helps
a lot in separating infrastructure issues from configuration issues.
As for the pa
This would be a great document to share in general. Would you be willing
to post those steps as a new thread on this mailing list? I am sure it
would help others, too.
On 25/06/14 02:59 AM, Kostiantyn Ponomarenko wrote:
Hi Vijay B,
I have 2 Debian machines with the latest Corosync and Pacemak
Hi,
On Wed, Jun 25, 2014 at 10:21:34AM +0200, Bart Coninckx wrote:
> Hi all,
>
> Aside of the thorough and comprehensive documentation, I was wondering if
> anyone would be willing to create a "Troubleshooting" document, containing a
> methodology to track down and correct errors. I feel like t
On 25 Jun 2014, at 14:41, Andrew Beekhof wrote:
>
> On 25 Jun 2014, at 6:21 pm, Bart Coninckx wrote:
>
>> Hi all,
>>
>> Aside of the thorough and comprehensive documentation, I was wondering if
>> anyone would be willing to create a "Troubleshooting" document, containing a
>> methodology t
On 25 Jun 2014, at 6:21 pm, Bart Coninckx wrote:
> Hi all,
>
> Aside of the thorough and comprehensive documentation, I was wondering if
> anyone would be willing to create a "Troubleshooting" document, containing a
> methodology to track down and correct errors. I feel like this is missing a
On 23.06.2014 01:14, Andrew Beekhof wrote:
>
> On 23 Jun 2014, at 8:35 am, Dennis Jacobfeuerborn
> wrote:
>
>> Hi,
>> what is the best way to list the resources running on the local node?
>> I'm trying to create a simple monitoring script and basically want to be
>> able to simply list all the
On 25.06.2014 10:21, Bart Coninckx wrote:
Hi all,
Aside of the thorough and comprehensive documentation, I was wondering if anyone would be
willing to create a "Troubleshooting" document, containing a methodology to
track down and correct errors. I feel like this is missing a bit in relation t
Additionnaly, stopping VIP73 only stop the ZK resource, not PostgreSQL.
I'm definitely doing something wrong or making bad assumptions. Can anyone
help ?
Thank you !
Jun 25 05:44:11 clustera cib[33828]: info: cib:diff: -
Jun 25 05:44:11 clustera cib[33828]: info: cib:diff: +
Jun 25 05:44
Hi all,
My setup is as follows : RedHat 6.3 (yes, I know,this is quite old) ,
Pacemaker 1.1.7, Corosync 1.4.1.
I noticed something that is strange because since it doesn't complies with
what I read (and understood) from the following ressources :
1. http://crmsh.nongnu.org/crm.8.html#cmdhelp_conf
On Wed, Jun 25, 2014 at 10:57 AM, Gianluca Cecchi wrote:
>
> Tried to select "feedback" button at bottom but it doesn't work (at least
> on my chrome browser on Fedora 20) for niether the italy one not the
> english one...
>
>
Actually the Italian feedback link was indeed not able to show the fee
On Wed, Jun 25, 2014 at 1:28 AM, Andrew Beekhof wrote:
>
> > SO it seems at midnight the resource already was with a failcount of 2
> (perhaps caused by problems happened weeks ago..?) and then at 03:38 got a
> timeout on monitoring its state and was relocated...
> >
> > pacemaker is at 1.1.6-1.2
Hi all,
Aside of the thorough and comprehensive documentation, I was wondering if
anyone would be willing to create a "Troubleshooting" document, containing a
methodology to track down and correct errors. I feel like this is missing a bit
in relation to the ample but sometimes (to me at least)
Thank you for your reply, I am aware of STONITH resource named
external/vcenter (or external/vmware I'm not sure at this moment).
The setup is more involved and somehow requires more software
installation and writing a password to my hypervisor in a file (which I
feel uneasy), but I postpone a
Hi Vijay B,
I have 2 Debian machines with the latest Corosync and Pacemaker.
I wanted the latest versions of these packages, so I didn't use "apt-get
install corosync pacemaker".
Instead of that I downloaded the sources, built it and installed it.
I have a document with all steps I did to get it w
19 matches
Mail list logo
