Corosync reporting interface 127.0.0.1 FAULTY

This document (7024348) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise High Availability Extension 12

SUSE Linux Enterprise High Availability Extension 15

Situation

Corosync is reporting the following error in systemd journal:

Dec 18 10:26:25 ha2 corosync[1698]: [TOTEM ] Marking ringid 0 interface 127.0.0.1 FAULTY

A similar message can be seen in corosync-cfgtool with -s option:

RING ID 0
id = 127.0.0.1
status = Marking ringid 0 interface 127.0.0.1 FAULTY
RING ID 1
id = 192.168.77.12
status = ring 1 active with no faults

Resolution

To fix this issue, corosync needs to be restarted. To do this, run:

systemctl stop pacemaker
systemctl start pacemaker

The above command will stop pacemaker & corosync. Running the above commands will also move all resources from this node to the 2nd node. Depending on business/application, downtime might be needed.

Cause

This can be happen if corosync was configured with a specific IP address but that IP address was not set on any ethernet card. It can also happen if, during bootup, corosync started when the network was not fully ready.

Some errors might look like:

Dec 18 10:25:48 linux-311j kernel: 8139cp 0000:00:04.0 eth1: link down
Dec 18 10:25:48 linux-311j kernel: IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Dec 18 10:26:18 ha2 wicked[1027]: eth1 setup-in-progress

Additional Information

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.