Troubleshooting
Problem
What TADDM logs should a customer start looking at for specific kinds of errors to determine the root cause?
Resolving The Problem
TADDM Logs
For specific kinds of errors, these are the logs to be reviewed for root cause:
Sensor Issue:
The split sensor log for the problematic discovery target
Product Console Issue:
Java console log from the client
ClientProxy.log from the server
ViewManager.log from the server
ApiServer.log from the server
Domain Manager Issue:
tomcat.log from the server
ApiServer.log from the server
API Issue:
ApiServer.log from the server
TopologyManager.log from the server
Storage Error:
DiscoverObserver.log from the server
TopologyManager.log from the server
Change History:
ChangeManager.log from the server
MonitorStateManager.log from the server
Startup issue:
tomcat.log from the server
all of the logs from dist/log/services
Discovery Hung (no Topology Build started):
DiscoverManager.log from the server
DiscoverObserver.log from the server
ProcessFlowManager.log from the server
ECMDB sync issue:
TopologyManager.log from the domain server
Synchronizer.log from the ecmdb server
TopologyBuilder issue (including TopologyBuilder hangs at less than 100% complete):
TopologyBuilder.log from the server
ProcessFlowManager.log from the server
TopologyBuilder hang at 100% complete:
ChangeManager.log from the server
MonitorStateManager.log from the server
ProcessFlowManager.log from the server
Product Synonym
TADDM
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21635936