IBM E027SLL-H Troubleshooting Guide - Page 10
Monitoring agent, troubleshooting
![]() |
View all IBM E027SLL-H manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 10 highlights
The Tivoli Enterprise Monitoring Server start task (CANSDSST default) encountered error message 'KLVST044 LOADLIST MEMBER NOT FOUND IN RKANPAR DATASET (KDSLLIST) KppLLIST KLVST001 CANDLE ENGINE INITIALIZATION ERROR(S), ABEND U0012' in the RKLVLOG at startup 167 KDS Parameters not generated from the batch parm deck 167 Cannot encrypt text. A call to CSNBSYE failed. Cannot encrypt contents of keyfile . . . . . 168 The error "KLVST005 MVS JOBSTEP AUTHORIZATION REQUIRED KLVST001 CANDLE ENGINE INITIALIZATION ERROR(S), ABEND U0012 CSV019I - Required module KLVSTWTO not accessed, it is not APF Authorized (RKANMODL) CSV028I - ABEND 306-0C" occurs in the z/OS monitoring server RKLVLOG during startup 168 The error "KLVSQ000 carved mode in effect for extended storage" occurred in the RKLVLOG during startup 168 Error message 'KDSMA013 OPEN VTAM for VDM1APPL failed with status 8' occurs in the Tivoli Enterprise Monitoring Server start task (CANSDSST default 169 Chapter 10. Monitoring agent troubleshooting 171 Command-line interface 171 OS agents 171 Linux OS agent fails to start 172 OS agent start command fails 172 Specific events are not monitored by the Windows OS agent 172 Take action commands and reflex automation . . 172 Warehouse agents 173 Unable to configure the Warehouse Proxy agent with modified parameters from the Tivoli Enterprise Portal GUI 174 Workspaces 174 A workspace view is showing an error . . . . 174 Local history migration tools move the agent operation logs to multiple agent history locations . 175 Unreadable tool tip information for Available EIF Receivers list of the Situation editor 175 32-bit Agent Builder agent will not start on 64-bit Windows with System Monitor Agent-installed OS Agent 175 Unable to locate the file name of an exported situation that begins with numerals 176 Tivoli Enterprise Portal data for UNIX OS and Linux OS agents is not updated after stopping the disk 176 Testing the connection to the Tivoli Data Warehouse database is valid even with an invalid password 176 Configured non-root user agent starts up as root 176 Large historical collections slow monitoring agents 176 Unable to access History Collection Configuration for any agent 176 viii IBM Tivoli Monitoring: Troubleshooting Guide Agent names and icons are displayed incorrectly 177 64 bit monitoring agents are not started . . . . 177 Errors in the configuration xml file 177 Subnode Limitations for autonomous function . . 178 Binary Path attribute of the Windows OS agent does not show a value 179 Installing pre-v6.2.1 Monitoring Agent for Windows OS onto a v6.2.1 or later monitoring server inadvertently unconfigures the monitoring server 179 OS agent restarted unexpectedly on heavily loaded systems 179 Calendar entries overlap 180 Receive an error when deploying an System Service Monitor agent 180 The Agent Service Interface is not globalized . . . 180 Some attribute group names are unintelligible from the History Collection Configuration window . . 180 History collection fails to display the most recent 24 hours of data 180 Situations with attributes from more than 1 group not supported with autonomous agent . . . . . 181 Failure when importing situation xml file edited with WordPad 181 Printer details of another system are displayed on the Tivoli Enterprise Portal 181 CTIRA_MAX_RECONNECT_TRIES environment variable is now obsolete 181 Agent goes offline after removing history path . . 182 Override button is not present for a situation. . . 182 Agent's Management Definition View columns are not showing data 182 There is a situation distribution discrepancy if there is a hub monitoring server outage when one or more remote monitoring servers remain active . 182 Installing v6.2.2 agent application support on a monitoring server for a prior release causes agents to fail 182 Installing backlevel Windows OS agent on existing environment causes monitoring server not to start . 182 SNMP trap Sendto fails 183 Situation overrides cannot be used to disable situations on specific systems at specific times . . 183 Situation or calendar name in thresholds.xml file appears incorrect 183 BAROC file is missing for IBM Tivoli Monitoring 5.x Endpoint situations 183 The target host name, platform, and version information is not displayed for the deployment status in the CLI or the workspace 184 Agent upgrade and restart using non-root . . . . 184 After installing and configuring a monitoring agent, it fails to start 186 situation_fullname slot missing for delete events 186 Logs are using the situation ID string instead of the display name 186 If a managed system list is removed for a situation, the situation stops 187 Descriptions are not displayed for default situations 187
![](/manual_guide/products/ibm-e027sllh-troubleshooting-guide-7c8d102/10.png)