Hi Andrew,
About a similar problem, we confirmed it in Pacemaker1.1.12.
The problem occurs in (glib2.40.0) in Ubuntu14.04.
lrmd[1632]: error: crm_abort: crm_glib_handler: Forked child 1840 to record
non-fatal assert at logging.c:73 : Source ID 51 was not found when attempting
to remove it
lr
On 2 Oct 2014, at 6:23 pm, Dmitry Pozdeiev wrote:
> Andrew Beekhof writes:
>
>> On 30 Sep 2014, at 5:32 am, Dmitry Pozdeiev wrote:
>>
>>> Forgot provide system info.
>>>
>>> Gentoo Linux 3.14.14 x86_64
>>> systemd 215-r3
>>> netctl 1.9
>>> corosync 2.3.3
>>> pacemaker 1.1.10
>>
>> ^^ syste
On 3 Oct 2014, at 12:10 am, Riccardo Bicelli wrote:
> I'm running pacemaker-1.0.10
well and truly time to get off the 1.0.x series
> and glib-2.40.0-r1:2 on gentoo
>
> Il 30/09/2014 23:23, Andrew Beekhof ha scritto:
>> On 30 Sep 2014, at 11:36 pm, Riccardo Bicelli
>> wrote:
>>
>>
>>> He
Am 02.10.2014 18:02, schrieb Digimer:
On 02/10/14 02:44 AM, Felix Zachlod wrote:
I am currently running 8.4.5 on to of Debian Wheezy with Pacemaker 1.1.7
Please upgrade to 1.1.10+!
Are you referring to a special bug/ code change? I normally don't like
building all this stuff from source in
emmanuel segura writes:
> for guest fencing you can use, something like this
> http://www.daemonzone.net/e/3/, rather to have a full cluster stack in
> your guest, you can try to use pacemaker-remote for your virtual guest
I think it could be done for the pure quorum node, but my other node
need
for guest fencing you can use, something like this
http://www.daemonzone.net/e/3/, rather to have a full cluster stack in
your guest, you can try to use pacemaker-remote for your virtual guest
2014-10-02 18:41 GMT+02:00 Daniel Dehennin :
> Hello,
>
> I'm setting up a 3 nodes OpenNebula[1] cluster
Hello,
I'm setting up a 3 nodes OpenNebula[1] cluster on Debian Wheezy using a
SAN for shared storage and KVM as hypervisor.
The OpenNebula fontend is a VM for HA[2].
I had some quorum issues when the node running the fontend die as the
two other nodes loose quorum, so I added a pure quorum node
On 02/10/14 02:44 AM, Felix Zachlod wrote:
I am currently running 8.4.5 on to of Debian Wheezy with Pacemaker 1.1.7
Please upgrade to 1.1.10+!
--
Digimer
Papers and Projects: https://alteeve.ca/w/
What if the cure for cancer is trapped in the mind of a person without
access to education?
__
Andrei,
I suspect that you think in a way 'if there is a default monitor
interval value of 60s monitor operation should occur every 60
seconds', correct?
Well, this is not true: you have to define (add) all operations manually.
Sorry if my guess is incorrect.
Best regards,
Alex
2014-10-02 12:2
Hi,
On Thu, Oct 02, 2014 at 12:22:35PM +0400, Andrei Borzenkov wrote:
> Is it possible to display values for all resource properties,
> including those set to default values?
What do you consider a "property"? Instance attributes or meta
attributes? Or both? The defaults for the former live in th
I'm running pacemaker-1.0.10 and glib-2.40.0-r1:2 on gentoo
Il 30/09/2014 23:23, Andrew Beekhof ha scritto:
On 30 Sep 2014, at 11:36 pm, Riccardo Bicelli wrote:
Hello,
I've just updated my cluster nodes and now I see lot of these errors in syslog:
Sep 30 15:32:43 localhost cib: [2870]: ERR
On Thu, Oct 2, 2014 at 2:36 PM, emmanuel segura wrote:
> I don't know if you can use Dummy primitivi as MS
>
> egrep "promote|demote" /usr/lib/ocf/resource.d/pacemaker/Dummy
> echo $?
> 1
>
Yes, I know I'm not bright, but still not *that* stupid :)
cn1:/usr/lib/ocf/resource.d # grep -E 'promote|
I don't know if you can use Dummy primitivi as MS
egrep "promote|demote" /usr/lib/ocf/resource.d/pacemaker/Dummy
echo $?
1
2014-10-02 12:02 GMT+02:00 Andrei Borzenkov :
> According to documentation (Pacemaker 1.1.x explained) "when
> [Master/Slave] the resource is started, it must come up in t
On Sun, Sep 28, 2014 at 3:03 PM, emmanuel segura wrote:
> try to use interleave meta attribute in your clone definition
>
Yes, you were right. I missed the fact that it was split between two
clones. Sorry, just starting with pacemaker , still learning ...
Thank you!
> http://www.hastexo.com/res
According to documentation (Pacemaker 1.1.x explained) "when
[Master/Slave] the resource is started, it must come up in the
mode called Slave". But what I observe here - in some cases pacemaker
treats Slave state as error. As example (pacemaker 1.1.9):
Oct 2 13:23:34 cn1 pengine[9446]: notice:
Is it possible to display values for all resource properties,
including those set to default values? cibadmin or "crm configure
show" display only explicitly set properties, and crm_resource or "crm
resource meta" work with single property only. Ideally I'd like to get
actual values of all resource
Am 02.10.2014 09:01, schrieb Felix Zachlod:
Am 02.10.2014 08:44, schrieb Felix Zachlod:
Am 01.10.2014 20:46, schrieb Digimer:
At some point along the way, both nodes were Primary while not
connected, even if for just a moment. Your log snippet above shows the
results of this break, they do not
Am 02.10.2014 08:44, schrieb Felix Zachlod:
Am 01.10.2014 20:46, schrieb Digimer:
At some point along the way, both nodes were Primary while not
connected, even if for just a moment. Your log snippet above shows the
results of this break, they do not appear to speak to the break itself.
Even
18 matches
Mail list logo
