Stalled discovery runs

When a discovery run is scheduled for a particular scan range, the time in which it is scheduled is called its scan window. Scheduled discovery of the scan range can only take place in that open scan window.

Stalled discovery runs

Some discovery runs can appear to be stalled. This occurs in one of two situations:

  • a discovery run has not completed within its scheduled scan window. This scan is termed on hold. The run continues or restarts at the next scan window.
  • discovering an endpoint requires additional discovery on another endpoint which is not currently in an open scan window. This scan is termed blocked.
    When the scan window for the other endpoint opens, the endpoint is scanned irrespective of whether the first endpoint is in an open scan window or not.

In previous releases, there was no way of determining that these situations were causing a run to stall.

Restart or continue

At the next scheduled scan window, any on hold or blocked runs will continue or restart, depending on whether all endpoints have been started or not. The behavior change introduced in BMC Atrium Discovery 8.2.1 is described below:

  • Scan fails to complete in scan window and all endpoints have notbeen started
    • Pre-8.2.1: scan continues at next window.
    • 8.2.1 and later: scan continues at next window.
  • Scan fails to complete in scan window and allendpoints have been started
    • Pre-8.2.1: scan continues at next window.
    • 8.2.1 and later: scan restarts at next window.

Blocked and on hold runs in the UI

The Currently Processing Runs tab of the Discovery Status window now displays a red (on hold) notice if a run is on hold and a red (blocked) notice if a run is blocked.

Blocked runs

Click the (blocked) notice. A dialog box is displayed showing why the discovery run is blocked.

The blocked endpoint is shown and the reason for it being blocked is given. In the preceding example, the blocked endpoint is and it is blocked because the DiscoveryRuncommand.DiscoveryRuncommand pattern is attempting to access another endpoint ( which is currently outside a scan window.

On hold runs

Click anywhere in the row of the on hold run to display the Discovery Run page for that run. To check the scanning window:

  1. From the Discovery Status page click the Scheduled Runs tab.
  2. The timing information for each scheduled run is shown in a table.

If you want to edit the discovery run, click its entry in the table and the Edit an Existing Run dialog box is displayed.

The tw_reasoning_status command line utility

The tw_reasoningstatus utility enables you to view the status of the Reasoning service. Typically this utility is used by Customer Support as a troubleshooting tool for investigating possible problems.


Reasoning runs the same status check automatically every 15 minutes and outputs the results in the tw_svc_reasoning.log file.

To use the utility, type the following command at the $TIDEWAY/bin/ directory:

tw_reasoningstatus [options] 

where options are either the command described in the following table or the standard, inherited options detailed in Using command line utilities.

Command Line Option


--waiting, -w

Lists information for all endpoints which are on hold waiting for information from the discovery of a different endpoint.


Expands the information provided by --waiting to include information on all endpoints being held waiting for discovery. This option is ignored if --waiting is not specified.

-u, --username=NAME

Specifies the name of the BMC Atrium Discovery user. If no name is specified, BMC Atrium Discovery uses the default, system.

User example

In the following example, you can view the status of the reasoning service.

Viewing the status of the Reasoning service

To view the status of the Reasoning service, type the following command:

$TIDEWAY/bin/tw_reasoningstatus --username joe

If you do not provide a password, you are prompted for one.
After providing a password, a status is displayed that includes information about engine status, pool state, queue length, and so forth. The output is saved in the tw_svc_reasoning.log file.

Was this page helpful? Yes No Submitting... Thank you