On Tue, Nov 30, 2010 at 5:57 PM, Patrick H. wrote:
> Well that fixed the problem. To me that seems weird that when A depends on B
> it doesnt work, but when B depends on A it works fine. But whatever, i'll
> just jot that little note down for future use.
Things get complicated when A is a clone b
>
>>Hi all
>> I use crm_node -i order to check node id. the result is as follow
>>
>> [r...@oss1 ~]# crm_node -i
>> 1678456074
>> Unknown option 'i'
>> crm_node - Tool for displaying low-level node information
>> Usage: crm_node command [options]
>> Options:
>> ?-?, --help ??This text
>> ?-$,
On 1 December 2010 04:28, jiaju liu wrote:
>
>
> >
> >>Hi all
> >> I use crm_node -i order to check node id. the result is as follow
> >>
> >> [r...@oss1 ~]# crm_node -i
> >> 1678456074
> >> Unknown option 'i'
> >> crm_node - Tool for displaying low-level node information
> >> Usage: crm_node comm
On 30 November 2010 20:39, Ziri Camden wrote:
>>> Things work great as long as I stick to a 2-node setup with STONITH
>>> disabled and quorum ignored. As soon as I add a third node, things get
>>> odd. The third node isn't seen by the rest of the cluster and doesn't
>>> see its peers.
>>
>> Usuall
>
>>Hi all
>> I use crm_node -i order to check node id. the result is as follow
>>
>> [r...@oss1 ~]# crm_node -i
>> 1678456074
>> Unknown option 'i'
>> crm_node - Tool for displaying low-level node information
>> Usage: crm_node command [options]
>> Options:
>> ?-?, --help ??This text
>> ?-$, -
I was thinking along the lines of your second suggestion.
It involves teaching my "external source" about relationships between
resources which I don't like but is possible.
A phrase from the '08 election cycle involving lipstick comes to mind ... ;)
Thanks for following up Tim!
Alan
On Mon, Nov 2
Hello,
The new releases of Heartbeat (3.0.4) and cluster-glue (1.0.7)
are mostly ready. The new code has been tested and we don't
expect any more changes. If you want to give them a whirl on your
test clusters, please do so and report any issues before
Monday Dec 6. On that day we'll issue the fin
>> Things work great as long as I stick to a 2-node setup with STONITH
>> disabled and quorum ignored. As soon as I add a third node, things get
>> odd. The third node isn't seen by the rest of the cluster and doesn't
>> see its peers.
>
> Usually its a firewall. Are they all connected to the same
Hi,
I have set up a three node cluster (running Ubuntu 10.04 LTS server with
Corosync 1.2.0, Pacemaker 1.0.8, drbd 8.3.7), where one node is only present to
provide quorum to the other two nodes in case one node fails but it itself
cannot run any resources. The other two nodes are running drbd
Well that fixed the problem. To me that seems weird that when A depends
on B it doesnt work, but when B depends on A it works fine. But
whatever, i'll just jot that little note down for future use.
Thanks
Sent: Tue Nov 30 2010 03:07:52 GMT-0700 (Mountain Standard Time)
From: Andrew Beekhof
To
On Tue, Nov 30, 2010 at 1:32 PM, Vit Pelcak wrote:
> class OCFS2(CIB10):
> def add_resources(self):
> self._create('''primitive clvm ocf:lvm2:clvmd op start interval="0"
> timeout="90s" op stop interval="0" timeout="100s"''')
> self._create('''primitive cmirror ocf:lvm2:cmirrord o
Hi,
On Sat, Nov 20, 2010 at 09:40:31AM -0500, Vadym Chepkov wrote:
> Hi,
>
> crm has a nice placement constraint syntax
>
> location loc1 res1 inf: node1
>
> which is a shortcut for
>
> location loc1 res1 inf: rule #uname eq node1
That's not so. The shortcut is in the XML not the shell. The
s
Dne 30.11.2010 13:14, Andrew Beekhof napsal(a):
I have put into attachment the one reasonably easy. It is about mounting
ext3 partition into mysql dir and then running mysql.
Problem here is, that doing so is not enough. I spotted, that is is
needed
to manually restart mysql when that ext3 parti
On Tue, Nov 30, 2010 at 12:41 PM, Vit Pelcak wrote:
> Dne 30.11.2010 11:21, Andrew Beekhof napsal(a):
>>
>> On Thu, Nov 25, 2010 at 1:36 PM, Vit Pelcak wrote:
>>>
>>> Hello everyone.
>>>
>>> I ran into problem.
>>>
>>> I cannot format ocfs2 partition with pcmk until "primitive o2cb
>>> ocf:ocfs2:
Dne 30.11.2010 11:21, Andrew Beekhof napsal(a):
On Thu, Nov 25, 2010 at 1:36 PM, Vit Pelcak wrote:
Hello everyone.
I ran into problem.
I cannot format ocfs2 partition with pcmk until "primitive o2cb
ocf:ocfs2:o2cb" is running. Right?
Probably
I have tested mkfs.ocfs2 as Tim suggested and i
On 11/30/2010 at 09:21 PM, Andrew Beekhof wrote:
> On Thu, Nov 25, 2010 at 1:36 PM, Vit Pelcak wrote:
> > Hello everyone.
> >
> > I ran into problem.
> >
> > I cannot format ocfs2 partition with pcmk until "primitive o2cb
> > ocf:ocfs2:o2cb" is running. Right?
>
> Probably
To my inten
On Thu, Nov 25, 2010 at 1:36 PM, Vit Pelcak wrote:
> Hello everyone.
>
> I ran into problem.
>
> I cannot format ocfs2 partition with pcmk until "primitive o2cb
> ocf:ocfs2:o2cb" is running. Right?
Probably
> I was thinking the way, that I would create scripts which would prepare
> cluster for m
On Mon, Nov 29, 2010 at 5:37 PM, Dejan Muhamedagic wrote:
> Hi,
>
> On Mon, Nov 29, 2010 at 02:42:42PM +0100, Uwe Grawert wrote:
>> Was: Re: [Pacemaker] crm resource restart doesn't restart the correct
>> resource
>>
>> Zitat von Dejan Muhamedagic :
>>
This is happening, because, when the cl
In general, its better to have the IP (primitive) depend on the clone. eg:
With that it behaved properly here.
On Mon, Nov 29, 2010 at 4:44 PM, Patrick H. wrote:
> Err, now its attached. Promise :-)
>
> -Patrick
>
> Sent: Mon Nov 29 2010 08:36:04 GMT-0700 (Mountain Standard Time)
> From:
On Mon, Nov 29, 2010 at 7:56 PM, Ziri Camden wrote:
> Hello,
>
> I'm evaluating Pacemaker and have been working my way through the
> excellent "Cluster from Scratch" document. I am using the stack as
> packaged in Debian Squeeze and attempting to set up a three-node
> cluster.
>
> Things work grea
On Mon, Nov 29, 2010 at 3:18 AM, wrote:
> Hi,
>
> We constituted a cluster by two node constitution.
> It is constitution complicated slightly that included two pingd in
> constitution.
>
> We confirmed a phenomenon in the next procedure.
>
> Step1) 192.168.40.3 addresses invalidate the understan
On Mon, Nov 29, 2010 at 3:39 AM, wrote:
> Hi,
>
> We constituted two simple nodes of the clone resource of one clone resource
> and
> stonith.
>
> But we set order of a stonith resource and the clone resource.
>
> We generated a problem in the next procedure.
>
> Step1)Start two nodes and send t
On Mon, Nov 29, 2010 at 5:11 AM, wrote:
> Hi Andrew,
>
> Sorry
> My response was late.
>
>> I think the smartest thing to do here is drop the cib_scope_local flag from
>> -f
>
> if(do_force) {
> crm_debug("Forcing...");
> /* cib_options |= cib_scope_local|c
23 matches
Mail list logo
