11.09.2014 05:57, Norbert Kiam Maclang wrote:
Is this something to do with quorum? But I already set
You'd need to configure fencing at the drbd resources level.
http://www.drbd.org/users-guide-emb/s-pacemaker-fencing.html#s-pacemaker-fencing-cib
property no-quorum-policy=ignore \
Thank you for spending time looking at my problem, really appreciate it.
Additional information on my problem
Before doing a restart on the primary node, tcpdump shows (exchange is
good):
IP node01.55010 node02.5405: UDP, length 87
IP node01.5405 node02.5405: UDP, length 74
IP node02.5405
On 11 Sep 2014, at 6:51 pm, Norbert Kiam Maclang
norbert.kiam.macl...@gmail.com wrote:
Thank you for spending time looking at my problem, really appreciate it.
Additional information on my problem
Before doing a restart on the primary node, tcpdump shows (exchange is good):
IP
Thank you Vladislav.
I have configured resource level fencing on drbd and removed wfc-timeout
and defr-wfc-timeout (is this required?). My drbd configuration is now:
resource pg {
device /dev/drbd0;
disk /dev/vdb;
meta-disk internal;
disk {
fencing resource-only;
on-io-error
Hi Kiran,
the --debug flag makes pcs print info about all runned external commands
and their output. Pcs has to read the CIB first in order to update it so
your xmlfile contains the original CIB at the beginning. You need to
find the updated CIB xml in the file (it starts on the line that
Hi,
After adding resource level fencing on drbd, I still ended up having
problems with timeouts on drbd. Is there a recommended settings for this? I
followed what is written in the drbd documentation -
http://www.drbd.org/users-guide-emb/s-pacemaker-crm-drbd-backed-service.html
, Another thing I
12.09.2014 05:00, Norbert Kiam Maclang wrote:
Hi,
After adding resource level fencing on drbd, I still ended up having
problems with timeouts on drbd. Is there a recommended settings for
this? I followed what is written in the drbd documentation -
