Troubleshooting unresponsive activities

If any activities such as exceptions, or scan file or patch policy deletion are unresponsive and stuck, use the steps in this topic to cancel such activities and run them again later. 

• • Unresponsive exceptions
  • Cancel background tasks for policy or scan file deletion
  • Tags not visible on the UI

Unresponsive exceptions

Issue symptoms and scope

Exceptions created for vulnerabilities may be unresponsive if the following issues are observed on the UI:

• On the start date of an exception the status is still shown as ENABLED and not ACTIVE. 
• After the end date of the exception, the exception status is still ACTIVE and not EXPIRED. 
• The in-progress states (Active-In-Progress, Expire-In-Progress, Disable-In-Progress, Delete-In-Progress) are unchanged for a long time. 

This can happen because the exception task has hung (reason could be resource crunch). In such a scenario you will need to cancel the activity using REST APIs. This will re-trigger the exception evaluation process.

This can happen , there may be a problem in the scheduler service and you may need to cancel the activity using REST APIs. 

Resolution

To cancel the current activity, use the following API call:TrueSight Automation Console: PUT/automation-console/api/v1/activities/cancel

The input parameter for this API is exception ID. Note that if an exception is not expired, using this workaround triggers the exception again. 

For details, see Using-REST-APIs. 

Cancel background tasks for policy or scan file deletion

Issue symptoms and scope

If you have deleted a patch policy or a vulnerability scan file from the UI and the status is unchanged for a long time, you may choose to cancel the operation and delete the policy or the scan file again. 

Resolution

To cancel the current policy deletion or scan file deletion activity, use the following REST API calls: 

1. Retrieve the activity status:
   GET/api/v1/activities/{id}
2. Cancel the activity:
   PUT/api/v1/activities/cancel
3. Retrieve the status post-cancellation:
   GET/api/v1/activities/{id}

After the post-cancellation status is shown as CANCELLED, the policy or the scan file is no longer deleted. You may choose to delete the policy/scan file again.  

For details, see Using-REST-APIs. 

Tags not visible on the UI

Issue symptoms and scope

If you added tags in the CSV file, imported them in Automation Console, and those tags are not displayed on the UI, then you may try to cancel the activity and import the file again. You can do this even if the logs show the status as completed.

Resolution

Cancel the activity and then import the file again. 

1. Retrieve the activity status:
   GET/api/v1/activities/{id}
2. Cancel the activity:
   PUT/api/v1/activities/cancel
3. Retrieve the status post-cancellation:
   GET/api/v1/activities/{id}

For details, see Using-REST-APIs.