search cancel

How to generate debug traces for installation using the LSM command or installation of PIF,PKG,RPM SD Packages?


Article ID: 17388


Updated On:


CA Automation Suite for Data Centers - Configuration Automation CA Client Automation - Asset Management CA Client Automation - IT Client Manager CA Client Automation CA Client Automation - Remote Control CA Client Automation - Asset Intelligence CA Client Automation - Desktop Migration Manager CA Client Automation - Patch Manager CA Server Automation



If an error occurs during an installation using the lsm command or during the installation of a SD package of type PIF/RPM/PKG on a Unix/Linux machine, it could be useful to get debug/trace files in order to have more information about the error.

Example :
A RPM package has been created in ITCM :

<Please see attached file for image>

Figure 1

When sending this package to a Linux machine, an error SMX occurs :

<Please see attached file for image>

Figure 2

How to generate trace files in order to have more information about this error ?


Enabling LSM trace
On the Unix/Linux machine do the following:

  • Edit file /opt/CA/installer/conf/sma.cfg and set TRACE=1 in section [transaction] :
  • In the same Terminal execute the following commands :
    caf stop
    export LSM_TRACELEVEL=6
    caf start
    caf will be started with LSM_TRACELEVEL=6
  • Try the LSM installation again/send the PIF,PKG,RPM SD Package again to the machine.
  • sma_*.trc trace files are generated under /opt/CA/installer/trace containing trace logs of execution of lsm command.

Disable LSM Trace

In order to disable the trace edit the file /opt/CA/installer/conf/sma.cfg and set TRACE to 0 :



Release: SEAUBC99000-12.8-Server Automation-Base Configuration


1558709399812000017388_sktwi1f5rjvs16rgg.gif get_app
1558709398065000017388_sktwi1f5rjvs16rgf.gif get_app