IBM Support

IT31430: FDC record with ProbeID XC022001 is reported after upgrading theMQ appliance firmware

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

  • After applying the 9.1.0.4 firmware, the Appliance may generate
a failure data capture (FDC) record with the following
information:
mqdpinit
XC022001
MQM Function Stack
dpcInitDaemon
xcsDisplayMessageForError
xcsWriteDiagnosticMessages
xcsFFST

aplE_HA_INIT_FAILED


While starting corosync service permission errors like the below
are reported.

snippet from initHA log
Wed Mar 18 06:02:38 EDT 2020:    /usr/share/corosync/corosync
start
Wed Mar 18 06:02:39 EDT 2020:    shell-init: error retrieving
current directory: getcwd: cannot access parent directories: No
such file or directory
Starting Corosync Cluster Engine (corosync): touch: cannot touch
'/var/lock/subsys/corosync': No such file or directory

Local fix

  • 



Problem summary


    

  • ****************************************************************
USERS AFFECTED:
All MQAppliance users with an HA configuration.


Platforms affected:
MultiPlatform

****************************************************************
PROBLEM DESCRIPTION:
Incorrect permission set on some of the internal files used by
the internal corosync process results in errors and causes the
FDC record. Though the FDC is cut the corosync service is
started successfully and the HA functionality is not affected.

    



Problem conclusion


    

  • The code has been modified to correct the permission errors.

---------------------------------------------------------------
The fix is targeted for delivery in the following PTFs:

Version    Maintenance Level
v9.1 LTS   9.1.0.6

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
    IT31430
    • 

  • Reported component name
    MQ APPLIANCE M2
    • 

  • Reported component ID
    5737H4700
    • 

  • Reported release
    910
    • 

  • Status
    CLOSED  PER
    • 

  • PE
    NoPE
    • 

  • HIPER
    NoHIPER
    • 

  • Special Attention
    NoSpecatt / Xsystem
    • 

  • Submitted date
    2020-01-07
    • 

  • Closed date
    2020-06-29
    • 

  • Last modified date
    2020-06-29
    • 





    

  • 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


    








      
              
                            

              

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

                          

          
 
        

      

    

      

        

          

            
Document Information


            

            


                        

            Modified date:
            

            30 June 2020
            

            
                      

        


        

        


      

    

  



    

  

  
    
            

          
Page Feedback