Hi,
Actually you were right. one of the ip-adresses were wrong in r0.res file I
have corrected this, but still I can't promote any of the nodes to primary.
output from drbdadm dump
[root@tdprodrepo01 ~]# drbdadm dump
# /etc/drbd.conf
common {
disk {
on-io-error dettach;
fencing resource-only;
}
handlers {
pri-on-incon-degr "/usr/lib/drbd/notify-pri-on-incon-degr.sh;
/usr/lib/drbd/notify-emergency-reboot.sh; echo b > /proc/sysrq-trigger ;
reboot -f";
pri-lost-after-sb "/usr/lib/drbd/notify-pri-lost-after-sb.sh;
/usr/lib/drbd/notify-emergency-reboot.sh; echo b > /proc/sysrq-trigger ;
reboot -f";
local-io-error "/usr/lib/drbd/notify-io-error.sh;
/usr/lib/drbd/notify-emergency-shutdown.sh; echo o > /proc/sysrq-trigger ;
halt -f";
fence-peer /usr/lib/drbd/crm-fence-peer.sh;
after-resync-target /usr/lib/drbd/crm-unfence-peer.sh;
}
}
# resource r0 on tdprodrepo01: not ignored, not stacked
# defined at /etc/drbd.d/r0.res:1
resource r0 {
on tdprodrepo01 {
volume 0 {
device /dev/drbd0 minor 0;
disk /dev/vg_drbd/lv_drbd01;
meta-disk internal;
}
address ipv4 xxx.22.11.61:7788;
}
on tdprodrepo02 {
volume 0 {
device /dev/drbd0 minor 0;
disk /dev/vg_drbd/lv_drbd01;
meta-disk internal;
}
address ipv4 xxx.22.11.62:7788;
}
}
and the other machine
[root@tdprodrepo02 corosync]# drbdadm dump
# /etc/drbd.conf
common {
disk {
on-io-error dettach;
fencing resource-only;
}
handlers {
pri-on-incon-degr "/usr/lib/drbd/notify-pri-on-incon-degr.sh;
/usr/lib/drbd/notify-emergency-reboot.sh; echo b > /proc/sysrq-trigger ;
reboot -f";
pri-lost-after-sb "/usr/lib/drbd/notify-pri-lost-after-sb.sh;
/usr/lib/drbd/notify-emergency-reboot.sh; echo b > /proc/sysrq-trigger ;
reboot -f";
local-io-error "/usr/lib/drbd/notify-io-error.sh;
/usr/lib/drbd/notify-emergency-shutdown.sh; echo o > /proc/sysrq-trigger ;
halt -f";
fence-peer /usr/lib/drbd/crm-fence-peer.sh;
after-resync-target /usr/lib/drbd/crm-unfence-peer.sh;
}
}
# resource r0 on tdprodrepo02: not ignored, not stacked
# defined at /etc/drbd.d/r0.res:1
resource r0 {
on tdprodrepo01 {
volume 0 {
device /dev/drbd0 minor 0;
disk /dev/vg_drbd/lv_drbd01;
meta-disk internal;
}
address ipv4 xxx.22.11.61:7788;
}
on tdprodrepo02 {
volume 0 {
device /dev/drbd0 minor 0;
disk /dev/vg_drbd/lv_drbd01;
meta-disk internal;
}
address ipv4 xxx.22.11.62:7788;
}
}
[root@tdprodrepo02 corosync]# cat /proc/drbd
version: 8.4.1 (api:1/proto:86-100)
GIT-hash: 91b4c048c1a0e06777b5f65d312b38d47abaea80 build by gardner@,
2012-08-25 00:57:01
0: cs:Connected ro:Secondary/Secondary ds:Diskless/Diskless C r-----
ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b oos:0
(Same on both machines)
Any futher ideas ? or do you think I should start from scratch and build
up my cluster ?
kind regards
/Fredrik
On Thu, Aug 15, 2013 at 1:48 PM, Jakob Curdes <[email protected]> wrote:
> Am 15.08.2013 13:25, schrieb Fredrik Hudner:
>
>>
>> So if you have any other suggestions how I can come out of this situation,
>> it would be much appreciated
>>
>> Are you sure the machines see each other? "diskless" for the remote side
> sounds not too convinving...
> JC
> ______________________________**_________________
> Linux-HA mailing list
> [email protected]
> http://lists.linux-ha.org/**mailman/listinfo/linux-ha<http://lists.linux-ha.org/mailman/listinfo/linux-ha>
> See also:
> http://linux-ha.org/**ReportingProblems<http://linux-ha.org/ReportingProblems>
>
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
