lock/8:208 /dev/block/8:48
/dev/block/8:176 /dev/block/8:192 ]
1) Is there any way to bring the real qdisk online?
2) Is there something I am missing to not import the qdisk as a node?
Thanks for the time!
Rob
___
Pacemaker mailing list:
erby thing tonight, so I thought I may throw it to the crowds before
I start going down too many blind alleys.
Question 2: What else is going to bite me? 8)
Sorry for the length!
--Rob
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.or
On 15/11/2013 9:01 PM, "Andrew Beekhof" wrote:
> N. Not on RHEL-6 anyway.
> Before I address the rest of your email, you need to be using pacemaker
with cman (cluster.conf) as described at:
>
Yep, I'm pretty sure I followed that. However, it's also possible that I
missed something, so I'll
cause that's not using anything that uses
getNodesFromCorosyncConf() which is everywhere through cluster.py
But after doing the commands in there, if you try to set a node
offline, it doesn't work, and comes up with that error that the node
doesn't exist.
--Rob
___
his mailing list with problems with RedHat's
documentation (eg, 3.2 says 'pcs cluster setup [--start] [--local]
cluster_name node1 [node2] [...]' but the ACTUAL command you run is
'pcs cluster setup --name=cluster_name node1 [node2] [...]')
--Rob
> Line 363 of /usr/lib/python2.6/site-packages/pcs/cluster.py has this:
>
> nodes = utils.getNodesFromCorosyncConf()
Ahha. Look what I just spotted.
https://github.com/feist/pcs/commit/8b888080c37ddea88b92dfd95aadd78b9db68b55
--Rob
___
as this is now a RedHat bug, not a pacemaker bug, I'm going
to stop talking about it on this list 8)
(I emailed Chris Feist, who I don't think I know, off list, as he
seems to be The Guy(tm))
--Rob
___
Pacemaker mailing list: Pacemaker@oss.clust
sources, but, it seems untidy to me.
I've tried a colocation set, which does let you add groups, but it
doesn't seem to do what I'm after.
Attached is the dump of my current config.
Any advice or help would be appreciated!
(Currently on CentOS
tor_3 on freepbx-a 'not running' (7):
call=2217, status=complete, last-rc-change='Mon Nov 18 14:05:08 2013',
queued=0ms, exec=0ms
I've been browsing through the cluster.log, and it's not even trying
to move httpd. I'm almost certain that it used to work fine with
generating.
This works:
It appears that pcs can't do that, or if it's possible to, I can't
figure out how.
Which is why I've been fighting with it all day!
Is this
On Mon, Nov 18, 2013 at 9:17 PM, Andrew Beekhof wrote:
> my eyes! my eyes!
So... What's the -right- way to do it then? 8)
--Rob
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
On Tue, Nov 19, 2013 at 8:55 AM, Andrew Beekhof wrote:
>
> On 19 Nov 2013, at 6:00 am, Rob Thomas wrote:
>> So... What's the -right- way to do it then? 8)
>
>
>
>
>
>
>
>
> is almost right, but mis
>>> On 19 Nov 2013, at 6:00 am, Rob Thomas wrote:
>>>> So... What's the -right- way to do it then? 8)
>>>
>>>
>>>
>>>
>>>
>>>
>>>
...
>> I'll hav
b.com/xrobau/pacemaker/commit/b1515e3f83fceeac951de8823d718bdf13e4a093
--Rob
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started:
maker/commit/9663a1b1d5fd1d353e144c268830bafa95192434
--Rob
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started: http://www.cluster
chore . Is there a tool/heuristic/rule of
thumb to help?
Cross-eyed from reading logs,
Rob
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
We're running SLES 11 SP1 so we're running pacemaker-1.1.5.
By the way, I am aware of the hb_report tool. It's a start but I haven't
found it to be particularly useful.
Rob
On Tue, Aug 14, 2012 at 6:20 AM, Sutherland, Rob
wrote:
> Whenever something goes wrong with on
x27;s any useful information I can provide from /var/log/messages
I'd be happy to provide them, but I just need to know which parts you
consider important, as there's tonnes of them!
--Rob
___
Pacemaker mailing list: Pacemaker@os
debug this, though.
Any hints on debugging this?
BTW: we only ever see this on a site 2 - never a site 1. This is consistent
across several labs. Is there a bias towards site 1?
Thanks in advance,
Rob
___
Pacemaker mailing list: Pacemaker@oss
All nodes in question NTP from the same time source (yes, we have run into
synchronicity issues in the past).
Interestingly, increasing the lease from 60 seconds to 120 seconds did not
affect the behaviour.
Rob
From: John Lauro [mailto:john.la...@covenanteyes.com]
Sent: Monday, August 25
-Original Message-
From: Dejan Muhamedagic [mailto:deja...@fastmail.fm]
Sent: Wednesday, August 27, 2014 5:04 AM
To: pacemaker@oss.clusterlabs.org
Subject: Re: [Pacemaker] SLES 11 SP3 boothd behaviour
Hi,
On Mon, Aug 25, 2014 at 07:43:34PM +, Sutherland, Rob wrote:
> Hello
You don't seem to understand the problem. You are, inadvertently, exposing
us to your internal legal issues.
We do not wish to be exposed to internal, confidential, Dell issues. If
this is NOT an Internal, Confidential, Dell issue, remove that header.
[image: Inline image 1]
On Tue, Oct 6, 2015
22 matches
Mail list logo
