Files to send to troubleshoot Sysload / SP Analyst related software

Document ID : KB000088301
Last Modified Date : 14/04/2018
Show Technical Document Details
Issue:
Affects Release version(s): 5

This article describes the list of Files to be sent to the Technical Support for SP Analyst products troubleshooting
Environment:
OS: All
Resolution:
A. Introduction

Troubleshooting of SP Analyst products generally requires to examine the program’s log and configuration files.

The log files are mandatory to start troubleshooting a problem and not only because they keep the trace of the program’s activity but also because they provide information that is vital to understand
the environment where the program is executed:

 · Operating system family
 · Exact version of the operating system
 · Virtualization of the environment if any
 · Version of the performance library used by Sysload on the operating system
 · Etc.

The logs also deliver precise information on the program:

 · Program version
 · Exact build number and build date
 · Type and number of tokens required to start the program
 · Etc.

The configuration files allow to verify if the program’s configuration currently used is appropriate or not, and/or if any modification of the configuration parameters could be implemented to solve the
issue.
Sending these files directly to the Technical Support team when opening a case ensures a faster and better handling of the issue.

<sysload> represents the path to Sysload SP Analyst programs and files in the document which is typically:
 · C:\Program Files\Sysload on Windows
 · /usr/local/sysload on Unix/Linux

B. Files to provide to help troubleshooting for the most common SP Analyst programs

1. SP Analyst Console files


 · Configuration file ('<sysload>\console\sld.ini').
 · Main log ('<sysload>\console\console.log').
 · Communication log ('<sysload>\console\sldmscom.log').
 · Screen copies showing the problem.
 · Sending the files specified for Management Server troubleshooting may help diagnose issues related to the console.

2. SP Analyst Management Server files

- Communication Server:
 · Configuration file ('<sysload>\sldcs\sldcs.ini').
 · Execution log ('<sysload>\sldcs\sldcs.log').

- Management Server:
 · Configuration file ('<sysload>\sldmgts\sldmgts.ini').
 · Execution log ('<sysload>\sldmgts\sldmgts.log').

- SP Analyst console:
 · Communication Server and Management Server work with the SP Analyst console (as well as  other client applications).
 · When diagnosing a problem with Management Server, it is also useful to diagnose the SP Analyst console.
 · Refer to the SP Analyst console section above to get the list of console files to send.

3. SP Analyst Token Server
 · Configuration file ('<sysload>/sldtkd/sldtkd.ini').
 · Execution log ('<sysload>/sldtkd/sldtkd.log').
 · Screen captures showing pages of the Token Server web interface (License info, token status...)

4. SP Analyst agent for Windows

- Collector:
 · Configuration file ('<sysload>\sldrmd\sldrmd.ini').
 · Execution log ('<sysload>\sldrmd\sldrmd.log').
 · Entity definition:
   o '<sysload>\sldrmd\entity.ini'.
   o '<sysload>\sldrmd\entity_EM.ini' (if exists).
 · Event definition:
   o '<sysload>\sldrmd\event.ini'.
   o '<sysload>\sldrmd\event_EM.ini' (if exists).

- File Server:
 · Initialization of File Server (<sysload>\sldfsd\sldfsd.cfg).
 · Configuration of File Server (<sysload>\sldfsd\sldfsd.ini).
 · Log of File Server (<sysload>\sldfsd\sldfsd.log).

- Script Monitor:
 · Initialization of Script Monitor (<sysload>\sldsmd\sldsmd.cfg).
 · Configuration of Script Monitor (<sysload>\sldsmd\sldsmd.ini).
 · Log of Script Monitor (<sysload>\sldsmd\sldsmd.log).

- Log Analyzer:
 · Initialization of Log Analyzer (<sysload>\sldlogd\sldlogd.cfg).
 · Configuration of Log Analyzer (<sysload>\sldlogd\sldlogd.ini).
 · Log of Log Analyzer (<sysload>\sldlogd\sldlogd.log).

5. SP Analyst agent for Unix or Linux
- Collector:
 · Configuration ('<sysload>/coll/conf/sldrmd-init').
 · Execution log ('<sysload>/coll/sldrmd.log').
 · Event definition:
   o '<sysload>/coll/conf/<hostname>-alert'.
   o '<sysload>/coll/conf/Event_EM.ini' (if exists).
 · Entity definition:
   o '<sysload>/coll/conf/entity-init'.
   o '<sysload>/coll/conf/Entity_EM-init' (if exists).

If the program has crashed, check if a file called 'core' or 'core.<pid>' is located in the following directories:
 · '<sysload>/coll/conf'.
 · '<sysload>/coll/pgm'.

- File Server:
 · Configuration ('<sysload>/coll/conf/sldfsd-init').
 · Execution log ('<sysload>/coll/sldfsd.log').
 · Initialization ('<sysload>/coll/conf/sldfsd').

If the program has crashed, check if a file called 'core' or 'core.<pid>' is located in the following directories:
 · '<sysload>/coll/conf'.
 · '<sysload>/coll/pgm'.

- Script Monitor:
 · Configuration ('<sysload>/coll/conf/sldsmd-init').
 · Execution log ('<sysload>/coll/sldsmd.log').
 · Initialization ('<sysload>/coll/conf/sldsmd').

If the program has crashed, check if a file called 'core' or 'core.<pid>' is located in the following directories:
 · '<sysload>/coll/conf'.
 · '<sysload>/coll/pgm'.

- Log Analyzer:
 · Configuration ('<sysload>/coll/conf/sldlogd-init').
 · Execution log ('<sysload>/coll/sldlogd.log').
 · Initialization ('<sysload>/coll/conf/sldlogd').

If the program has crashed, check if a file called 'core' or 'core.<pid>' is located in the following directories:
· '<sysload>/coll/conf'.
· '<sysload>/coll/pgm'.

6. SP Analyst agent for Citrix

- Collector:
 · Configuration of the Collector (<sysload>\sldrmd_ctx\sldrmd_ctx.ini).
 · Log of the Collector (<sysload>\sldrmd_ctx\sldrmd_ctx.log).
 · Entity definition:
   o '<sysload>\sldrmd_ctx\entity.ini'.
   o '<sysload>\sldrmd_ ctx \entity_EM.ini' (if exists).
 · Event definition:
   o '<sysload>\sldrmd_ ctx \event.ini'.
   o '<sysload>\sldrmd_ ctx \event_EM.ini' (if exists).
 
- File Server:
 · Initialization of File Server (<sysload>\sldfsd\sldfsd.cfg).
 · Configuration of File Server (<sysload>\sldfsd\sldfsd.ini).
 · Log of File Server (<sysload>\sldfsd\sldfsd.log).

- Script Monitor:
 · Initialization of Script Monitor (<sysload>\sldsmd\sldsmd.cfg).
 · Configuration of Script Monitor (<sysload>\sldsmd\sldsmd.ini).
 · Log of Script Monitor (<sysload>\sldsmd\sldsmd.log).

- Log Analyzer:
 · Initialization of Log Analyzer (<sysload>\sldlogd\sldlogd.cfg).
 · Configuration of Log Analyzer (<sysload>\sldlogd\sldlogd.ini).
 · Log of Log Analyzer (<sysload>\sldlogd\sldlogd.log).

7. SP Analyst agent for Oracle

- Collector on Windows:
 · Execution log ('<sysload>\sldord\sldord.log').
 · Configuration ('<sysload>\sldord\sldord.ini').
 · Installation log ('<sysload>\sldord\o_csld.log').
 · Event definition:
   o '<sysload>\sldord\<instance name>-alert'.
   o '<sysload>\sldord\<instance name>-alert_EM' (if exists).
 
- Collector on Unix and Linux:
 · Execution log ('<sysload>/coll/sldord.log').
 · Configuration ('<sysload>/coll/conf/sldord-init').
 · Configuration log ('<sysload>/coll/o_csld.log').
 · If exist, log of the Collector stop ('<sysload>/coll/sldord_stop.log').
 · Event definition:
   o '<sysload>/coll/conf/<instance name>-alert'.
   o '<sysload>/coll/conf/<instance name>-alert_EM' (if exists).

- DB Event on Windows:
 · Execution log ('<sysload>\dborevt\dboraevt.log').
 · Configuration ('<sysload>\dborevt\dboraevt.ini').
 · Library of SQL queries ('<sysload>\dborevt\sqlreqlib\*.*').
 · Log of SQL commands ('<sysload>\dborevt\dbeventsql.log').
 · Event log file ('<sysload>\dborevt\alertcmd.log').