Troubleshooting problems with HA queue manager run locations

If you encounter the situation where a high availability (HA) queue manager is not running on the expected appliance, or is not running at all, you can take the following steps to investigate the cause.

Failed resource actions

Start by investigating whether there have been any failed resource actions associated with the queue manager.

The HA solution monitors and manages resources. If an error occurs when performing an operation on a resource on an appliance, this information is recorded using a failed resource action. Some failed resource actions prevent the queue manager from running and must be cleared before the queue manager can be restarted.

Use the following command to see any failed action resources associated with a queue manager:

status -a qmname

For example:

mqa(mqcli)# status qm1 -a
QM(qm1)                                  Status(Running)
CPU:                                     0.90%
Memory:                                  188MB
Queue manager file system:               56MB used, 0.2GB allocated [45%]
HA role:                                 Primary
HA status:                               Normal
HA control:                              Enabled
HA preferred location:                   This appliance
HA blocked location:                     None

Failed resource action:                  Monitor
Resource type:                           HA floating IP
Failure location:                        This appliance
Failure time:                            2022-01-01 10:58:04
Failure reason:                          Not running
Blocked location:                        None

The failed resource action in this example relates to the floating IP address used for the queue manager. The failed resource action will force the queue manager to restart in an attempt to resolve the issue. Some failed resource actions can resolve the underlying issue when the queue manager restarts, others cannot and require the initial cause to be fixed. After you fix the underlying issue, or confirm it has fixed itself, you issue the cleanha -m qm1 command to remove the failed resource action.

Other causes

You should also investigate other potential causes of HA queue manager problems:

Appliance offline: If an HA queue manager is not running on the preferred appliance, check that the appliance is actually available.
Appliance suspended: The appliance has been suspended from the HA group by running the sethagrp -s command.
The queue manager has been stopped: If the queue manager has been stopped using the endmqm command, HA control is disabled for that queue manager.