No subject

disabled. However, after starting the drbd, the status is stuck in
Connecting, and on the logs I can see the following: "prepare net:
drbd0:failed(new-peer:10)"

[root at drbd1 ~]# drbdadm status
drbd0 role:Secondary
  disk:Inconsistent
  drbd2 connection:Connecting

[root at drbd1 ~]# journalctl -u drbd
-- Logs begin at Wed 2018-08-15 20:37:05 UTC, end at Wed 2018-08-15
21:01:01 UTC. --
Aug 15 20:37:15 drbd1.novalocal systemd[1]: Starting DRBD -- please
disable. Unless you are NOT using a cluster manager....
Aug 15 20:37:16 drbd1.novalocal drbd[969]: Starting DRBD resources: [
Aug 15 20:37:16 drbd1.novalocal drbd[969]: create res: drbd0
Aug 15 20:37:16 drbd1.novalocal drbd[969]: prepare disk: drbd0
Aug 15 20:37:16 drbd1.novalocal drbd[969]: prepare net:
drbd0:failed(new-peer:10)
Aug 15 20:37:16 drbd1.novalocal drbd[969]: (null): [skipped:drbd0]
Aug 15 20:37:16 drbd1.novalocal drbd[969]: adjust disk: [skipped:drbd0]
Aug 15 20:37:16 drbd1.novalocal drbd[969]: attempt to connect: [skipped:drbd0]
Aug 15 20:37:16 drbd1.novalocal drbd[969]: ]
Aug 15 20:37:16 drbd1.novalocal drbd[969]: WARN: stdin/stdout is not a
TTY; using /dev/consoleopen('/dev/console, O_RDONLY): Permission
Aug 15 20:37:16 drbd1.novalocal drbd[969]: WARN: stdin/stdout is not a
TTY; using /dev/consoledrbdadm: Unknown command 'sh-b-pri'
Aug 15 20:37:16 drbd1.novalocal drbd[969]: .
Aug 15 20:37:16 drbd1.novalocal systemd[1]: Started DRBD -- please
disable. Unless you are NOT using a cluster manager..

Any clue what I am doing wrong?

Regards,
Adrian