IT36293: SPACE MANAGEMENT DSMRECALLD MAY NOT START AFTER A SYSTEM BOOT DUE TO MISSING RPCBIND DEPENDENCY

APAR status

• Closed as program error.

Error description

• Space Management (HSM) dsmrecalld may not start upon a system
  boot due to missing rpcbind dependency.
  As a result, the HSM
  managed file systems could not be mounted at boot time or
  subsequent accesses to HSM migrated files might fail due to
  "Input/output" error.
  
  IBM Spectrum Protect Versions Affected:
  All Space Management client versions on AIX GPFS  and Linux
  GPFS platforms
  
  Initial Impact: High
  
  Additional Keywords:
  dsmrecalld, receiver, rpc, rpcbind, svc_register
  

Local fix

• On all HSM nodes within your Scale cluster:
  1) Stop HSM
  service:
  
  2) Edit '/usr/lib/systemd/system/hsm.service' HSM
  systemd configuration file, so that it contains
  the following
  content.
  Note: the important addition is three new lines under
  [Unit] section of the configuration file:
  "Wants", "Requires"
  and "After":
  "
  [Unit]
  Description=HSM
  Service
  Wants=rpcbind.service
  Requires=network.target
  rpcbind.service
  After=network.target rpcbind.service
  
  [Service]
  
  ExecStart=/opt/tivoli/tsm/client/hsm/bin/dsmwatchd nodetach
  Rest
  art=always
  
  [Install]
  WantedBy=multi-user.target
  "
  3) Reload
  the HSM systemd configuration and start the HSM service as
  follows:
  systemctl daemon-reload
  systemctl start hsm
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * IBM Spectrum Protect for Space Management (HSM) client       *
  * versions 7.1.x and 8.1.x on Linux GPFS platforms             *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See ERROR DESCRIPTION.                                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fixing level when available. This problem is projected *
  * to be fixed in HSM client levels 7.1.8.11 and 8.1.12. Note   *
  * that this is subject to change at the discretion of IBM.     *
  ****************************************************************
  

Problem conclusion

• After the fix, the HSM recall function will work as expected
  regardless whether the rpcbind service is started before or
  after the HSM service at the system boot time.
  

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:

Modules/Macros

• dsmrecal
  

Fix information

• Fixed component name

  TSM SPACE MGMT

• Fixed component ID

  5698HSMCL

Applicable component levels