IT34419: MQ Appliance queue manager failover is unsuccessful if the queuemanager file system is in use by another process

APAR status

• Closed as program error.

Error description

• A queue manager is unable to manually failover successfully
  with sethapreferred or sethagrp commands when its logs are
  being accessed by the REST API or dspmqerr command. The
  failover will fail and queue manager will go into Partitioned
  state.
  
  The following errors can be observed on the message logs under
  trace directory:
  
  Sep 25 10:16:04 APP1 Filesystem(QM1_fs)[1418515]: ERROR:
  Couldn't unmount /var/mqm/vols/QM1; trying cleanup with KILL
  Sep 25 10:16:04 APP1 Filesystem(QM1_fs)[1418515]: INFO: No
  processes on /var/mqm/vols/QM1 were signalled. force_unmount is
  set to 'false'
  Sep 25 10:16:04 APP1 lrmd[23250]:  warning: QM1_fs_stop_0
  process (PID 1418515) timed out
  Sep 25 10:16:04 APP1 lrmd[23250]:  warning:
  QM1_fs_stop_0:1418515 - timed out after 60000ms
  Sep 25 10:16:04 APP1 lrmd[23250]:   notice:
  QM1_fs_stop_0:1418515:stderr [ umount: /var/mqm/vols/QM1:
  target is busy. ]
  ...
  Sep 25 10:16:04 APP1 crmd[23253]:    error: Result of stop
  operation for QM1_fs on APP1: Timed Out
  

Local fix

• Stop the execution of any rest API scripts or dspmqerr command
  while a manual failover is executed.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Users using MQ Appliance for HA
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  If the queue manager file system is in use while the failover
  happens then an attempt is made to restrictively terminate the
  process that is accessing the file system.  However, an omission
  in this logic meant that the process did not detect a complete
  set of processes that were accessing the filesystem, and so did
  not attempt to terminate them.
  

Problem conclusion

• The code has been modified to correct the detection of other
  processes accessing the queue manager filesystem.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v9.1 LTS   9.1.0.8
  v9.2 LTS   9.2.0.3
  v9.x CD    9.2.2
  
  The latest available maintenance can be obtained from
  'WebSphere MQ Recommended Fixes'
  http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
  
  If the maintenance level is not yet available information on
  its planned availability can be found in 'WebSphere MQ
  Planned Maintenance Release Dates'
  http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
  ---------------------------------------------------------------
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  MQ APPLIANCE M2

• Fixed component ID

  5737H4700

Applicable component levels