[ClusterLabs] redundant ring and corosync makes/sees it as loopback??

[lejeczek]

hi everyone

My cluster faulted my secondary ring today and on one node I found this:

Printing ring status.
Local node ID 3
RING ID 0
    id    = 10.5.8.65
    status    = ring 0 active with no faults
RING ID 1
    id    = 127.0.0.1
    status    = Marking ringid 1 interface 127.0.0.1 FAULTY

How the hell loopback address got there?

I did: systemctl restart corosync and all went back to "okey"

many thanks, L.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: pEpkey.asc
Type: application/pgp-keys
Size: 1757 bytes
Desc: not available
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20190228/e204629b/attachment.bin>