IBM Support

IT21483: ACCEPTOR DAEMON STARTED WITH INIT.D SCRIPT FAILS DUE TO SYSTEMD IMPLEMENTATION PROBLEM

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as Vendor Solution.

Error description

  • Tivoli Storage Manager/IBM Spectrum Protect documentation
    recommends to use dsmcad.service shipped with the package The
    init.d script is still available to start the acceptor daemon on
    a systemd-based Linux distribution. The RC scripts in
    /etc/init.d should be converted on the fly at system
    initialization time into systemd service files.    When starting
    the acceptor daemon using the init.d script the operation fails
    due to the conversion script (systemd-sysv-generator) starting
    too early during the boot process before the /opt file system
    has been mounted.  This is systemd implementation problem with
    Red Hat.
    
    Customer/L2 Diagnostics (if applicable)
    None
    
    *NOTE*
    In Red Hat Enterprise Linux - RHEL 7, the System V init process
    has been replaced by systemd as the default init process. The
    dsmcad service script is installed in the System V location
    /etc/init.d
    
    Platforms affected:
    Red Hat Linux, Tivoli Storage Manager/IBM Spectrum Protect 7.1,
    8.1
    
    Initial Impact: Medium
    
    Additional Keywords: RHEL dsmcad TSM IT20524  technote 1976275
    

Local fix

  • 1) Replace the /etc/init.d/ symbolic links with the real files
    2) Use the provided dsmcad.service file, as Tivoli Storage
    Manager/IBM Spectrum Protect documentation recommends.
    

Problem summary

Problem conclusion

Temporary fix

Comments

  • The problem is caused by a bug inside RH systemd implementation:
    - the systemd-sysv-converter service is started before the local
    file systems are mounted at the boot time. As a result,
    /etc/init.d/dsmcad (that is a symbolic link to
    '/opt/tivoli/tsm/client/ba/bin/rc.dsmcad', in fact) is ignored.
    For more details about the issue and a possible solution,
    please, follow these links:
    https://bugzilla.redhat.com/show_bug.cgi?id=1285492
    https://access.redhat.com/solutions/2067013
    

APAR Information

  • APAR number

    IT21483

  • Reported component name

    TSM SERVER

  • Reported component ID

    5698ISMSV

  • Reported release

    81L

  • Status

    CLOSED ISV

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-07-17

  • Closed date

    2017-08-15

  • Last modified date

    2017-08-15

  • 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

    TSM CLIENT

  • Fixed component ID

    5698ISMCL

Applicable component levels

[{"Line of Business":{"code":"LOB26","label":"Storage"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGSG7","label":"Tivoli Storage Manager"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"81L"}]

Document Information

Modified date:
13 February 2021