On Thu, 13 Feb 2014 09:56:56 +0900 (JST)
renayama19661...@ybb.ne.jp wrote:
But the next information appeared when I put crm.
Does this last message not have any problem?
---
[root@srv01 ~]# crm configure load update
db2-resource_set_0207.crm WARNING: pgsql:
Thanks Lars,
I understand that i have an out-of-memory situation, but I don't' understand
because swap memory is 100% free (128Gb).
Bye
Walter
-Original Message-
From: Lars Marowsky-Bree [mailto:l...@suse.com]
Sent: mercoledì 12 febbraio 2014 18:05
To: The Pacemaker cluster resource
On 2014-02-13T11:45:07, walter.pis...@erptech.it wrote:
Thanks Lars,
I understand that i have an out-of-memory situation, but I don't' understand
because swap memory is 100% free (128Gb).
Hard to say without knowing what leaked the memory. If it's a process
that locks itself into RAM, that
Hi,
i have a fresh 2 node cluster (kvm host1 - guest = nodeA | kvm host2 -
guest = NodeB) and it seems to work but from time to time i have a lot of
errors like
Feb 13 13:41:04 corosync [TOTEM ] Retransmit List: 196 198 184 185 186 187
188 189 18a 18b 18c 18d 18e 18f 190 191 192 193 194 195 197
Hi,
Check if your switch support multicat, however you can use unicast.
Bye
Walter
From: Beo Banks [mailto:beo.ba...@googlemail.com]
Sent: giovedì 13 febbraio 2014 17:22
To: pacemaker@oss.clusterlabs.org
Subject: [Pacemaker] Multicast pitfalls? corosync [TOTEM ] Retransmit List:
Hi,
i have a
hi thanks...for your help.
i have two node cluster
both node are running on seperate hosts.
the 2x hosts have 2 nic's eth0 is 172.XXX...whatever and eth1 is
direct connection (crossover cable) between the hosts.
the issue must be my kvm host,or?
2014-02-13 17:40 GMT+01:00
Can you post /etc/corosync/corosync.conf ?
Thanks
Walter
From: Beo Banks [mailto:beo.ba...@googlemail.com]
Sent: giovedì 13 febbraio 2014 18:01
To: The Pacemaker cluster resource manager
Subject: Re: [Pacemaker] Multicast pitfalls? corosync [TOTEM ] Retransmit List:
hi thanks...for your help.
I am excited to announce the release of Pacemaker v1.1.11
https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-1.1.11
There were no changes between the final release and rc5.
This has been a very successful release process. I'm proud of the testing
and contributions the community
here you are
i have add 2 lines windows_size and i switch from active to passive.
but both options doen st solve the issue :(
compatibility: whitetank
totem {
version: 2
secauth: on
threads: 0
token: 1
token_retransmits_before_loss_const: 10
# How long to wait for join messages in the
Corosync configuration is ok, can you use tcpdump for check connection ?
Bye
Walter
From: Beo Banks [mailto:beo.ba...@googlemail.com]
Sent: giovedì 13 febbraio 2014 18:32
To: The Pacemaker cluster resource manager
Subject: Re: [Pacemaker] Multicast pitfalls? corosync [TOTEM ] Retransmit List:
On 13/02/14 12:01 PM, Beo Banks wrote:
hi thanks...for your help.
i have two node cluster
both node are running on seperate hosts.
the 2x hosts have 2 nic's eth0 is 172.XXX...whatever and eth1 is
direct connection (crossover cable) between the hosts.
the issue must be my kvm host,or?
What
Awesome!
Thanks all! :D
On 13/02/14 12:26 PM, David Vossel wrote:
I am excited to announce the release of Pacemaker v1.1.11
https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-1.1.11
There were no changes between the final release and rc5.
This has been a very successful
Hello,
I am still looking for help on these unknown error(1) messages from pengine.
Is my assessment correct that these error messages are the root cause for
pacemaker to think that resource is active on both nodes? Any help will be much
appreciated.
Ajay
Great job David, thanks for taking the lead on this role while I was on baby
duty :)
On 14 Feb 2014, at 4:26 am, David Vossel dvos...@redhat.com wrote:
I am excited to announce the release of Pacemaker v1.1.11
https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-1.1.11
The previous patch wasn't quite right.
Could you try this new one?
http://paste.fedoraproject.org/77123/13923376/
[11:23 AM] beekhof@f19 ~/Development/sources/pacemaker/devel ☺ # git diff
diff --git a/crmd/callbacks.c b/crmd/callbacks.c
index ac4b905..d49525b 100644
--- a/crmd/callbacks.c
Hi Kristoffer,
Thank you for comments.
But the next information appeared when I put crm.
Does this last message not have any problem?
---
[root@srv01 ~]# crm configure load update
db2-resource_set_0207.crm WARNING: pgsql: action monitor not
advertised
Yes, of course. Now beginning build world and test )
14.02.2014, 04:41, Andrew Beekhof and...@beekhof.net:
The previous patch wasn't quite right.
Could you try this new one?
http://paste.fedoraproject.org/77123/13923376/
[11:23 AM] beekhof@f19 ~/Development/sources/pacemaker/devel ☺ #
On 14.02.2014 02:50, Dennis Jacobfeuerborn wrote:
Hi,
I'm still working on my NFSv4 cluster and things are working as
expected...as long as I don't add an IPAddr2 resource.
The DRBD, filesystem and exportfs resources work fine and when I put the
active node into standby everything fails over as
hi
[bad udp cksum fa38!]
is that a normal?
node 1
tcpdump -envv port 5405 -i eth1
tcpdump: listening on eth1, link-type EN10MB (Ethernet), capture size 65535
bytes
08:46:01.230420 52:54:00:09:ef:2f 52:54:00:ba:8a:1c, ethertype IPv4
(0x0800), length 149: (tos 0x0, ttl 64, id 0, offset 0,
19 matches
Mail list logo
