Changing the totem token timeout value of a cluster is not making any effect and node is getting fenced before the set timeout value

Solution Verified - Updated -


  • A node in the cluster is getting fenced with "[TOTEM ] A processor failed, forming new configuration" messages. This issue continued even after updating the totem token timeout to higher value in corosync.conf file and propagating it to rest of the nodes with pcs cluster sync command.
  • Changes in token attribute value of the corosync configuration are not getting reflected in cluster.


  • Red Hat Enterprise Linux Server release 6,7 with High Availability Add-On
  • pacemaker
  • corosync

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In