IBM Support

The command 'systemctl status tsminst1' may fail to display status.

Troubleshooting


Problem

Recent versions of Linux distribution uses systemd and the systemctl command to manage services. However, the command 'systemctl status tsminst1' may fail to display status, even if dsmserv process is running well.

Symptom

If you use the systemctl command to manage TSM service, you have to update the file /etc/rc.d/init.d/tsminst1. Unless you don't update it, the command 'systemctl status <instance name>' always displays the status 'Active: failed' incorrectly even if the TSM Server process correctly started by the command 'systemctl start <instance name>'.

    # systemctl status tsminst1 -l
    * tsminst1.service - SYSV: Starts/Stops an IBM Tivoli Storage Manager Server instance
       Loaded: loaded (/etc/rc.d/init.d/tsminst1)
       Active: failed (Result: resources) since Mon yyyy-mm-dd hh:mm:ss JST; n weeks m days ago

    .......


You may find APAR IT16102, and update the file /etc/rc.d/init.d/tsminst1 according to the local fix of IT16102, as below:


    (From:)
    # pidfile: /var/run/dsmserv_instancename.pid
    (To:)
    # pidfile: /var/run/dsmserv_tsminst1.pid

However, you may still fails to display the status. The command 'systemctl status <instance name>' may still displays the incorrect status 'Active: failed'.

    # systemctl status tsminst1 -l
    * tsminst1.service - SYSV: Starts/Stops an IBM Tivoli Storage Manager Server instance
       Loaded: loaded (/etc/rc.d/init.d/tsminst1)
       Active: failed (Result: resources) since Mon yyyy-mm-dd hh:mm:ss JST; n weeks m days ago
    ......

[{"Product":{"code":"SSEQVQ","label":"IBM Spectrum Protect"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"Server","Platform":[{"code":"PF016","label":"Linux"}],"Version":"Version Independent","Edition":"","Line of Business":{"code":"LOB69","label":"Storage TPS"}}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Historical Number

16717

Document Information

Modified date:
17 June 2018

UID

swg21998709