Stopping the pcsd.service causes pacemaker to fail in updating token value.

Solution Verified - Updated -

Issue

  • In some situations, token value needs to be updated for some reasons in Pacemaker cluster, but pcs cluster sync fails with error below after setting new token value in /etc/corosync.conf(where nodeA represents one of Pacemaker node names).
Error: Unable to set corosync config: Unable to connect to nodeA, try setting higher timeout in --request-timeout option (Failed connect to nodeA:2224; Connection refused)

Environment

  • Red Hat Enterprise Linux 7/8/9
  • Pacemaker
  • pcsd.service

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