Why does clustered service starts on wrong/non-preferred node? - Red Hat Customer Portal

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

Issue

When clustered services are started from either Luci or the command line the services do not start on the highest priority node within the failover domain.
Even though the clustered service is configured in an ordered failover domain it is not starting on the highest priorty node

Environment

Red Hat Enterprise Linux 5
Red Hat Enterprise Linux 6
Red Hat Cluster Suite
Red Hat High Availability Add On
Clustered service configured configured to run in an ordered-restricted failover domain with nofailback="1"

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)