Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
For a while now, I've been noticing that when starting the secondary,
the script is just stuck waiting. I don't know what it's waiting for,
though. As you can see on the primary, it's been connected, synced,
and up-to-date...
On the secondary:
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 120 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 'logs'; 0 sec -> wait forever)
To abort waiting enter 'yes' [ 60]:
And for a number of seconds already, the primary has been reporting:
0: cs:Connected st:Primary/Secondary ds:UpToDate/UpToDate C r---
...
1: cs:Connected st:Primary/Secondary ds:UpToDate/UpToDate C r---
...
2: cs:Connected st:Primary/Secondary ds:UpToDate/UpToDate C r---
...
3: cs:Connected st:Primary/Secondary ds:UpToDate/UpToDate C r---
...
4: cs:Connected st:Primary/Secondary ds:UpToDate/UpToDate C r---
...
5: cs:Connected st:Primary/Secondary ds:UpToDate/UpToDate C r---
...
6: cs:Connected st:Primary/Secondary ds:UpToDate/UpToDate C r---
...
7: cs:Connected st:Primary/Secondary ds:UpToDate/UpToDate C r---
--
Maurice Volaski, mvolaski at aecom.yu.edu
Computing Support, Rose F. Kennedy Center
Albert Einstein College of Medicine of Yeshiva University