rgmanager fails to stop a clustered tomcat-6 resource when the configuration file is located on a shared storage that is failing in RHEL 6

Solution Unverified - Updated -

Issue

  • rgmanager fails to stop a tomcat-6 resource while trying to relocate a failed service and set it to failed state requiring manual intervention. This seems to happen if the configuration file is located on a failed network storage (e.g. nfs).
Jul  3 16:20:30 node1 rgmanager Stopping service service:myService
Jul 03 16:20:29 node1 rgmanager status on netfs:sharedfs timed out after 10 seconds
Jul 03 16:20:30 node1 rgmanager Stopping service service:myService
Jul 03 16:23:30 node1 rgmanager [tomcat-6] Checking Existence Of File /sharedfs/tomcat.conf [tomcat-6:myTomcat] > Failed - File Is Not Readable
Jul 03 16:23:30 node1 rgmanager [tomcat-6] Verifying Configuration Of tomcat-6:myTomcat > Failed
Jul 03 16:23:30 node1 rgmanager stop on tomcat-6 "myTomcat" returned 2 (invalid argument(s))
Jul 03 16:24:00 node1 rgmanager stop on netfs:myService timed out after 30 seconds
Jul 03 16:24:01 node1 rgmanager #12: RG service:myService failed to stop; intervention required
Jul 03 16:24:01 node1 rgmanager Service service:myService is failed

Environment

  • Red Hat Enterprise Linux (RHEL) 6 with the High Availability Add On
  • rgmanager
  • resource-agents releases prior to 3.9.2-40.el6
  • One or more tomcat-6 resources in /etc/cluster/cluster.conf
    • The configuration file for the tomcat-6 resource is on shared storage, such as an fs, clusterfs, or netfs resource that is also part of the service
    • The shared file system storing the tomcat-6 config file is failing in some way

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
Close

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