Problem with Corosync Promox 7.1.7

gabrielwz

New Member
May 12, 2022
1
0
1
Hello,
I have a promox cluster with several computers and it is happening to me that once a day corosync raises the load of the computers to 100% and it is not possible to login through the web interface.

At the moment I fix it by stopping corosync on all servers for a moment and then starting them.

Could you help me identify what it could be? Is there a configuration that I'm missing? .

Logs of error:

May 11 03:24:19 cloud corosync[731085]: [TOTEM ] A processor failed, forming new configuration: token timed out (9500ms), waiting 11400ms for consensus.
May 11 04:09:41 cloud corosync[731085]: [TOTEM ] A processor failed, forming new configuration: token timed out (9500ms), waiting 11400ms for consensus.
May 11 04:53:56 cloud corosync[731085]: [TOTEM ] A processor failed, forming new configuration: token timed out (9500ms), waiting 11400ms for consensus.
May 11 13:28:33 cloud corosync[731085]: [TOTEM ] A processor failed, forming new configuration: token timed out (9500ms), waiting 11400ms for consensus.
May 11 15:15:43 cloud corosync[731085]: [TOTEM ] A processor failed, forming new configuration: token timed out (9500ms), waiting 11400ms for consensus.
May 11 15:25:23 cloud corosync[731085]: [TOTEM ] A processor failed, forming new configuration: token timed out (9500ms), waiting 11400ms for consensus.
May 11 15:33:18 cloud corosync[731085]: [TOTEM ] A processor failed, forming new configuration: token timed out (9500ms), waiting 11400ms for consensus.
May 12 00:12:01 cloud corosync[731085]: [TOTEM ] A processor failed, forming new configuration: token timed out (9500ms), waiting 11400ms for consensus.
May 12 00:35:52 cloud corosync[731085]: [TOTEM ] A processor failed, forming new configuration: token timed out (9500ms), waiting 11400ms for consensus.
May 12 00:39:34 cloud corosync[731085]: [TOTEM ] A processor failed, forming new configuration: token timed out (9500ms), waiting 11400ms for consensus.
May 12 02:32:30 cloud corosync[731085]: [TOTEM ] A processor failed, forming new configuration: token timed out (9500ms), waiting 11400ms for consensus.
May 12 09:07:28 cloud corosync[91617]: [TOTEM ] A processor failed, forming new configuration: token timed out (9500ms), waiting 11400ms for consensus.
 
that's already a symptom of something going wrong, you'd need to go further back in the logs to find the actual cause..
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!