Stalled discovery runs

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

To identify 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 considered 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 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.

To restart or continue

At the next scheduled scan window, any runs that are on hold or blocked will continue or restart, depending on whether all endpoints have been started or not. The following happens:

  • Scan fails to complete in scan window and all endpoints have not been started. Scan continues at next window.
  • Scan fails to complete in scan window and all endpoints have been started. Scan restarts at next window.

To identify locked and on hold runs in the UI

The Currently Processing Runs tab of the Discovery Status window 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 137.72.94.27 and it is blocked because the DiscoveryRuncommand.DiscoveryRuncommand pattern is attempting to access another endpoint (137.72.94.219) 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 to display the Edit an Existing Run dialog box.

To view the status of the Reasoning service by using the tw_reasoning_status 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.

Automatic use of tw_reasoningstatus

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.

Option

Description

--waiting, -w

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

--waiting-full

Expands the information provided by the -waiting option 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.

Example of viewing the status of the Reasoning service

  1. On the command line, type the following:
    $TIDEWAY/bin/tw_reasoningstatus --username joe
  2. 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

Comments