• State Not Answered
  • Locked Locked
  • Replies 6 replies
  • Subscribers 93 subscribers
  • Views 5850 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

JobServer strange process step

delonge
over 7 years ago

 Hi everyone,

Lately while checking the logs of my job server I've noticed this strange process step that keeps appearing :

 

Does anyone knows what this means?

FYI, this process step appears hundreds of times, as if it was in an infinite loop.

What worries me the most is the message "Process step uuid not found. Set MISSING state". I can't figure out what this message means.

Furthermore, this is causing the jobs in the job queue to take an eternity to execute.

Thank you in advance for your help.

Regards.

Parents
  • 0 over 7 years ago

    The processes with the task CheckJob will be generated, when you do have long running jobs on the job services that haven't sent a status back into the queue.

    The system will check after a configurable amount of time if the job is still running at the job service that fetched the job into it's internal cache (status of the process step is Loaded or Processing).

    The result MISSING from the CheckJob execution states, that the process step couldn't be found executing on the job service.

    The configuration parameter Common\Jobservice\LoadedJobsTimeOut allows you to tune the check interval. You could try to increase that to see, if the number of recurring CheckJob execution decrease.

    For any further help, it would be great to know the version of One Identity Manager.

    You could contact the product support as well for any additional assistance.

Reply
  • 0 over 7 years ago

    The processes with the task CheckJob will be generated, when you do have long running jobs on the job services that haven't sent a status back into the queue.

    The system will check after a configurable amount of time if the job is still running at the job service that fetched the job into it's internal cache (status of the process step is Loaded or Processing).

    The result MISSING from the CheckJob execution states, that the process step couldn't be found executing on the job service.

    The configuration parameter Common\Jobservice\LoadedJobsTimeOut allows you to tune the check interval. You could try to increase that to see, if the number of recurring CheckJob execution decrease.

    For any further help, it would be great to know the version of One Identity Manager.

    You could contact the product support as well for any additional assistance.

Children
No Data