On 6/06/2016 22:16, Roland Kammerer wrote:
On Mon, Jun 06, 2016 at 09:24:00PM +1000, Adam Goryachev wrote:
Still looks like the same problem, starting from a completely clean
Hi,
sorry, it also requires a change in the main repo which was not pushed
public yet.
git clone --recursive git://git.linbit.com/drbd-9.0.git
cd drbd-9.0/
make -j
Thanks so much, that now works, and so I reach the next problem, it
seems my satellite node can't connect to any other nodes...
This is the satellite node:
root@xen6:~# drbdmanage list-nodes
No nodes defined
This is one of the other nodes:
san2:~# drbdmanage list-nodes
+------------------------------------------------------------------------------------------------+
| Name | Pool Size | Pool Free |
| State |
|------------------------------------------------------------------------------------------------|
| castle | 5403308 | 4017368 |
| ok |
| san2 | 3777040 | 2432060 |
| ok |
| san3 | 1830932 | 1821384 |
| ok |
| san5 | 2764172 | 2745084 |
| ok |
| xen6 | 0 | 0 | |
satellite node, no storage |
+------------------------------------------------------------------------------------------------+
san2:~# drbdadm status
.drbdctrl role:Secondary
volume:0 disk:UpToDate
volume:1 disk:UpToDate
castle role:Secondary
volume:0 peer-disk:UpToDate
volume:1 peer-disk:UpToDate
san3 role:Secondary
volume:0 peer-disk:UpToDate
volume:1 peer-disk:UpToDate
san5 role:Secondary
volume:0 peer-disk:UpToDate
volume:1 peer-disk:UpToDate
filesrv role:Secondary
disk:UpToDate
castle role:Secondary
peer-disk:UpToDate
xen6 connection:Connecting
So, what is missing/wrong now? I would think xen6 machine needs to know
it should connect to the other machines, but there is no config or
storage to tell it to do that. Where/how do I configure this?
san2:~# drbdmanage howto-join xen6
Error: Node "xen6" is a satellite node!
Just make sure drbdmanaged is running on xen6
Operation completed successfully
root@xen6:~# ps axf|grep drbd
2976 ? S< 0:00 \_ [drbd-reissue]
3013 pts/0 S+ 0:00 | \_ grep drbd
1052 ? Sl 0:04 /usr/bin/python
/usr/bin/dbus-drbdmanaged-service
1068 ? S 0:00 \_ drbdsetup events2 all
Looks like drbdmanaged is running....
root@xen6:~# dmesg|grep drbd
[ 2714.519639] drbd: initialized. Version: 9.0.2-1 (api:2/proto:86-111)
[ 2714.519642] drbd: GIT-hash: 14d2eead95f99a7de1c0b3e3f335a30b8d486bcb
build by root@xen6, 2016-06-06 22:20:37
[ 2714.519644] drbd: registered as block device major 147
[89849.902882] drbd: module cleanup done.
[89863.813918] drbd: initialized. Version: 9.0.2-1 (api:2/proto:86-111)
[89863.813921] drbd: GIT-hash: 14d2eead95f99a7de1c0b3e3f335a30b8d486bcb
build by root@xen6, 2016-06-06 22:20:37
[89863.813923] drbd: registered as block device major 147
Following the advice I usually hand out, "have you rebooted" I
re-started the xen6 machine and get this:
root@xen6:~# drbdmanage list-nodes
ERROR:dbus.proxies:Introspect error on :1.3:/interface:
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply:
Message recipient disconnected from message bus without replying
Error: Cannot connect to the drbdmanaged process using DBus
The DBus subsystem returned the following error description:
org.freedesktop.DBus.Error.ServiceUnknown: The name :1.3 was not
provided by any .service files
root@xen6:~# cat /proc/drbd
version: 9.0.2-1 (api:2/proto:86-111)
GIT-hash: 14d2eead95f99a7de1c0b3e3f335a30b8d486bcb build by root@xen6,
2016-06-06 22:20:37
Transports (api:14):
root@xen6:~# ps axf| grep drbd
1083 ? S< 0:00 \_ [drbd-reissue]
1087 pts/0 S+ 0:00 \_ grep drbd
root@xen6:~# systemctl start drbd.service
root@xen6:~# systemctl status drbd.service
● drbd.service - DRBD -- please disable. Unless you are NOT using a
cluster manager.
Loaded: loaded (/lib/systemd/system/drbd.service; disabled; vendor
preset: enabled)
Active: active (exited) since Tue 2016-06-07 23:43:23 AEST; 15s ago
Process: 1090 ExecStart=/lib/drbd/drbd start (code=exited,
status=0/SUCCESS)
Main PID: 1090 (code=exited, status=0/SUCCESS)
Jun 07 23:43:23 xen6 systemd[1]: Starting DRBD -- please disable. Unless
you are NOT using a cluster manager....
Jun 07 23:43:23 xen6 drbd[1090]: Starting DRBD resources:no resources
defined!
Jun 07 23:43:23 xen6 drbd[1090]: no resources defined!
Jun 07 23:43:23 xen6 drbd[1090]: WARN: stdin/stdout is not a TTY; using
/dev/consoleWARN: stdin/stdout is not a TTY; using /dev/consoledrbdadm:
Unknown command 'sh-b-pri'
Jun 07 23:43:23 xen6 drbd[1090]: .
Jun 07 23:43:23 xen6 systemd[1]: Started DRBD -- please disable. Unless
you are NOT using a cluster manager..
Would appreciate suggestions or advice from here please.
Regards,
Adam
_______________________________________________
drbd-user mailing list
[email protected]
http://lists.linbit.com/mailman/listinfo/drbd-user
