Jump to content

ITOM Jobs stuck in Processing Output


Recommended Posts

Afternoon 

we are getting intermittent site of jobs getting stuck in the Processing Output status. Its not just the job below, it seems to be across all

image.png.54eccbd88d02595be681b8f713679f68.png

If you re-run the job type they complete successfully

It would be great if this could be looked into and we could understand if there is any monitoring that could let the supporting team know if jobs get stuck??

 

thanks

Andy

Link to post
Share on other sites

Hi@AndyGilly,  I believe that this is an issue we are currently aware of and is in the development queue for further investigation.   I will enquire into any progress  they we have made and request that it is given a higher priority.  Can you confirm that the issue is consistently exhibits that same behaviour?  In that initially it stalls and subsequent executions are successful.  Also does refreshing the GUI in the Job queue have any effect?

Regards,

Ricky

 

Link to post
Share on other sites

@AndyGilly, Can you review the SIS log (EspSisService.log), and check that the following lines exist for any of the stalled jobs:

2021-03-10 16:52:00Z [INFO]:[GENERAL]:[1164] Result: Success
2021-03-10 16:52:00Z [INFO]:[GENERAL]:[1164] Setting job 317 status to processingOutput
2021-03-10 16:52:00Z [INFO]:[GENERAL]:[1164] Setting job 317 status to succeeded

Regards,

Ricky

Link to post
Share on other sites

Morning @Ricky

below is what i can see in the log for the completion of that job

2021-03-10 16:53:09Z [INFO]:[GENERAL]:[5340] Result: Success

2021-03-10 16:53:09Z [INFO]:[GENERAL]:[5340] Setting job 317 status to processingOutput
2021-03-10 16:53:09Z [INFO]:[GENERAL]:[5340] Setting job 317 status to succeeded
2021-03-10 16:53:09Z [ERROR]:[COMMS]:[5340] The SIS authorization key is invalid
2021-03-10 16:53:09Z [ERROR]:[GENERAL]:[5340] Failed to update job status. Operation[automation::sisUpdateJobStatus] The SIS authorization key is invalid

thanks

Andy

Link to post
Share on other sites

Hi @AndyGilly, looks like the SIS authorization key is being reported as invalid for some reason, our dev team are looking into the issue and I will get back to you as soon as I get a response.  

Do you have more than one SIS and what is the pairing status of them in the Admin tool?

Regards,

Ricky

Link to post
Share on other sites

@AndyGillyThanks for the update. Have spoken with the Dev team and they suggest that the issue must be the result of some form of communication error.   I am currently in the process of organising access to the logs from yesterday, in order to investigate this further.   I may also require access to the logs located on the SIS sever on you're network, and may require them to sent over.  Due to the nature of the investigation I will be requesting that an Incident be raised on your behalf to track future progress, and will advise you of the incident reference.

Could you also confirm roughly when you first started to experience the reported behaviour?

Regards,

Ricky

Link to post
Share on other sites

Morning @Ricky

thanks for the update

We have only really started to put a higher volume of jobs through ITOM in the last couple of weeks and therefore the issue has been noticed more.

Although, I do think I have seen this behaviour pretty much since we started using ITOM

thanks

Andy

Link to post
Share on other sites
  • 1 month later...

Hi @Ricky

is there an update on PM00166852 please???

we have been doing some new starter testing today and have found the issue to be appearing more frequently. We cannot see any logic to the error occurring (differing jobs etc)

thanks

Andy

image.thumb.png.62988fc8116568d7ae585c0a5f3913ff.png

Link to post
Share on other sites

Hi @AndyGilly, Apologies for the delay in responding. I am still waiting for an update on this issue. I know that we have been able to identify the root cause of the problem and that the fix will be within the SIS. A release is due soon; however, I am still waiting for confirmation of the timeframe as I believe dependencies are holding back the release. I hope to get more information and hopefully an ETA later this week, and I will update you accordingly.
Regards,
Ricky

 

 

Link to post
Share on other sites

@AndyGillyI am still waiting for confirmation of the next version of the SIS release date that will contain the fix for the issue you are experiencing. I believe that there were discussions on this late last week, and I am still waiting for further details. Apologies for the delay, and as soon as I get some information, I will let you know.

Regards,
Ricky

 

  • Thanks 1
Link to post
Share on other sites

Morning @Ricky

it would be great to get an update, we are holding off putting our automated new starter process live until this fix is in & and I would like to plan our release if possible please

thanks

Andy

Link to post
Share on other sites

Hi @AndyGilly, I am still waiting for confirmation of a date when the fix will become available, but will give the dev team a poke to get some progress with this.

Regards,

Ricky

Link to post
Share on other sites

@AndyGilly, Have spoken with the dev team and they are hoping to get an SIS release out next week, which will contain the fixes required to resolve the issue.  I will post an update as soon as I can to confirm that the update has been pushed for release.

Regards,

Ricky

 

  • Like 1
Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...