Log in to Your Red Hat Account

Your Red Hat account gives you access to your profile, preferences, and services, depending on your status.

If you are a new customer, register now for access to product evaluations and purchasing capabilities.

Need access to an account?

If your company has an existing Red Hat account, your organization administrator can grant you access.

If you have any questions, please contact customer service.

Red Hat Account Number:

Red Hat Account

Customer Portal

For your security, if you’re on a public computer and have finished using your Red Hat services, please be sure to log out.

Select Your Language

With votequorum's last_man_standing enabled, the last node still loses quorum when the second-to-last node becomes unresponsive in a RHEL 7 High Availability cluster

Solution Unverified - Updated 2015-04-09T13:54:35+00:00 -

Issue

I have last_man_standing configured in this cluster, and nodes are removed one-by-one in a cascading fashion, and quorum is decreased after each event. However when it gets down to the last two nodes and one of them leaves, the remaining node loses quorum.
last_man_standing doesn't work when the last node leaves
Is last_man_standing supposed to work all the way down to a single node?

Environment

Red Hat Enterprise Linux (RHEL) 7 with the High Availability Add On
corosync with the votequorum plugin

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

New to Red Hat?

Learn more about Red Hat subscriptions

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.

Here are the common uses of Markdown.

Code blocks

~~~
Code surrounded in tildes is easier to read
~~~

Links/URLs

[Red Hat Customer Portal](https://access.redhat.com)