Am 29.10.2014 01:39, schrieb Andrew Beekhof:
I just have one question about how a resource agent should behave on "reload"
invoked if the resource is currently stopped. Should the resource be started or remain
stopped?
I don't think that is defined. Certainly pacemaker wont trigger that case
Hi,
I've never used crm_report before. I just read the man file and generated a
tarball from 1-2 hours before I reconfigured all the DRBD related
resources. I've put the tarball here -
https://www.dropbox.com/s/suj9pttjp403msv/unexplained-apache-failure.tar.bz2?dl=0
Hope you can help figure out w
Can you run crm_report so we can see the logs and PE files?
> On 28 Oct 2014, at 9:16 pm, Sihan Goi wrote:
>
> Hi,
>
> I followed those steps previously. I just tried it again, but I'm still
> getting the same error. My "crm configure show" shows the following:
>
> node node01 \
> att
> On 28 Oct 2014, at 6:07 pm, Felix Zachlod wrote:
>
> Hello folks,
>
>
> I just have one question about how a resource agent should behave on "reload"
> invoked if the resource is currently stopped. Should the resource be started
> or remain stopped?
I don't think that is defined. Certainl
> On 29 Oct 2014, at 9:30 am, Lax wrote:
>
> Andrew Beekhof writes:
>>> Thanks for your help as always Andrew. Is there any sample that you can
>>> point me to how to configure it for the resource.
>>
>> I mean something like:
>>
>>chkconfig {LSB-name} off
>>
> I tried setting it this
Today we are proud to announce the release of `crmsh` version 2.1.1!
This version primarily fixes all known issues found since the release
of `crmsh` 2.1 in June. We recommend that all users of crmsh upgrade
to this version, especially if using Pacemaker 1.1.12 or newer.
A massive thank you to ev
Andrew Beekhof writes:
> > Thanks for your help as always Andrew. Is there any sample that you can
> > point me to how to configure it for the resource.
>
> I mean something like:
>
> chkconfig {LSB-name} off
>
I tried setting it this way and still resource gets started on both the
nodes
> On 28 Oct 2014, at 8:59 pm, philipp.achmuel...@arz.at wrote:
>
> hi,
>
> any recommendation/documentation for a reliable fencing implementation on a
> multi-node cluster (4 or 6 nodes on 2 site).
> i think of implementing multiple node-fencing devices for each host to
> stonith remaining n
> On 29 Oct 2014, at 7:42 am, Lax wrote:
>
> Andrew Beekhof writes:
>
> So on pacemaker restart, is there any way I can stop my LSB resource
> coming
> up in START mode when such resource is already running on a master?
Tell init/systemd not to start it when the node boots
Andrew Beekhof writes:
> >>> So on pacemaker restart, is there any way I can stop my LSB resource
coming
> >>> up in START mode when such resource is already running on a master?
> >>
> >> Tell init/systemd not to start it when the node boots
> >
> > Thanks for the response Andrew.
> >
> > Bu
hi,
Von:Dejan Muhamedagic
An: The Pacemaker cluster resource manager
Datum: 28.10.2014 16:45
Betreff:Re: [Pacemaker] fencing with multiple node cluster
>
>
>Hi,
>
>On Tue, Oct 28, 2014 at 09:51:02AM -0400, Digimer wrote:
>>> On 28/10/14 05:59 AM, philipp.achmuel...@arz.at w
Hi,
On Tue, Oct 28, 2014 at 09:51:02AM -0400, Digimer wrote:
> On 28/10/14 05:59 AM, philipp.achmuel...@arz.at wrote:
>> hi,
>>
>> any recommendation/documentation for a reliable fencing implementation
>> on a multi-node cluster (4 or 6 nodes on 2 site).
>> i think of implementing multiple node-fe
On 28/10/14 02:24 AM, kamal kishi wrote:
Hi,
I know, no fencing configuration creates issue.
But the current scenario is due to fencing??
Maybe, maybe not. I can say that *not* having it will make solving the
problem much more difficult. Please get it working, it's pretty easy and
it will
On 28/10/14 05:59 AM, philipp.achmuel...@arz.at wrote:
hi,
any recommendation/documentation for a reliable fencing implementation
on a multi-node cluster (4 or 6 nodes on 2 site).
i think of implementing multiple node-fencing devices for each host to
stonith remaining nodes on other site?
thank
Hi,
I followed those steps previously. I just tried it again, but I'm still
getting the same error. My "crm configure show" shows the following:
node node01 \
attributes standby=off
node node02
primitive ClusterIP IPaddr2 \
params ip=192.168.1.110 cidr_netmask=24 \
op moni
FYI: I cannot reproduce this problem right now. I guess I made a mistake
analyzing the logs.
--
andrena objects ag
Büro Frankfurt
Clemensstr. 8
60487 Frankfurt
Tel: +49 (0) 69 977 860 38
Fax: +49 (0) 69 977 860 39
http://www.andrena.de
Vorstand: Hagen Buchwald, Matthias Grund, Dr. Dieter Kuhn
Au
hi,
any recommendation/documentation for a reliable fencing implementation on
a multi-node cluster (4 or 6 nodes on 2 site).
i think of implementing multiple node-fencing devices for each host to
stonith remaining nodes on other site?
thank you!
Philipp
> On 28 Oct 2014, at 6:26 pm, Sihan Goi wrote:
>
> Hi,
>
> No, I did not do this. I followed the Pacemaker 1.1 - Clusters from scratch
> edition 5 for Fedora 13, and in section 7.3.4 it instructed me to run the
> following commands, which I did:
> mkfs.ext4 /dev/drbd1
> mount /dev/drbd1 /mnt
Andrei, Andrew,
I'm afraid the machine is not available to me anymore, i'm sorry.
I reproduced the problem on my laptop. It seems that a failing to
start colocated resource made some othe other resources to be demoted
and stopped.
So this is most likely a non issue.
I'll monitor this issue and l
Hi,
No, I did not do this. I followed the Pacemaker 1.1 - Clusters from scratch
edition 5 for Fedora 13, and in section 7.3.4 it instructed me to run the
following commands, which I did:
mkfs.ext4 /dev/drbd1
mount /dev/drbd1 /mnt
create index.html file in /mnt
umount /dev/drbd1
Subsequently, afte
Hello folks,
I just have one question about how a resource agent should behave on
"reload" invoked if the resource is currently stopped. Should the
resource be started or remain stopped? I did not find anything about
that in the documentation, in gernel there are not mant informations
about
21 matches
Mail list logo
