IBM E027SLL-H Troubleshooting Guide - Page 9
Monitoring server, troubleshooting - history
View all IBM E027SLL-H manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 9 highlights
Portal server performance is slow 149 Cannot create a Tivoli Enterprise Portal Server database 149 You receive a KFW error when a query is sent to more than 200 managed systems 150 Non-hub situations are not associated at the Tivoli Enterprise Portal Server level 151 Starting and stopping the Eclipse Help Server . . 151 Non-root stopping or starting agents causes problems 151 Root password is not accepted during non-root Tivoli Enterprise Portal Server configuration . . . 151 Corba user exception is included in the portal server log when creating situations 152 Stopping or starting the eWAS subcomponent of the portal server 152 Chapter 9. Monitoring server troubleshooting 153 Messages related to the index file are displayed when the agent fails back to a remote monitoring server 153 A generic RPC communications error is received when issuing a long-running tacmd execute command 153 Troubleshooting monitoring server problems on distributed systems 153 The CT_GET request method fails in SOAP queries with a V6.2.3 hub monitoring server, a remote hub monitoring server earlier than V6.2.3, and an agent connected to a remote monitoring server 154 Exposure of passwords in the clear . . . . . 154 Receive a seeding failed message 154 High monitoring server CPU after restarting with Warehouse Proxy Agents configured . . . 154 Upgrade inconsistency between the History and Object windows 155 Attribute groups started for collection on the managed systems should not be available on the monitoring server list 155 To decrypt a password, KDS_VALIDATE_EXT='Y' is required . . . . 156 Remote Tivoli Enterprise Monitoring Server consumes high CPU when large number of agents connect 156 Unable to start the Tivoli Enterprise Monitoring Server after the kdsmain process is terminated abnormally 156 THRESHOLDS.XML and Tivoli Enterprise Monitoring Server table not cleaned when managed system override is removed . . . . 157 Situations fail to trigger for attributes by applying group function 157 Monitoring server application support completes all seeding functions but might crash as the program is exiting 157 tacmd login fails when monitoring server is configured with LDAP authentication . . . . 158 Some agents are displayed in the Service Console list that are not accessible from that user interface 159 tacmd login fails after hub monitoring server is recycled 159 tacmd and SOAP are not able to connect . . . 160 The system crashes when attempting a bulk import or export command 160 Monitoring server fails to start, but then does after a reboot 160 Remote monitoring server lost connection to the hub and all agents display offline . . . . . 161 After the set timeout, the Tivoli Enterprise Monitoring Server is still pending . . . . . 161 Providing the wrong path to configuration files during LDAP configuration causes the Tivoli Enterprise Portal login window to hang . . . 161 Crash on Linux remote monitoring server during hub failover to Hot Standby . . . . . 162 HUB Tivoli Enterprise Monitoring Server quiesce prevents the display of the data collected by the attached Tivoli Enterprise Monitoring Agents 162 During installation of a remote Tivoli Enterprise Monitoring Server on a Windows system, the agent support is applied, but fails . . . . . 162 Using a Deploy Group with addSystem or updateAgent commands 163 Tivoli Enterprise Monitoring Server requires restart if you issue itmcmd server stop/start commands when you are already logged on . . 163 Log indicates hub monitoring servers are down when they are up 163 The Platform view in the Manage Tivoli Enterprise Monitoring Services panel shows the Tivoli Enterprise Monitoring Server as running as a 32 bit application, but my agents are shown as running as 64 bit applications 164 Tivoli Enterprise Monitoring Server does not release memory after running a large SQL query 164 SQL queries with more than 200 OR predicates do not complete 164 Tivoli Enterprise Monitoring Server aborts unexpectedly when exiting the telnet session used to start it 165 KCIIN0084E Timeout appears while waiting for Tivoli Enterprise Monitoring Server to start on AIX 5.3 165 In a hot standby (FTO) environment, commands to a mirror hub might not return hub records after reconnection 165 A deleted object is redisplayed when two hot standby (FTO) hubs reconnect 166 Troubleshooting monitoring server problems on z/OS systems 166 Receive Program KDFCINIT and Program FAXCMON messages 166 Contents vii