corosync-qdevice error "Unhandled error when reading from server" after setting the system crypto policy to FUTURE

Solution Unverified - Updated -

Issue

  • My cluster nodes are not able to connect with the quorum device after setting the crypto policy to FUTURE and the following errors constantly appear in the log files:

    Nov 13 15:01:47 node1 corosync-qdevice[1014]: Unhandled error when reading from server. Disconnecting from server
    Nov 13 15:01:49 node1 corosync-qdevice[1014]: Unhandled error when reading from server. Disconnecting from server
    Nov 13 15:01:51 node1 corosync-qdevice[1014]: Unhandled error when reading from server. Disconnecting from server
    Nov 13 15:01:53 node1 corosync-qdevice[1014]: Unhandled error when reading from server. Disconnecting from server
    
  • Configuring and starting corosync-qnetd is failed after setting the crypto policy to FUTURE.

    Nov  4 08:21:36 qdevice systemd[1]: Starting Corosync Qdevice Network daemon...
    Nov  4 08:21:36 qdevice corosync-qnetd[37136]: NSS error (-5977): Failure to load dynamic library
    Nov  4 08:21:36 qdevice systemd[1]: corosync-qnetd.service: Main process exited, code=exited, status=1/FAILURE
    

Environment

  • Red Hat Enterprise Linux 9
  • Red Hat Enterprise Linux 8
  • High Availability or Resilient Storage add-ons
  • Pacemaker cluster with quorum device
  • Crypto policies have been set to FUTURE

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