Manually deleting discovery tasks

If the crawler is unresponsive for any reason when a discovery task is deleted from the management server, the crawler is not alerted that the task is deleted. When the

crawler becomes responsive, it continues to run the discovery scan as scheduled and consume unnecessary resources.

To avoid these repercussions, manually delete the task from its associated crawler.

The Forcepoint Security Manager warns you in this situation, and asks if you want to continue. To delete the task:

1. Use either of the methods below to identify the ID of the job to delete:
   • Go to the Main > Logs > System Log page in the Data Security module of the Security Manager and search for the entry stating the task was deleted. For example:

     The task Discovery_Name ID 8e76b07c-e8e5-43b7-b991- 9fc2e8da8793 was deleted from the Forcepoint Security Manager, but not from the crawler, Crawler_Name 10.201.33.1.

   • Log on to the crawler machine associated with the discovery task, then:
     1. Go to the %DSS_HOME%/DiscoveryJobs folder.
     2. To search for the relevant task and ID, open each job, one at a time, and examine the first line of its definition.xml file.

        For example, the first line of one file might show:

        <job type="discovery" id="3178b4f9-96fe-4554-ad1d- eaa29fa23374" name="ora3" altID="168476">

        This means that task “ora3” has ID 3178b4f9-96fe-4554-ad1d- eaa29fa23374.

2. To delete the job, log on to the crawler machine and go the %DSS_HOME%/ packages/Services folder.
3. Run the following command:

   Python WorkSchedulerWebServiceClient.pyc -o deleteJob -j #jobId#

   Here, jobID is the ID number identified in Step 1.