preferred_lft forever
Kind regards,
Jelle de Jong
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
iJwEAQECAAYFAlJSuVQACgkQ1WclBW9j5HmsMwP+IU2bH7rTTj6jKg4B23o8fN7K
QQAxlkaBa4QvfbASkSzmXHwPMnLVqaTrWNRKa58EYXrNoMkTSbGGKYlQK1CLSQcR
QHe0USxZdPHDJmj6N/NYlfuZKLW1UL0iGyf98rc8g2KF4cXAsnvlnrT
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 29/07/13 20:58, Arnold Krille wrote:
So further testing show that the bonded interfaces below seem to
eat all broadcasts and all forwards (for the virtual machines).
Don't know why yet. But as soon as I switched my network-config to
use the
On 26-10-11 22:57, Arturo Borrero Gonzalez wrote:
Now i'm very busy building an openldap active/active cluster with
pacemaker, and I don't have the time to translate.
I think that when I have a bit more free time I will translate the full
document. In fact, I remember that I start
wants to translate it to english.
I cant read Spanish at all :) Google translate helped a bit.
I am interested in your conclusions and comparisons between a keepalived
vs pacemaker/corosync redundant firewall set-up. Maybe you can translate
these parts?
Kind regards,
Jelle de Jong
On 16-06-11 08:38, Florian Haas wrote:
On 06/16/2011 12:50 AM, imnotpc wrote:
Funny but it looks fairly unequivocal to me.
Yes and no. The message is clear but unless you have someone sitting at
a console 24/7 running tail on the log file, it has little value.
According to the ClusterLabs
On 14-06-11 22:35, Florian Haas wrote:
On 06/14/2011 01:38 PM, Jelle de Jong wrote:
# disk erros during iscsi/drbd migration on kvm host system
http://paste.debian.net/119830/
You need to either use portblock (check the guide I mentioned in my 2/24
message), or move the IP address
in a usable state and
then execute the meatclient -c hennessy command so AFTER a reboot.
The only documentation I could find:
less -S /usr/share/doc/cluster-glue/stonith/README.meatware
Thanks in advance,
Kind regards,
Jelle de Jong
___
Pacemaker mailing list
On 14-06-11 15:22, Florian Haas wrote:
On 2011-06-10 17:28, Jelle de Jong wrote:
The problem is most of my kvm guest file-systems get corrupted when
migrating my iscsi target on heavy disk load on the kvm guests.
Have you tried setting DefaultTime2Retain like I suggested on Feb 24?
Yes I did
On 14-06-11 15:48, Florian Haas wrote:
On 2011-06-14 15:41, Jelle de Jong wrote:
On 14-06-11 15:22, Florian Haas wrote:
On 2011-06-10 17:28, Jelle de Jong wrote:
The problem is most of my kvm guest file-systems get corrupted when
migrating my iscsi target on heavy disk load on the kvm guests
On 27-05-11 18:19, Roman Schartlmüller wrote:
Can anybody please help me with configuration? Maybe there is something
wrong.
Maybe lose the no-quorum-policy=ignore options. And a html mail with
tables really :D
Kind regards,
Jelle de Jong
from a network issues)
Thanks in advance,
Kind regards,
Jelle de Jong
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started: http
de Jong
___
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
viktoriya VirtualDomain[26100]: ERROR: Configuration
file /etc/libvirt/qemu/evelyn.powercraft.nl.xml does not exist or is not
readable.
How should I use the VirtualDomain RA?
Thanks in advance,
Kind regards,
Jelle de Jong
___
Pacemaker mailing list
/Using_Pacemaker_with_Lustre
crm configure help location
crm ra info ocf:ping
That should give you a jup start.
You may need to increase the corosync token.
Kind regards,
Jelle de Jong
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http
regards,
Jelle de Jong
___
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
Dear Andrew,
On 18-04-11 09:05, Andrew Beekhof wrote:
On Fri, Apr 15, 2011 at 9:54 PM, Jelle de Jong
jelledej...@powercraft.nl wrote:
How should I change my configuration[1] so it understands that it can
not run resources on the third node (machine ebony) but should use it
for quorum only
, but then
all damage is already made...
I must be doing something _terrible_ wrong since I can't believe a
pacemaker/corosync cluster shouldn't be able to survive a network glitch
(short network failures) without all kind of split brains and losing the
node.
Thanks in advance,
Kind regards,
Jelle de
) but should use it
for quorum only?
[1] http://pastebin.com/wYjqpDvk
I tried changing the corosync.conf and commented out the service
section, but now pacemaker does not detect the third node at all, and
tests show it is also is not used for quorum.
Thanks in advance,
Kind regards,
Jelle de Jong
:
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ lrmd: \[[0-9]+\]: WARN:
G_SIG_dispatch: Dispatch function for SIGCHLD was delayed [0-9]+ ms \(
100 ms\) before being called \(GSource: 0x[0-9]+f20\)$
Thanks in advance,
Kind regards,
Jelle de Jong
___
Pacemaker
the Cluster_from_Scratch.pdf,
Pacemaker-1.0-Pacemaker_Explained-en-US and ha-iscsi.pdf.
Thanks in advance,
With kind regards,
Jelle de Jong
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
20 matches
Mail list logo
