[ClusterLabs] Not all bind address belong to the same IP family - corosync fails

lejeczek peljasz at yahoo.co.uk
Fri May 10 07:38:22 EDT 2019


hi guys,

I have a node which fails to start, but only at sys boot time to make it
more curious, like this:

....

corosync[28752]:  [MAIN  ] parse error in config: Not all bind address
belong to the same IP family
May 10 12:33:45 rider.privatecorosync[28752]:  [MAIN  ] Corosync Cluster
Engine exiting with status 8 at main.c:1406.
May 10 12:33:45 rider.privatecorosync[28530]: Starting Corosync Cluster
Engine (corosync): [FAILED]
May 10 12:33:45 rider.privatesystemd[1]: corosync.service: control
process exited, code=exited status=1
May 10 12:33:45 rider.privatesystemd[1]: Failed to start Corosync
Cluster Engine.
May 10 12:33:45 rider.privatesystemd[1]: Dependency failed for Pacemaker
High Availability Cluster Manager.
May 10 12:33:45 rider.privatesystemd[1]: Job pacemaker.service/start
failed with result 'dependency'.
May 10 12:33:45 rider.privatesystemd[1]: Unit corosync.service entered
failed state.
May 10 12:33:45 rider.privatesystemd[1]: corosync.service failed.

Would anybody care to suggest how to investigate & fix this?

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/20190510/2acf5a75/attachment.bin>


More information about the Users mailing list