IBM Support

IT33612: MQ Appliance HA initialization error during reboot

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • During reboot of MQ appliance the following FDC and error
    message will be generated.
    
     AMQ171906.0.FDC  1594400121.020646 2020/07/10 12:55:21.020646-4
    9.1.0.5 1 -d /dev/sdb   mqdpinit  171906   1
    XC022001 xcsDisplayMessage aplE_HA_INIT_FAILED
    
    
    Error messages from initHA log:
    
    Fri Jul 10 12:55:16 EDT 2020: { Entering initHA
    Fri Jul 10 12:55:16 EDT 2020:   shell-init: error retrieving
    current directory: getcwd: cannot access parent directories: No
    such file or directory
     172017 ttyS0    00:00:00 initHA
    ...
    Fri Jul 10 12:55:20 EDT 2020:    amqqmutil -m shell-init: error
    retrieving current directory: getcwd: cannot access parent
    directories: No such file or directory -l
    QMNAME(TESTQM)              HA(Replicated) HALSADDR() HALSINT()
    DRPORT(1200) DRADDR(10.182.0.19)
    ...
    Fri Jul 10 12:55:21 EDT 2020:    AMQ7048E: The queue manager
    name is either not valid or not known.
    
    Fri Jul 10 12:55:21 EDT 2020: } Leaving initHA 113
    
    The error might cause unexpected failures including migration
    problems and appliance reload.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of MQ appliance running with MQ version 9.1
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    A problem in setting working directory for an internal MQ
    process caused failure
    in HA initialization during reboot.
    

Problem conclusion

  • MQ code has been modified to set the working directory for the
    affected MQ process.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.1 LTS   9.1.0.7
    v9.2 LTS   9.2.0.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 number

    IT33612

  • Reported component name

    MQ APPLIANCE M2

  • Reported component ID

    5737H4700

  • Reported release

    915

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-07-20

  • Closed date

    2020-11-19

  • Last modified date

    2020-11-26

  • 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

[{"Line of Business":{"code":"LOB36","label":"IBM Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS5K6E","label":"IBM MQ Appliance"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"915"}]

Document Information

Modified date:
27 November 2020