RHEL 6 clustered messaging service shows as 'stopped' in clustat output but qpidd process is still running

Solution In Progress - Updated -

Issue

  • clustat output indicates that services on the rebooted node as "stopped" despite active qpid processes running

Environment

  • Red Hat Enterprise Linux (RHEL) 6 with the High Availability Add On
  • MRG Messaging with qpidd
  • qpidd managed by cluster services in /etc/cluster/cluster.conf via script resources based on /etc/init.d/qpidd
  • clustat shows service as stopped but ps shows corresponding qpidd processes running

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