Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
I'm freaking out!.
In my previous message I sent the syslog about drbdmanaged startup at
boot time, hoping for help.
Moreover today, starting servers, not only I had to make drbdmanage
restart but after done it , checking drbdsetup status I found a
problem on vm-104:
On PVE1:
root at mpve1:~# drbdsetup status
.drbdctrl role:Primary
volume:0 disk:UpToDate
volume:1 disk:UpToDate
mpve2 role:Secondary
volume:0 peer-disk:UpToDate
volume:1 peer-disk:UpToDate
mpve3 role:Secondary
volume:0 peer-disk:UpToDate
volume:1 peer-disk:UpToDate
vm-100-disk-1 role:Secondary
disk:UpToDate
mpve2 role:Secondary
peer-disk:UpToDate
mpve3 role:Secondary
peer-disk:UpToDate
vm-101-disk-1 role:Secondary
disk:UpToDate
mpve2 role:Secondary
peer-disk:UpToDate
mpve3 role:Secondary
peer-disk:UpToDate
vm-102-disk-1 role:Secondary
disk:UpToDate
mpve2 role:Secondary
peer-disk:UpToDate
mpve3 role:Secondary
peer-disk:UpToDate
vm-103-disk-1 role:Secondary
disk:UpToDate
mpve2 role:Secondary
peer-disk:UpToDate
mpve3 role:Secondary
peer-disk:UpToDate
vm-104-disk-1 role:Primary
disk:UpToDate
mpve2 connection:Connecting
mpve3 connection:StandAlone
vm-105-disk-1 role:Secondary
disk:UpToDate
mpve2 role:Secondary
peer-disk:UpToDate
mpve3 role:Secondary
peer-disk:UpToDate
on PVE2:
vm-104-disk-1 role:Secondary
disk:UpToDate
mpve1 connection:StandAlone
mpve3 connection:StandAlone
(other results omitted, they are all UpToDate)
On PVE3:
vm-104-disk-1 role:Secondary
disk:UpToDate
mpve1 connection:Connecting
mpve2 connection:Connecting
what does it mean? what am I to do?
Thank's for help,
Michele