What does the message "waiting for quorum device Qdevice poll" mean?

Solution Verified - Updated -

Issue

  • The fence device is not triggered after a node lost communication in the cluster and displays the message "waiting for quorum device Qdevice poll (but maximum for 30000 ms)".

  • The corosync-qdevice is waiting 30 seconds to recalculate the votes when a node is lost in order to trigger fencing.

    Sep 16 18:17:08 node2 corosync[1182]:  [TOTEM ] A processor failed, forming new configuration.
    Sep 16 18:17:14 node2 corosync[1182]:  [VOTEQ ] waiting for quorum device Qdevice poll (but maximum for 30000 ms)
    Sep 16 18:17:14 node2 corosync[1182]:  [TOTEM ] A new membership (192.168.122.12:10968) was formed. Members left: 1
    Sep 16 18:17:14 node2 corosync[1182]:  [TOTEM ] Failed to receive the leave message. failed: 1
    Sep 16 18:17:14 node2 corosync[1182]:  [CPG   ] downlist left_list: 1 received
    Sep 16 18:17:14 node2 attrd[2531]:   notice: Node node1 state is now lost
    Sep 16 18:17:14 node2 attrd[2531]:   notice: Removing all node1 attributes for peer loss
    -
    Sep 16 18:17:25 node2 corosync[1182]:  [VOTEQ ] waiting for quorum device Qdevice poll (but maximum for 30000 ms)
    Sep 16 18:17:25 node2 corosync[1182]:  [TOTEM ] A new membership (192.168.122.11:10972) was formed. Members joined: 1
    Sep 16 18:17:25 node2 corosync[1182]:  [CPG   ] downlist left_list: 0 received
    Sep 16 18:17:25 node2 corosync[1182]:  [CPG   ] downlist left_list: 0 received
    

Environment

  • Red Hat Enterprise Linux Server (RHEL) 7 with the High Availability or Resilient Storage Add-Ons
  • pacemaker cluster with corosync-qdevice

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