Perform Identity Request Maintenance task not getting started

IdentityIQ (IIQ) IIQ Discussion and Questions
,
1

Which IIQ version are you inquiring about?

8.4P3

Please share any images or screenshots, if relevant.

image
image1799×728 28.8 KB

Please share any other relevant files that may be required (for example, logs).

performIdentityReqLogs.txt (173.5 KB)

Share all details about your problem, including any error messages you may have received.

For a few days the identity request maintenance task has not been running; all partition threads are in a waiting state, so I tried to run without partition, but it is still showing as scanning. I’m not sure what happened, so please suggest I need to verify.

Thanks

Venu

2

Hi @venumgm235 - Make sure the task result from the current one is deleted and retry. Are the other tasks running properly?

3

Hi @venumgm235

Here is the cleanest way to get rid of stale or stuck tasks:

  1. Try terminating from the UI: If this works, great; however, it generally won’t work for these types of stale tasks.
  2. Use the Debug Page:
  • Navigate to TaskResult.
  • Search for Perform Identity Request Maintenance.
  • Select the stale task and click Delete.
  1. Restart Services:
  • Stop all application servers/services, including IQService.
  • Restart the Database.
  • Start the application servers/services and IQService.

Note: Ensure there are no other pending or in-progress tasks before proceeding.

  1. Run Maintenance task: Execute the Perform Identity Request Maintenance task.

Hopefully, this resolves the issue.

4

Hello @iiq-isc ,

After restart, the task is running, but what could be the reason? as it’s a PROD, we can’t restart every time, so how can we tackle this in the future?

Thanks

Venu

5

Hi @venumgm235

Thanks for the update; it’s good to hear that the issue is resolved. This is a very rare scenario.

As part of the root cause analysis: We need to examine various logs to see if there were performance issues due to low disk space or a network glitch. We need to determine what exactly caused the process to hang; it may have been a network connection issue.