/build/static/layout/Breadcrumb_cap_w.png
06/24/2019 407 views

Is there any way to have failed post install tasks automatically retry the failed task?

1 Comment   [ + ] Show comment

Comments

  • Is best to troubleshoot why it failed....

    See:

    https://www.itninja.com/question/detailed-error-logs-of-failed-tasks


Community Chosen Answer

2

No when that happens it normally it needs user intervention.  Why keep retrying the same wrong thing it should consistently give the same failure?

You can have it continue on error but you will never know it failed a step unless you go digging thru logs for each deployment.

Answered 06/25/2019 by: SMal.tmcc
Red Belt

  • See that’s the thing, all the scripts have been tested and work fine at our main site. Once on the RSAs different scripts begin to fail and the frustration comes in when the tech needs to retry a failed task 3 or 4 times before it finally works.

All Answers

1

Here we have slow network nic driver load sometimes due to negotiation on speed still happening after a task reboots.  I cured that timing problem by adding a ksleep state to slow down the tasks some.  This file is on your kbox and is ok to use as long as you have a licensed SDA.


Answered 06/25/2019 by: SMal.tmcc
Red Belt

  • would I add this as part of the post-install tasks? Would you mind showing me how I think this may help with the issues I am experiencing?
    • You say you can retry a few times and it works. That points in the direction of timing issues. You could have another background install in progress and after it finishes you can get the task to work. Something is not loaded fully due to the machine being slower and is not ready yet.

      You need to narrow the problem down.

      Does this problem occur on the next task after the previous task was checked to reboot.
      That points to local slowness causing problems and the machine is not ready yet after boot

      Does this happen on tasks with attachments could be file access to RSA vs SDA
      Could be you need to re-sync due to version changes

      Does this always happen on certain tasks?
      Could be the previous task had multiple installers and the first one finished and sent a false signal to the SDA and it moved on to the next task and other chained installers are still running (autocad does this I do a ksleep 500 at end of autocad install and it now works as post.

      The placement of ksleep is determined by the type of problem. I have some at the beginning of tasks, some at end of tasks and a ksleep app task to slip in where needed.

      When it occurs you need to open a recovery command window and go the c:\kace -- applictions\### directory and run the task manually to see if it kicks an error ( do not use the silent switch)
0

can you share a couple of the tasks?  do you know what is failing on them?  sounds like a timing issue. also can you get the deployment xml for both the SDA and RSA on a deployment that contains a failing script?

One thing to try when one fails is to open a cmd window and go the c:\kace -- applictions\### directory and run the task manually to see what error it may kick.

To get the xml files:

In a browser point at a the deployment with a bad task and get the ID from the bottom of the browser screen.

Connect to \\ikbox\peinst\scripts (user .\admin password is samba pw)

get the xml file from there for the deployment that matches the ID


























Do the same thing on the RSA.

Answered 06/25/2019 by: SMal.tmcc
Red Belt