After rebooting the server, none of the ITM components starts

Technote (troubleshooting)


Problem(Abstract)

ITM components including TEPS, TEMS or the agents failed to start after rebooting the server

Symptom

You may notice the below error in the TEMS or TEPS or agent log

(4B6B16E1.0041-19F8:kbbssge.c,52,"BSS1_GetEnv") ICCRTE_DIR="<gskit directory>"
(4B6B16E1.0042-19F8:kglcry.c,226,"checkICCStatus") ICC unknown error detected (4B6B16E1.0043-19F8:kglcry.c,177,"printICCStatus") majRC=999, minRC=999, mode=999 (4B6B16E1.0044-19F8:kglcry.c,179,"printICCStatus") desc=The specified module could not be found. (4B6B16E1.0045-19F8:kglcry.c,2216,"initializeICC") ICC initialization failed

Cause

The cause of the problem is related to GSKit. It could be broken or the ITM components are not pointing to the correct GSKit

Resolving the problem

To resolve the issue, edit the configuration file and make sure that the correct GSKit path is used. Since the GSKit path is referenced in many configuration files, update the below configuration files if available. Also, make sure that the GSKit path is consistent across all the environmental variable on the server

Windows

Environmental file

%CANDLEHOME%\CMS\KBBENV
%CANDLEHOME%\BIN\KUIENV
%CANDLEHOME%\BIN\KFWENV
%CANDLEHOME%\TMAITM6\KpcENV

Variable

ICCRTE_DIR
CSV1_PATH
PATH

Linux/UNIX

Environmental file

$candlehome/config/<hostname>_ms_<temsname>.config
$candlehome/config/pc.config

Variable

LD_LIBRARY_PATH
LIBPATH
SHLIB_PATH
ICCRTE_DIR

Where <pc> is the two letter product code


Rate this page:

(0 users)Average rating

Document information


More support for:

Tivoli Management Server for Distributed Systems

Software version:

6.1, 6.2, 6.2.1, 6.2.2

Operating system(s):

AIX, Linux, Windows

Software edition:

All Editions

Reference #:

1421540

Modified date:

2011-02-18

Translate my page

Machine Translation

Content navigation