[Pacemaker] Patch to crm command.
Hi, A load command of the crm command is a wrong order, but is handled as update. [root@srv01 ~]# crm configure load upadate trac1383.crm.dampen5s ---> miss upadate crm_verify[7602]: 2011/04/19_17:09:40 WARN: unpack_nodes: Blind faith: not fencing unseen nodes I send a patch. It is displayed the next by a patch. [root@srv01 ~]# crm crm(live)# configure crm(live)configure# load a.crm ERROR: unknown method crm(live)configure# cd crm(live)# quit bye [root@srv01 ~]# crm configure load xxx a.crm ERROR: unknown method xxx Best Regards, Hideo Yamauchi. cibconfig.patch Description: Binary data ___ 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
Re: [Pacemaker] crm_simulate small bug
Hi, Dejan Thank you for applying it! Thanks, Yuusuke IIDA (2011/05/25 18:30), Dejan Muhamedagic wrote: Hi, On Wed, May 25, 2011 at 05:43:05PM +0900, Yuusuke IIDA wrote: Hi, Andrew I used crm_simulate and found a small bug. A return code of the operation that I appointed in "-i option "is not handed definitely. Good catch! Applied. Cheers, Dejan Best Regards, Yuusuke IIDA -- METRO SYSTEMS CO., LTD Yuusuke Iida Mail: iiday...@intellilink.co.jp diff -r 0d3225be3f9d tools/crm_inject.c --- a/tools/crm_inject.cMon May 23 18:32:07 2011 +0200 +++ b/tools/crm_inject.cWed May 25 17:33:34 2011 +0900 @@ -793,7 +793,7 @@ cib_node = inject_node_state(global_cib, node); CRM_ASSERT(cib_node != NULL); - update_failcounts(cib_node, resource, interval, rc); + update_failcounts(cib_node, resource, interval, outcome); cib_resource = inject_resource(cib_node, resource, rclass, rtype, rprovider); CRM_ASSERT(cib_resource != NULL); ___ 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker ___ 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker -- METRO SYSTEMS CO., LTD Yuusuke Iida Mail: iiday...@intellilink.co.jp ___ 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
[Pacemaker] drbd log messages
Hello, I'm running following version of drbd on Linux 2.6.29.6-0.6.smp.gcc4.1.x86_64 #1 SMP version: 8.3.8.1 (api:88/proto:86-94) GIT-hash: 0d8589fcc32c874df57c930ca1691399b55ec893 build by rmake-chroot@localhost.localdomain, 2010-09-22 23:08:46 I'm seeing lots of these messages : = May 20 13:03:38 foo-01 pengine: [4062]: notice: common_apply_stickiness: ms-drbd can fail 99 more times on foo-01.trustblue.com before being forced off May 20 13:03:38 foo-01 pengine: [4062]: notice: LogActions: Leave resource drbd0:0(Slave foo-02.trustblue.com) May 20 13:03:38 foo-01 pengine: [4062]: notice: LogActions: Leave resource drbd0:1(Master foo-01.trustblue.com) May 20 11:51:51 foo-01 pengine: [4062]: notice: LogActions: Leave resource drbd0:0(Slave foo-02.trustblue.com) May 20 11:51:51 foo-01 pengine: [4062]: notice: LogActions: Leave resource drbd0:1(Master foo-01.trustblue.com) May 20 12:06:52 foo-01 pengine: [4062]: notice: clone_print: Master/Slave Set: ms-drbd [drbd0] May 20 12:06:52 foo-01 pengine: [4062]: notice: common_apply_stickiness: ms-drbd can fail 99 more times on foo-01.trustblue.com before being forced off May 20 12:06:52 foo-01 pengine: [4062]: notice: common_apply_stickiness: ms-drbd can fail 99 more times on foo-01.trustblue.com before being forced off May 20 12:06:52 foo-01 pengine: [4062]: notice: LogActions: Leave resource drbd0:0(Slave foo-02.trustblue.com) May 20 12:06:52 foo-01 pengine: [4062]: notice: LogActions: Leave resource drbd0:1(Master foo-01.trustblue.com) May 20 12:21:52 foo-01 pengine: [4062]: notice: clone_print: Master/Slave Set: ms-drbd [drbd0] May 20 12:21:52 foo-01 pengine: [4062]: notice: common_apply_stickiness: ms-drbd can fail 99 more times on foo-01.trustblue.com before being forced off May 20 12:21:52 foo-01 pengine: [4062]: notice: common_apply_stickiness: ms-drbd can fail 99 more times on foo-01.trustblue.com before being forced off May 20 12:21:52 foo-01 pengine: [4062]: notice: LogActions: Leave resource drbd0:0(Slave foo-02.trustblue.com) May 20 12:21:52 foo-01 pengine: [4062]: notice: LogActions: Leave resource drbd0:1(Master foo-01.trustblue.com) May 20 12:34:40 foo-01 lrmd: [4060]: info: rsc:drbd0:1:63: monitor May 20 12:36:52 foo-01 pengine: [4062]: notice: clone_print: Master/Slave Set: ms-drbd [drbd0] May 20 12:36:52 foo-01 pengine: [4062]: notice: common_apply_stickiness: ms-drbd can fail 99 more times on foo-01.trustblue.com before being forced off May 20 12:36:52 foo-01 pengine: [4062]: notice: common_apply_stickiness: ms-drbd can fail 99 more times on foo-01.trustblue.com before being forced off May 20 12:36:52 foo-01 pengine: [4062]: notice: LogActions: Leave resource drbd0:0(Slave foo-02.trustblue.com) May 20 12:36:52 foo-01 pengine: [4062]: notice: LogActions: Leave resource drbd0:1(Master foo-01.trustblue.com) May 20 12:51:52 foo-01 pengine: [4062]: notice: clone_print: Master/Slave Set: ms-drbd [drbd0] May 20 12:51:52 foo-01 pengine: [4062]: notice: common_apply_stickiness: ms-drbd can fail 99 more times on foo-01.trustblue.com before being forced off May 20 12:51:52 foo-01 pengine: [4062]: notice: common_apply_stickiness: ms-drbd can fail 99 more times on foo-01.trustblue.com before being forced off May 20 12:51:52 foo-01 pengine: [4062]: notice: LogActions: Leave resource drbd0:0(Slave foo-02.trustblue.com) May 20 12:51:52 foo-01 pengine: [4062]: notice: LogActions: Leave resource drbd0:1(Master foo-01.trustblue.com) May 20 12:59:12 foo-01 kernel: block drbd1: pdsk( UpToDate -> Diskless ) May 20 12:59:12 foo-01 kernel: block drbd1: Creating new current UUID May 20 12:59:13 foo-01 kernel: block drbd1: real peer disk state = Consistent May 20 12:59:13 foo-01 kernel: block drbd1: drbd_sync_handshake: May 20 12:59:13 foo-01 kernel: block drbd1: self 7BFDD5CAEC7E3D71:D4618C068872B92F:85DD32B6D2F5BCF0:42ABBC298069B9B4 bits:0 flags:0 May 20 12:59:13 foo-01 kernel: block drbd1: peer D4618C068872B92E::85DD32B6D2F5BCF0:42ABBC298069B9B4 bits:0 flags:2 May 20 12:59:13 foo-01 kernel: block drbd1: uuid_compare()=1 by rule 70 May 20 12:59:13 foo-01 kernel: block drbd1: conn( Connected -> WFBitMapS ) pdsk( Diskless -> Outdated ) May 20 12:59:13 foo-01 kernel: block drbd1: peer( Secondary -> Unknown ) conn( WFBitMapS -> TearDown ) May 20 12:59:13 foo-01 kernel: block drbd1: asender terminated May 20 12:59:13 foo-01 kernel: block drbd1: Terminating asender thread May 20 12:59:13 foo-01 kernel: block drbd1: oc_eds eund-2<>lc rd:sotsn eotiMpsz=06sn=1 May 20 12:59:13 foo-01 kernel: block drbd1: Handshake successful: Agreed network protocol version 94 May 20 12:59:13 foo-01 kernel: block drbd1: conn( WFConnection -> WFReportParams ) May 20 12:59:13 foo-01 kernel: block drbd1: Starting asender thread (from drbd1_receiver [20202]) May 20 12:59:13 foo-01 kernel: block drbd1: data-integrity-alg: M
Re: [Pacemaker] crm_simulate small bug
Hi, On Wed, May 25, 2011 at 05:43:05PM +0900, Yuusuke IIDA wrote: > Hi, Andrew > > I used crm_simulate and found a small bug. > A return code of the operation that I appointed in "-i option "is not handed > definitely. Good catch! Applied. Cheers, Dejan > Best Regards, > Yuusuke IIDA > > -- > > METRO SYSTEMS CO., LTD > > Yuusuke Iida > Mail: iiday...@intellilink.co.jp > > diff -r 0d3225be3f9d tools/crm_inject.c > --- a/tools/crm_inject.c Mon May 23 18:32:07 2011 +0200 > +++ b/tools/crm_inject.c Wed May 25 17:33:34 2011 +0900 > @@ -793,7 +793,7 @@ > cib_node = inject_node_state(global_cib, node); > CRM_ASSERT(cib_node != NULL); > > - update_failcounts(cib_node, resource, interval, rc); > + update_failcounts(cib_node, resource, interval, outcome); > > cib_resource = inject_resource(cib_node, resource, rclass, rtype, > rprovider); > CRM_ASSERT(cib_resource != NULL); > ___ > 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker ___ 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
Re: [Pacemaker] stonith question
Hi, On Tue, May 24, 2011 at 01:40:49PM -0500, Phil Armstrong wrote: > Hi, > > I have a 2 node cluster with stonith disabled: > > name="stonith-enabled" value="false"/> > > This is on an x86_64 liux system. I was having trouble getting a > system dump. I would drop into kdb, then enter kdump. The dump > process would appear to initiate, then it would hang, and then the > machine would reboot itself as if it had been stonith'd. This was > when I had both nodes active in the HA cluster. > > I stopped openais on both nodes and I was able to get all the darn > system dumps I wanted. But before that (when openais was on) I could > find no evidence in the logs of the node that remained up that it > had decided to shoot the node doing the kdump, and of course once I > dropped into kdb there was no evidence of anything in that node's > log. > > My question is is there ever any situation with stonith disabled > that a node would shoot either itself or another node in the > cluster. I don't think so. You may also want to take a look at external/kdumpcheck. That should allow you to use fencing and get the kdump. Thanks, Dejan > I can get an hb_report if someone thinks that would be > helpful, but for now I'm just posing the above question. > > Thanks. > > Phil > > > -- > Phil Armstrong p...@sgi.com > Phone: 651-683-5561 VNET 233-5561 > > > ___ > 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker ___ 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
Re: [Pacemaker] CRM: 'ascii' codec can't encode character
On Wed, May 25, 2011 at 10:59:12AM +0200, Nikita Michalko wrote:
> Hi Lars,
>
> thank you very match - indeed that was it! After changing the value of
> "timeout" to 60, the crm shell work again.
> I changed also utf8 coding to locale - much better ...
So, which locale do you actually use?
Thanks,
Dejan
>
> Best wishes
>
> Nikita Michalko
>
>
> Am Mittwoch 25 Mai 2011 10:09:49 schrieb Lars Ellenberg:
> > On Wed, May 25, 2011 at 09:12:29AM +0200, Nikita Michalko wrote:
> > > Hi Dejan,
> > >
> > >
> > > thanks for your reply! Here is the output of the command :
> > > /usr/lib64/heartbeat/crmd version
> > > CRM Version: 1.1.5 (ecb6baaf7fc091b023d6d4ba7e0fce26d32cf5c8)
> > > And cib.xml is attached ...
> >
> > There:
> > > > > value="6ß"/>
> >
> > You got an "6ß" there (or at least that's what it looks like when
> > converted to utf8...)
> >
> > Change that to 6s (or whatever you actually meant),
> > and the crm shell will work again.
> >
> > Below patchlet makes the crm shell not crash on this for me.
> > But I'm not sure if hardcoding "utf8" is the best way forward,
> > probably it should be locale aware.
> > Possibly it needs to put a try execpt around that s.encode,
> > and chose a different representation, if it is not possible
> > to encode it in whatever the current locale is?
> >
> >
> > diff --git a/shell/modules/parse.py b/shell/modules/parse.py
> > --- a/shell/modules/parse.py
> > +++ b/shell/modules/parse.py
> > @@ -728,7 +728,7 @@ class CliParser(object):
> > '''
> > cli_list = ''
> > if type(s) == type(u''):
> > -s = s.encode('ascii')
> > +s = s.encode('utf8')
> > if type(s) == type(''):
> > if s and s.startswith('#'):
> > self.comments.append(s)
> >
>
> ___
> 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
___
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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
Re: [Pacemaker] CRM: 'ascii' codec can't encode character
Hi Lars,
On Wed, May 25, 2011 at 10:09:49AM +0200, Lars Ellenberg wrote:
> On Wed, May 25, 2011 at 09:12:29AM +0200, Nikita Michalko wrote:
> > Hi Dejan,
> >
> >
> > thanks for your reply! Here is the output of the command :
> > /usr/lib64/heartbeat/crmd version
> > CRM Version: 1.1.5 (ecb6baaf7fc091b023d6d4ba7e0fce26d32cf5c8)
> > And cib.xml is attached ...
>
> There:
> > > value="6ß"/>
>
> You got an "6ß" there (or at least that's what it looks like when
> converted to utf8...)
>
> Change that to 6s (or whatever you actually meant),
> and the crm shell will work again.
Thanks for looking into this.
> Below patchlet makes the crm shell not crash on this for me.
> But I'm not sure if hardcoding "utf8" is the best way forward,
> probably it should be locale aware.
Yes, it really should. At least comments and some description
fields should be able to contain the locale specific encoding. At
the time I had a problem with the python lexer, though I can't
recall anymore what it exactly was, I think that it was not
capable of dealing with non-ascii stuff. But perhaps I was just
misusing it. Need to investigate this further.
> Possibly it needs to put a try execpt around that s.encode,
> and chose a different representation, if it is not possible
> to encode it in whatever the current locale is?
Yep, a good idea.
Cheers,
Dejan
> diff --git a/shell/modules/parse.py b/shell/modules/parse.py
> --- a/shell/modules/parse.py
> +++ b/shell/modules/parse.py
> @@ -728,7 +728,7 @@ class CliParser(object):
> '''
> cli_list = ''
> if type(s) == type(u''):
> -s = s.encode('ascii')
> +s = s.encode('utf8')
> if type(s) == type(''):
> if s and s.startswith('#'):
> self.comments.append(s)
>
>
> --
> : Lars Ellenberg
> : LINBIT | Your Way to High Availability
> : DRBD/HA support and consulting http://www.linbit.com
>
> DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.
>
> ___
> 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
___
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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
Re: [Pacemaker] CRM: 'ascii' codec can't encode character
Hi Lars,
thank you very match - indeed that was it! After changing the value of
"timeout" to 60, the crm shell work again.
I changed also utf8 coding to locale - much better ...
Best wishes
Nikita Michalko
Am Mittwoch 25 Mai 2011 10:09:49 schrieb Lars Ellenberg:
> On Wed, May 25, 2011 at 09:12:29AM +0200, Nikita Michalko wrote:
> > Hi Dejan,
> >
> >
> > thanks for your reply! Here is the output of the command :
> > /usr/lib64/heartbeat/crmd version
> > CRM Version: 1.1.5 (ecb6baaf7fc091b023d6d4ba7e0fce26d32cf5c8)
> > And cib.xml is attached ...
>
> There:
> > > value="6ß"/>
>
> You got an "6ß" there (or at least that's what it looks like when
> converted to utf8...)
>
> Change that to 6s (or whatever you actually meant),
> and the crm shell will work again.
>
> Below patchlet makes the crm shell not crash on this for me.
> But I'm not sure if hardcoding "utf8" is the best way forward,
> probably it should be locale aware.
> Possibly it needs to put a try execpt around that s.encode,
> and chose a different representation, if it is not possible
> to encode it in whatever the current locale is?
>
>
> diff --git a/shell/modules/parse.py b/shell/modules/parse.py
> --- a/shell/modules/parse.py
> +++ b/shell/modules/parse.py
> @@ -728,7 +728,7 @@ class CliParser(object):
> '''
> cli_list = ''
> if type(s) == type(u''):
> -s = s.encode('ascii')
> +s = s.encode('utf8')
> if type(s) == type(''):
> if s and s.startswith('#'):
> self.comments.append(s)
>
___
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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
[Pacemaker] crm_simulate small bug
Hi, Andrew I used crm_simulate and found a small bug. A return code of the operation that I appointed in "-i option "is not handed definitely. Best Regards, Yuusuke IIDA -- METRO SYSTEMS CO., LTD Yuusuke Iida Mail: iiday...@intellilink.co.jp diff -r 0d3225be3f9d tools/crm_inject.c --- a/tools/crm_inject.c Mon May 23 18:32:07 2011 +0200 +++ b/tools/crm_inject.c Wed May 25 17:33:34 2011 +0900 @@ -793,7 +793,7 @@ cib_node = inject_node_state(global_cib, node); CRM_ASSERT(cib_node != NULL); - update_failcounts(cib_node, resource, interval, rc); + update_failcounts(cib_node, resource, interval, outcome); cib_resource = inject_resource(cib_node, resource, rclass, rtype, rprovider); CRM_ASSERT(cib_resource != NULL); ___ 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
Re: [Pacemaker] CRM: 'ascii' codec can't encode character
On Wed, May 25, 2011 at 09:12:29AM +0200, Nikita Michalko wrote:
> Hi Dejan,
>
>
> thanks for your reply! Here is the output of the command :
> /usr/lib64/heartbeat/crmd version
> CRM Version: 1.1.5 (ecb6baaf7fc091b023d6d4ba7e0fce26d32cf5c8)
> And cib.xml is attached ...
There:
> value="6ß"/>
You got an "6ß" there (or at least that's what it looks like when
converted to utf8...)
Change that to 6s (or whatever you actually meant),
and the crm shell will work again.
Below patchlet makes the crm shell not crash on this for me.
But I'm not sure if hardcoding "utf8" is the best way forward,
probably it should be locale aware.
Possibly it needs to put a try execpt around that s.encode,
and chose a different representation, if it is not possible
to encode it in whatever the current locale is?
diff --git a/shell/modules/parse.py b/shell/modules/parse.py
--- a/shell/modules/parse.py
+++ b/shell/modules/parse.py
@@ -728,7 +728,7 @@ class CliParser(object):
'''
cli_list = ''
if type(s) == type(u''):
-s = s.encode('ascii')
+s = s.encode('utf8')
if type(s) == type(''):
if s and s.startswith('#'):
self.comments.append(s)
--
: Lars Ellenberg
: LINBIT | Your Way to High Availability
: DRBD/HA support and consulting http://www.linbit.com
DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.
___
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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
Re: [Pacemaker] CRM: 'ascii' codec can't encode character
Hi Dejan, thanks for your reply! Here is the output of the command : /usr/lib64/heartbeat/crmd version CRM Version: 1.1.5 (ecb6baaf7fc091b023d6d4ba7e0fce26d32cf5c8) And cib.xml is attached ... Best wisshes Nikita Michalko Am Dienstag 24 Mai 2011 15:44:47 schrieb Dejan Muhamedagic: > Hi Nikita, > > On Tue, May 24, 2011 at 02:31:13PM +0200, Nikita Michalko wrote: > > Hi all, > > > > after installing (from RPMs) & configuring 2-node cluster with crm > > yesterday, it suddenly shows today error: > > crm > > crm(live)# configure > > ERROR: 'ascii' codec can't encode character u'\xdf' in position 71: > > ordinal not in range(128) > > > > Did anybody seen this error? What is wrong with crm? > > Which version is this? Please send output from: > > $ /usr/lib64/heartbeat/crmd version > > Can you also attach the CIB (the XML version) or send it to me > privately. > > Thanks, > > Dejan > > > TIA for any response! > > > > > > Nikita Michalko > > > > ___ > > 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker > > ___ > 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker > NM_cib.xml Description: XML document ___ 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
Re: [Pacemaker] How to ensure that a resource is only running at one place?
Hi Mark,
I totally agree with that, I was looking for a quick and simple
solution to this problem. But indeed it makes no sense to check
somewhere if a resource that should not run is running. I also imagine
that it would induce more work and a higher load due to those unneeded
checks.
I also understand now why it can be interesting to switch from basic
lsb scripts to generic OCF resource agent, just to get rid of the old
fashioned init.d script to avoid that scatter-brained users start
resources manually as when there was no pacemaker cluster.
Thank you,
Kevin,
> > Because by default on my asymmetric cluster I saw that the op monitor
> > action is only executed on the node where the resource is currently running,
> > and when a user start manually (not through the crm) the same resource on
> > another node pacemaker won't see it because it is not executing the op
> > monitor on all nodes that are potentially able to run the resource.
> >
>
> This makes complete sense. If pacemaker didn't start a resource, how is it
> expected to know to manage that resource?
>
>
> >
> > Am I obliged to write my own RA with a master/slave or primary/secondary
> > knowledge to be sure that the resource is active only at one place at a
> > time?
> >
> >
> Really, it seems the only obligation is to not allow a user to have shell
> access on your cluster nodes if they can't understand the concept of what a
> cluster is and won't listen to you when you explain to them that they must
> not start resources on their own just because they feel like it. It takes
> very little time to teach a user how to run 'crm status' or to show them a
> simple web page that will show them the status of all cluster resouces, so
> they can tell for themselves that the service they're about to start is
> already running (see the -h switch for crm_mon and imagine how you can have
> an apache resource that runs to show the web page it outputs).
>
> If a user doesn't understand what is really a pretty simple concept ("we run
> a cluster suite and it starts/stops these particular resources itself, so
> don't ever, ever touch them unless told to do so"), then it's pretty
> dangerous to let them onto the cluster nodes in the first place, no? Do you
> have the option of changing permissions so that the users can't start the
> resource, can't execute the scripts/binaries required, and instead only the
> cluster suite, the root user, and perhaps a trusted admin or two can?
>
> Regards,
> Mark
___
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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
