Readme File for IBM^® Spectrum Symphony 7.3.2 Interim Fix 602054

Readme File for: IBM Spectrum Symphony

Product Release: 7.3.2

Update Name: Interim Fix 602054

Fix ID: sym-7.3.2-build602054-bbva

Publication Date: June 5, 2024

 

This interim fix includes two updates to enhance logging in the service instance manager (SIM) for IBM Spectrum Symphony 7.3.2 with Fix 601711:

1.       The first update adds INFO level messages to the SIM log to show the socket handle state and how many bytes are expected. There is new code to check whether the socket handle is valid and a message is logged if there is an error.

2.       The second update adds INFO level messages to the SIM log for global standby transfers to show the intermediate operations and a periodic internal state dump every 15 minutes for all running SIM’s.

 

Contents

1. List of fixes

2. Download location

3. Product and components affected

4. Installation and configuration

5. Uninstallation

6. List of files

7. Product notifications

8. Copyright and trademark information

 

1.   List of fixes

APAR: P105147

2.   Download location

Download interim fix 602054 from the following location: https://www.ibm.com/eserver/support/fixes/

3.   Product and components affected

Component name, Platform, Fix ID:

SOAM, Linux-x86_64, sym-7.3.2-build602054-bbva

4.   Installation and configuration

Follow the instructions in this section to download and install this interim fix on your cluster.

System requirements

Linux-x86_64

Prerequisites

Fix 601711 must be installed before applying this fix package.

Installation and configuration

a.     Log on to the primary host as the cluster administrator and disable all applications:

> egosh user logon -u Admin -x password

> soamcontrol app disable all

b.     Download the package to each of your compute host (or just one host if you are using a shared file system) to, for example, to a /symfixes directory.

c.     Run the egoinstallfixes command to install the soamcore-7.3.2.0_x86_64_build602054.tar.gz files:

> egoinstallfixes /symfixes/soamcore-7.3.2.0_x86_64_build602054.tar.gz

Note: Running the egoinstallfixes command automatically backs up the current binary files to a fix backup directory for recovery purposes. Do not delete this backup directory; you will need it if you want to recover the original files. For more information on using this command, see the egoinstallfixes command reference.

d.     Run the pversions command to verify the installation:

> pversions -b 602054

e.     Update the application profile to add the PLATCOMMDRV_READ_STUCK_LOGGING and SIM_GLOBAL_STANDBY_LOGGING environment variables. Specify a value of Y to enable the optional logging, or specify N to disable the logging. All logging is at the INFO level, so the SIMs on the compute hosts should be configured to log at the INFO level to avoid any unnecessary logging:

        <SIM … >

           <osTypes>

            <osType name="all" startCmd="${SOAM_HOME}/${VERSION_NUM}/${EGO_MACHINE_TYPE}/etc/sim">

              <env name="PLATCOMMDRV_CONNECTION_RECV_TIMEOUT">15</env>

              <env name="PLATCOMMDRV_READ_STUCK_LOGGING">Y</env>

              <env name="SIM_GLOBAL_STANDBY_LOGGING">Y</env>

            </osType>

          </osTypes>

        </SIM>

With these parameters configured, the following messages will be logged at INFO level in the SIM log:

PLATCOMMDRV_READ_STUCK_LOGGING=Y

platcommdrv.Reactive_Stream - Reactive_Stream::handle_input current=131, reading_bytes=109, isNonBock=1, flags=2050

SIM_GLOBAL_STANDBY_LOGGING=Y

sim.client.Sim2SimManager - Sim2SimManager::onSIMConnected: Connected to global standby SIM url=127.0.0.1:43065

sim.client.Sim2SimClient - Sim2SimClient::queryLinger(): Querying info for global standby id=267a9a96-1ec4-11ef-c000-00000a0b51c1-140253310481984-1220561, from peer SIM.

sim.client.Sim2SimClient - Sim2SimClient::transferLinger(): Transferring global standby id=267a97bc-1ec4-11ef-c000-00000a0b51c1-140253310481984-1220561, from peer SIM.

