resources that return "not installed" from a monitor operation before their dependent resources are active cannot be started in a RHEL 6 High Availability pacemaker cluster
Issue
- When we add a
mysqlresource in apacemakercluster, the other nodes in the cluster report that themysqldbinary is not found and reports "Not installed" which prevents the mysql resource from starting on those nodes. - If a resource depends on another (such as a
Filesystem) before it can be found or used, thenpacemakerwill report "not installed" errors for it on startup and we can never enable the group its in
Environment
- Red Hat Enterprise Linux (RHEL) 6 with the High Availability Add On
pacemaker- A resource that depends on another resource before it can be activated
- This is usually true for resources where the binary or some critical file is installed on a shared storage resource like a
Filesystem
- This is usually true for resources where the binary or some critical file is installed on a shared storage resource like a
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Close
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.