Corosync Service Fails to Start on Proxmox Cluster Node

[4rarius]

Hello Proxmox Community,

I'm currently facing an issue with my Proxmox cluster, using raspberry pi 4s, specifically with the Corosync service failing to start on one of my nodes. Here are the details and steps I've taken so far:

Cluster Configuration:

• Node 1: 192.168.1.101
• Node 2: 192.168.1.102
• Cluster Name: rpi4s

Issue:

• The Corosync service fails to start on Node 2, with error messages indicating it was killed by a signal. The specific errors from the logs include "Cannot initialize CMAP service" and "Could not initialize corosync configuration API error 2."

Steps Taken:

1. Checked Proxmox Services:
   • Verified that pve-cluster, pvedaemon, and pveproxy services are running.
   • Encountered critical initialization failures for Corosync.
2. Reviewed and Synchronized Configuration Files:
   • Ensured corosync.conf is identical on both nodes.
   • Confirmed authkey is identical and has correct permissions (root:root and chmod 600).
3. Network Configuration:
   • Verified network interfaces and ensured no IP conflicts.
   • Confirmed both nodes can ping each other.
4. Examined Logs:
   • Detailed logs from journalctl and /var/log/corosync/corosync.log indicate fatal signals and initialization failures.
5. Tried Alternative Methods:
   • Temporarily changed directory permissions to allow authkey copying.
   • Enabled debugging in corosync.conf.

Despite these steps, the Corosync service on Node 2 consistently fails to start. I would greatly appreciate any insights or suggestions from the community on how to resolve this issue.

Thank you in advance for your help!

Best regards,