Log File Analysis

Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

UCMDB/UD Application Probe logs provide extensive insights into the application/discovery health. Utilities like BareTail and BareGrep will help to read UCMDB logs from Windows servers.

Communication log for discovery jobs. Enabling communication logs for debugging discovery job failures helps to perform troubleshooting. Enabling communication logs will add overhead to the application performance of the system resources on the probes. Enable communication logs only when you want to debug the logs. Check job adapter configuration settings.

For a detailed description of the Create communication log setting and instructions on how to enable and view communication logs, see the Data Flow Management section of the UCMDB Help and DDMI to Universal Discovery Migration Walkthrough Guide.

DEBUG: Log levels in UCMDB are configurable by changing the log setting under the \conf\logs. No logs should ever be in DEBUG by default as it affects the system IO performance. Enable DEBUG mode only when performing troubleshooting.

Log File Analysis (Patterns to Look For)

Wrong DB Credentials: error.log, cmdb.dal.log

com.mercury.topaz.cmdb.server.manage.dal.CmdbDalException: 
 [ErrorCode [2]  Couldn't connect to database ]:Error getting connection from pool Caused by: com.mercury.jdbc.sqlserverbase.ddd0: [mercury][SQLServer JDBC Driver][SQLServer] Login failed for user 'sa'.at com.mercury.jdbc.sqlserverbase.ddb9.b(Unknown Source)

Database Down: error.log, cmdb.dal.log

Caused by:

com.mercury.topaz.cmdb.shared.base.CmdbException: [ErrorCode [-2147483648] undefined error code] com.mercury.jdbc.sqlserverbase.ddd0: [mercury][SQLServer JDBC Driver] Error establishing socket to host and port: myd-vm02162:1433.

Reason: Connection refused

DB Timeout: error.log, cmdb.dal.log

Timeout expired. Check DDM logs to see what's taking so long java.sql.SQLTimeoutException: [mercury][SQLServer JDBC Driver]Execution timeout expired java.sql.SQLTimeoutException: [mercury][Oracle JDBC Driver]Execution timeout expired.

Server out of memory : error.log , wrapper.log

.......  Dumping heap to java_pid7624.hprof ...
java.lang.OutOfMemoryError : Java heap space

Java heap out of memory: wrapper.log

java.lang.OutOfMemoryError: GC overhead limit exceeded
java.lang.OutOfMemoryError: Java heap space

Failed to start server: wrapper.log

...INFO  - Starting cmdb server
...
FATAL  | wrapper  | 2014/09/22 15:31:21.322 | There were 10 failed launches in a row, each lasting less than 300 seconds.  Giving up

JVM Hung: wrapper.log

...JVM appears hung: Timed out waiting for signal from JVM.
...
ERROR  | wrapper  | 2014/08/28 11:11:55.417 |  JVM did not exit on request, terminated