Troubleshooting
Problem
How to trace a TADDM discovery run?
Resolving The Problem
You can trace the phases of discovery from when a discovery starts to when the change history is updated and the topology dependencies are built. Each phase of a discovery is recorded in an associated log file.
Discovery run phase and log file
After you start a discovery, each discovery is assigned a unique identifier (run ID). A time stamp of YYYY-MM-DD-hh:mm:ss:SSS identifies the discovery run, for example, 20110517225225948. The YYYY-MM-DD portion represents the year, month, and day. The hh:mm:ss.sss represents the time of day on a 24-hour clock, carried out to the thousandths of a second. In the preceding example, the date is 2011/05/17 and the time is 22:52:25.948. You can use this identifier to create separate log files for each sensor in the $COLLATION_HOME/log/sensors directory. The time stamp is used within the log files.
During a discovery, the process flow manager monitors the state of the discovery and the state of the sensor events. The process flow manager also manages the hand off from one service to another. The process flow activity is stored in the $COLLATION_HOME/log/services/ProcessFlowManager.log file on the discovery or domain server.
The following examples show various activities that are monitored by the process flow manager and how this information is stored in the log file.
- Starting discovery:
– 2011-05-17 22:53:01,643 ProcessFlowManager [RMI TCP Connection(42)-127.0.0.1] INFO processflowmgr.ProcessFlowManagerImpl - [ProcessFlowManagerImpl.I.0] startDiscovery() started discovery with run id 2,011,051,722,525,948 – 2011-05-17 22:53:01,643 ProcessFlowManager [RMI TCP Connection(42)-127.0.0.1] INFO processflowmgr.ProcessFlowManagerImpl - [ProcessFlowManagerImpl.I.22] startDiscovery() setting the discoveryRun's run id to 2,011,051,722,525,948 – 2011-05-17 22:53:01,973 ProcessFlowManager [RMI TCP Connection(42)-127.0.0.1] INFO processflowmgr.ProcessFlowManagerImpl - Discovery run, 2011051722525948 started with profile Level 2 Discovery
- Discovery done:
– 2011-05-17 22:56:11,689 ProcessFlowManager [RMI TCP Connection(45)-127.0.0.1] INFO processflowmgr.ProcessFlowManagerImpl - [ProcessFlowManagerImpl.I.36] discoveryDone(2,011,051,722,525,948) called by Discovery Manager
- Discovery event:
– 2011-05-17 22:53:49,901 ProcessFlowManager [RMI TCP Connection(45)-127.0.0.1] INFO processflowmgr.ProcessFlowManagerImpl - [ProcessFlowManagerImpl.I.32] discoveryProgress(2,011,051,722,525,948, Discovered - The CustomAppServerSensor (JavaServer 9.156.47.175:36750) sensor discovered the following: CustomAppServerResult, JavaServer,9.156.47.175:36750.) called by Discovery Manager
Topology builder phase and log file
The topology builder builds the relations and dependencies between the discovered items. The topology builder runs a list of agents that are listed in the $COLLATION_HOME/etc/TopologyBuilderConfigurationDefault.xml file. The topology agents run at specified intervals. However, events that occur during a discovery and when a discovery is completed can also trigger the topology builder. Each agent carries out a specific task, for example, consolidates, figures out dependencies, builds dependencies charts, and removes old information. The topology builder log files are stored in the: $COLLATION_HOME/log/services/TopologyBuilder.log file on the domain server, synchronization server, and primary storage server.
The following examples show the various stages when building relationships and shows how this information is stored in the log file.
- Starting builder execution:
– 2011-05-17 22:56:11,717 TopologyBuilder [RMI TCP Connection(158)-127.0.0.1] INFO cdb.TivoliStdMsgLogger - CTJOT0400I Topology builder is starting.
- Topobuilder done:
– 2011-05-17 23:16:39,429 TopologyBuilder [TopologyBuilderEngineThread$Dependency@0.5] INFO engine.TopologyBuilderEngine - Topology agent completed : all normally in seconds 30.367
- Moving to next TopoAgent:
– 2011-05-17 23:16:29,774 TopologyBuilder [TopologyBuilderEngineThread$Dependency@0.5] INFO cdb.TivoliStdMsgLogger - CTJOT0403I Topology builder agent class com.ibm.cdb.topomgr.topobuilder.agents.ComputerSystemConsolidationAgent is stopping. – 2011-05-17 23:16:30,078 TopologyBuilder [TopologyBuilderEngineThread$Dependency@0.5] INFO cdb.TivoliStdMsgLogger - CTJOT0402I Topology builder agent class com.ibm.cdb.topomgr.topobuilder.agents.ComputerSystemTypeAgent is starting.
If you find problems, for example the topology builder is hanging, check for the last started topology agent in the log file to identify the problem. If there are no entries in the TopologyBuilder.log file, check the entries in the TopologyManager.log file after the timestamp of the last started agent.
Other services and log files
The change manager processes events and updates the change history records. This processing is independent of the discovery phase; it receives events from other services, for example, the topology builder process and bulk load program. When you open a topology view, the view manager builds the structures that are required for the GUI to render the topology efficiently. The services logs are stored in the: $COLLATION_HOME/log/services directory. Each service log has the same name as the service for example, services/ChangeManager.log file.
The following examples show how this information is stored in the service log files.
- ChangeManager:
–2011-05-19 13:22:42,342 ChangeManager [ChgWork-1] INFO changemgr. ChangeManagerPersisterImpl - [ChangeManagerPersister.I.3] Got a create or delete event
- ViewManager:
–2011-05-19 16:37:22,428 ViewManager [RMI TCP Connection(174)-127.0.0.1] INFO viewmgr.ViewMetaLoader - [ViewMetaLoader.I.31] getViewMeta() found view meta definition for view Business Application Topology
Product Synonym
TADDM