I'm running through the following guide: http://pve.proxmox.com/wiki/DRBD and it all makes sense and is understandable. I'm hitting an issue when I am getting to the Prepare drbd configuration section.
I've followed through and setup the
file as well as the
file.
When I try to start DRBD I get what appear to be errors output below
This happens on both nodes. My two nodes are called prox01 & prox02 dns is setup so if I nslookup prox01 or prox02 they resolve to the machine IP address which are 192.168.1.10 (prox01) & 192.168.1.11 (prox02).
The two DRBD nics that are linked are on 10.0.1.10 (prox01) & 10.0.1.11 (prox02)
My config file is below. I'm not quite sure what I am missing here. I did notice the shared secret option which at the moment says my secret should this be something specific to my setup and if so how do I find this?
my /etc/hosts file on each node looks like the following:
Any help would be great.
I've followed through and setup the
Code:
/etc/drbd.d/global_common.conf
Code:
/etc/drbd.d/r0.resWhen I try to start DRBD I get what appear to be errors output below
Code:
root@prox01:/etc/drbd.d# /etc/init.d/drbd start
Starting DRBD resources:[
r0
no suitable meta data found :(
Command '/sbin/drbdmeta 0 v08 /dev/sdb1 internal check-resize' terminated with exit code 255
drbdadm check-resize r0: exited with code 255
d(r0) 0: Failure: (119) No valid meta-data signature found.
==> Use 'drbdadm create-md res' to initialize meta-data area. <==
[r0] cmd /sbin/drbdsetup 0 disk /dev/sdb1 /dev/sdb1 internal --set-defaults --create-device --no-disk-barrier --no-disk-flushes failed - continuing!
s(r0) n(r0) ]..........
***************************************************************
DRBD's startup script waits for the peer node(s) to appear.
- In case this node was already a degraded cluster before the
reboot the timeout is 60 seconds. [degr-wfc-timeout]
- If the peer was available before the reboot the timeout will
expire after 0 seconds. [wfc-timeout]
(These values are for resource 'r0'; 0 sec -> wait forever)
To abort waiting enter 'yes' [ 23]:
To abort waiting enter 'yes' [ 27]:yes
0: State change failed: (-2) Need access to UpToDate data
Command '/sbin/drbdsetup 0 primary' terminated with exit code 17
0: State change failed: (-2) Need access to UpToDate data
Command '/sbin/drbdsetup 0 primary' terminated with exit code 17
0: State change failed: (-2) Need access to UpToDate data
Command '/sbin/drbdsetup 0 primary' terminated with exit code 17
0: State change failed: (-2) Need access to UpToDate data
Command '/sbin/drbdsetup 0 primary' terminated with exit code 17
0: State change failed: (-2) Need access to UpToDate data
Command '/sbin/drbdsetup 0 primary' terminated with exit code 17
.
root@prox01:/etc/drbd.d#This happens on both nodes. My two nodes are called prox01 & prox02 dns is setup so if I nslookup prox01 or prox02 they resolve to the machine IP address which are 192.168.1.10 (prox01) & 192.168.1.11 (prox02).
The two DRBD nics that are linked are on 10.0.1.10 (prox01) & 10.0.1.11 (prox02)
My config file is below. I'm not quite sure what I am missing here. I did notice the shared secret option which at the moment says my secret should this be something specific to my setup and if so how do I find this?
Code:
resource r0 {
protocol C;
startup {
wfc-timeout 0; # non-zero wfc-timeout can be dangerous (http://forum.proxmox.com/threads/3465-Is-it-safe-to-use-wfc-timeout-in-DRBD-configuration)
degr-wfc-timeout 60;
become-primary-on both;
}
net {
cram-hmac-alg sha1;
shared-secret "my-secret";
allow-two-primaries;
after-sb-0pri discard-zero-changes;
after-sb-1pri discard-secondary;
after-sb-2pri disconnect;
#data-integrity-alg crc32c; # has to be enabled only for test and disabled for production use (check man drbd.conf, section "NOTES ON DATA INTEGRITY")
}
on prox01 {
device /dev/drbd0;
disk /dev/sdb1;
address 10.0.1.10:7788;
meta-disk internal;
}
on prox02 {
device /dev/drbd0;
disk /dev/sdb1;
address 10.0.1.11:7788;
meta-disk internal;
}
disk {
# no-disk-barrier and no-disk-flushes should be applied only to systems with non-volatile (battery backed) controller caches.
# Follow links for more information:
# http://www.drbd.org/users-guide-8.3/s-throughput-tuning.html#s-tune-disable-barriers
# http://www.drbd.org/users-guide/s-throughput-tuning.html#s-tune-disable-barriers
no-disk-barrier;
no-disk-flushes;
}
}my /etc/hosts file on each node looks like the following:
Code:
127.0.0.1 localhost.localdomain localhost
192.168.1.10 prox01.fourthfloorsolutions.com prox01 pvelocalhost
192.168.1.11 prox02.fourthfloorsolutions.com prox02 pvelocalhost
# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhostsAny help would be great.