Adding a new node changes corosync token timeout

Solution In Progress - Updated -


  • After adding new corosync nodes, the runtime totem.token for pacemaker cluster gets increased.

  • It is expected to be the token value as defined in totem {} directive of corosync configuration file /etc/corosync/corosync.conf:

[root@node2 ~]# cat /etc/corosync/corosync.conf
totem {
    version: 2
    cluster_name: mycluster
    secauth: off
    transport: udpu
    token: 5000

However, the 'runtime.config.totem.token' value of from corosync-cmapctl doesn't seem to related to 'totem.token' specified in the corosync configuration:

[root@node2 ~]# corosync-cmapctl | grep totem.token
runtime.config.totem.token (u32) = 5650
totem.token (u32) = 5000


  • Red Hat Enterprise Linux 7 with the High Availability Add-On
  • Red Hat Enterprise Linux 8 with the High Availability Add-On

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content