<div dir="ltr"><p style="margin:0px 0px 1em;padding:0px;border:0px;font-size:15px;clear:both;font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;line-height:19.5px">I have a newly configured DRBD-Cluster 8.4.5 on 2 VM running ubuntu 14.04, following this example: <a href="http://geekpeek.net/configure-drbd-ubuntu/" rel="nofollow" style="margin:0px;padding:0px;border-width:0px 0px 1px;border-bottom-style:dotted;border-bottom-color:rgb(69,69,69);text-decoration:none;color:rgb(12,101,165)">http://geekpeek.net/configure-drbd-ubuntu/</a></p><p style="margin:0px 0px 1em;padding:0px;border:0px;font-size:15px;clear:both;font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;line-height:19.5px">Unfortunatelly I can not start the service. It seems to be either a network setup problem or maybe a incompatibility issue with 8.4.x on ubuntu 14.04</p><p style="margin:0px 0px 1em;padding:0px;border:0px;font-size:15px;clear:both;font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;line-height:19.5px">This is the msg I get:</p><pre style="margin-top:0px;padding:5px;border:0px;font-size:13px;overflow:auto;width:auto;max-height:600px;font-family:Consolas,Menlo,Monaco,'Lucida Console','Liberation Mono','DejaVu Sans Mono','Bitstream Vera Sans Mono','Courier New',monospace,sans-serif;word-wrap:normal;background-color:rgb(238,238,238)"><code style="margin:0px;padding:0px;border:0px;font-family:Consolas,Menlo,Monaco,'Lucida Console','Liberation Mono','DejaVu Sans Mono','Bitstream Vera Sans Mono','Courier New',monospace,sans-serif;white-space:inherit">sudo /etc/init.d/drbd start
* Starting DRBD resources [
]
<1>bind(s->s_fd, (struct sockaddr*) &s->s_local, sizeof(s->s_local)) failed: -1 No such file or directory
<1>error creating netlink socket
..........
***************************************************************
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 30 seconds. [degr-wfc-timeout]
- If the peer was available before the reboot the timeout will
expire after 30 seconds. [wfc-timeout]
(These values are for resource 'disk1'; 0 sec -> wait forever)
To abort waiting enter 'yes' [ 120]:No response from the DRBD driver! Is the module loaded?
</code></pre><p style="margin:0px 0px 1em;padding:0px;border:0px;font-size:15px;clear:both;font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;line-height:19.5px">The config file</p><pre style="margin-top:0px;padding:5px;border:0px;font-size:13px;overflow:auto;width:auto;max-height:600px;font-family:Consolas,Menlo,Monaco,'Lucida Console','Liberation Mono','DejaVu Sans Mono','Bitstream Vera Sans Mono','Courier New',monospace,sans-serif;word-wrap:normal;background-color:rgb(238,238,238)"><code style="margin:0px;padding:0px;border:0px;font-family:Consolas,Menlo,Monaco,'Lucida Console','Liberation Mono','DejaVu Sans Mono','Bitstream Vera Sans Mono','Courier New',monospace,sans-serif;white-space:inherit">resource disk1
{
startup {
wfc-timeout 30;
outdated-wfc-timeout 20;
degr-wfc-timeout 30;
}
net {
cram-hmac-alg sha1;
shared-secret sync_disk;
}
syncer {
rate 100M;
verify-alg sha1;
}
on node1 { # Node1 defined
device /dev/drbd0;
disk /dev/sdb; # Device to use with DRBD
address <a href="http://192.168.57.120:7789">192.168.57.120:7789</a>; # IP Address and port of Node1
meta-disk internal;
}
on node2 { # Node2 defined
device /dev/drbd0;
disk /dev/sdb; # Device to use with DRBD
address <a href="http://192.168.57.130:7789">192.168.57.130:7789</a>; # IP Address and port of Node2
meta-disk internal;
}
}
</code></pre><p style="margin:0px 0px 1em;padding:0px;border:0px;font-size:15px;clear:both;font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;line-height:19.5px">There is little to nothing to find on the net on how to solve this. Any help is greatly appreciated.</p></div>