IBM Support

IT36950: IBM MQ installation might cause failure in non-IBM MQ programs that use libcurl or libedit libraries

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

  • IBM MQ installation might cause failure in non-IBM MQ programs
    like yum, python etc. that use libcurl or libedit libraries if
    the user runs ldconfig before running the non-IBM MQ programs.
    
    Example:
    
    sudo ldconfig
    sudo yum update
    
      /usr/lib64/python2.7/site-packages/pycurl.so: undefined
    symbol: CRYPTO_num_locks
    

Local fix

  • Remove the line that contains "/usr/lib64" in
    /etc/ld.so.conf.d/mqm.conf before running ldconfig
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users of IBM MQ who run ldconfig before running any non-IBM MQ
    programs that use libcurl or libedit libraries.
    
    
    Platforms affected:
    Linux on x86-64, Linux on zSeries, Linux on x86, Linux on S390
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    IBM MQ ships libedit and libcurl libraries with the product and
    installs them to the IBM MQ installation directory. These
    libraries might also be installed by the user or the OS in
    /usr/lib64.
    IBM MQ adds "/usr/lib64" to /etc/ld.so.conf.d/mqm.conf during
    the installation. This might cause
    conflict in libraries on non-IBM MQ programs if the user run
    ldconfig before running the program.
    The "/usr/lib64" in /etc/ld.so.conf.d/mqm.conf is required only
    for the primary installation.
    

Problem conclusion

  • The IBM MQ code has been modified to add "/usr/lib64" in
    /etc/ld.so.conf.d/mqm.conf only for the primary installation.
    
    Users who have configured the IBM MQ primary installation and
    see a library conflict with IBM MQ installed libraries
    are recommended to unset the primary installation before running
    ldconfig.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.2 LTS   9.2.0.5
    v9.x CD    9.2.5
    
    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

    IT36950

  • Reported component name

    MQ BASE V9.2

  • Reported component ID

    5724H7281

  • Reported release

    920

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-05-18

  • Closed date

    2021-11-02

  • Last modified date

    2021-11-02

  • 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 BASE V9.2

  • Fixed component ID

    5724H7281

Applicable component levels

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"920"}]

Document Information

Modified date:
03 November 2021