sim.client.Sim2SimClient - Sim2SimClient::TransferResourceUnitResult(): Transfer completed for global standby pid=1161786

There will also be a periodic state dump of the SIM every 15 minutes controlled by the SIM_GLOBAL_STANDBY_LOGGING setting. The following output has been truncated. Enabling this output should not affect performance.

sim.simcore.ResourceUnitManager - Enter ResourceUnitManager::dump()

sim.simcore.ResourceUnitManager - ResourceUnitManager::dump() service id to service thread proxy id map size : 1975

sim.simcore.ResourceUnitManager - ResourceUnitManager::dump() service thread proxy id to service id map size : 1975

sim.simcore.ResourceUnitManager - ResourceUnitManager::dump() active resource map size : 1

sim.simcore.ResourceUnit - Enter ResourceUnit::dump() SimThreadProxy ID : 2f2545b0-1ec4-11ef-c000-00000a0b51c1-140150839416384-1220357

sim.simcore.ResourceUnit - ResourceUnit::dump() broker map size <1>.

sim.simcore.ResourceUnit - ResourceUnit::dump() linger broker map size <0>.

sim.simcore.ServiceBroker - Enter ServiceBroker::dump() Service ID <si-sympingservice-1974-pid=1220378-eid=9032-host=bleepers91.fyre.ibm.com>

sim.simcore.ResourceUnit - Exit ResourceUnit::dump() SimThreadProxy ID : 2f2545b0-1ec4-11ef-c000-00000a0b51c1-140150839416384-1220357

sim.simcore.ResourceUnitManager - ResourceUnitManager::dump() linger resource map size :0

sim.simcore.ResourceUnitManager - ResourceUnitManager::dump() m_queryLingerStpMap size :0

sim.simcore.ResourceUnitManager - Exit ResourceUnitManager::dump()

 

The PLATCOMMDRV_READ_STUCK_LOGGING and SIM_GLOBAL_STANDBY_LOGGING settings can be enabled independently, if required. To debug the read stuck issue, just enable PLATCOMMDRV_READ_STUCK_LOGGING=Y. To debug the extra services running on the compute host, enable SIM_GLOBAL_STANDBY_LOGGING=Y. Initially, enable both and try to reproduce both issues. If one or both issues cannot be reproduced, first disable both settings and try to reproduce the issue. Once reproduced, try enabling the settings independently.

 

The following new INFO messages have been added. The latter message will provide more information for use with PLATCOMMDRV_CONNECTION_RECV_TIMEOUT.

platcommdrv.Reactive_Stream - Reactive_Stream::handle_input failed to operate on handle 131, error=9

platcommdrv.Reactive_Stream - Reactive_Stream::handle_input excessive time in receive for handle 131 time=23 seconds.

 

Once the issue has been reproduced, send IBM all compute host logs, network and process data from the host with the issue.

 

f.       From the primary host, register and enable the applications:

> soamreg application_profile.xml

> soamcontrol app enable application_name

 

5.   Uninstallation

If required, follow the instructions in this section to uninstall this interim fix from your cluster:

a.     Log on to the primary host as the cluster administrator and disable all applications:

> egosh user logon -u Admin -x password

> soamcontrol app disable all

b.     Roll back this interim fix:

> egoinstallfixes -r 602054

c.     Remove the configuration in the application profile.

d.     From the primary host, register and enable the applications:

> soamreg application_profile.xml

> soamcontrol app enable application_name

6. List of files

   soam/7.3.2/linux-x86_64/etc/sim

 

7.   Product notifications

To receive information about product solution and patch updates automatically, subscribe to product notifications on the My Notifications page http://www.ibm.com/support/mynotifications/ on the IBM Support website (http://support.ibm.com). You can edit your subscription settings to choose the types of information you want to get notification about, for example, security bulletins, fixes, troubleshooting, and product enhancements or documentation changes. 

8.   Copyright and trademark information

© Copyright IBM Corporation 2024

U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

IBM®, the IBM logo, and ibm.com® are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.