Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.
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 |
|
|
Either word in a topic |
|
|
Topics that do not contain a specific word or phrase |
|
|
Topics that contain one string and do not contain another | ^ (caret) |
cat ^ mouse
|
A combination of search types | ( ) parentheses |
|
Data Flow Probe Log Files
Data Flow Probe logs store information about job activation that occurs on the Probe Gateway and Probe Manager. The log files can be accessed from the following location:
C:\UCMDB\DataFlowProbe\runtime\log
Note Alternatively, to access the Data Flow Probe's log files, log in to the JMX console (https://localhost:8453) and, from the main page, select the GeneralUtils mbean. Activating the executeLogGrabber function zips all the Data Flow Probe's log files. Save the .zip file locally on your client machine.
General Logs
WrapperProbeGw.log |
Records all the Probe's console output in a single log file.
|
probe-error.log |
Summary of the errors from the Probe.
|
wrapperLocal.log |
When running the Probe in separate mode (that is, the Probe Manager and Probe Gateway are installed on separate machines), a log file is also saved to the Probe Manager.
|
postgresql.log |
Displays database related error during the installation. Note If this log is empty, check in the Event Viewer logs. |
pg_upgrade.log |
Shows the running details of the pg_upgrade.bat script, including the details about PostgreSQL upgrade and table splitting. The log does not appear in the log folder by default. It appears only when you manually run the pg_upgrade.bat script or may appear when you select the upgrade option during probe installation.
|
probe_upgrade_conf_merge.log |
Shows the related information when probe upgrader merges configuration files.
|
probe_auto_upgrade.log |
Shows the related information when the probe auto upgrade agent upgrades a probe. It shows in the C:\UCMDB\DataFlowProbe\runtime\log\probeUpgradeLogs\<source_version>to<target_version> folder. For example: C:\UCMDB\DataFlowProbe\runtime\log\probeUpgradeLogs\10.32to2018.05. This log file is also sent to the UCMDB server and shows as <domain_name>_<probe_name>_auto_upgrade.log in the C:\UCMDB\UCMDBServer\runtime\log\probeUpgradeLogs\<source_version>to<target_version>\failed|success folder.
|
Probe Gateway Logs
probeGW-taskResults.log |
Records all the task results sent from the Probe Gateway to the server.
|
probeGW-tasks.log |
Records all the tasks received by the Probe Gateway.
|
Probe Manager Logs
probeMgr-performance.log |
Performance statistics dump, collected every predefined period of time, which includes memory information and thread pool statuses.
|
probeMgr-adaptersDebug.log |
Contains messages that are created following a job execution. |
Discovery Rules Engine Log Files
normalization.audit.log |
Logs information about the processing of the Discovery Rules Engine.
|
normalization.log |
Logs detailed information about the processing of the Discovery Rules Engine, enabling you to trace detailed information of the Discovery Rule Engine process.
|
We welcome your comments!
To open the configured email client on this computer, open an email window.
Otherwise, copy the information below to a web mail client, and send this email to cms-doc@microfocus.com.
Help Topic ID:
Product:
Topic Title:
Feedback: