DX Infrastructure Manager

Expand all | Collapse all

robot not starting after windows patching

  • 1.  robot not starting after windows patching

    Posted 2 days ago
    Hi all,

    Just curious if anyone has noticed more "Robot x is inactive" alarms over the past few weeks? As our fleet is being patched and rebooted, the nimsoft service is occasionally failing to start:


    If we manually set the service to restart after first/second failure in the services recovery tab - it seems to be ok, but I worry that any subsequent robot updates will remove those settings.

    Cheers!


  • 2.  RE: robot not starting after windows patching

    Broadcom Employee
    Posted yesterday
    All of mine were updated, restarted, and robot came up fine.

    ------------------------------
    Support Engineer
    Broadcom
    ------------------------------



  • 3.  RE: robot not starting after windows patching

    Broadcom Employee
    Posted yesterday
    You still may want to research what the root cause is. Most likely your patch cause a possible pre-req service to delay or not start. Maybe one in your list, which should be fixable. Here is a doc I have used to delay the Niimsoft Service Start which will probably also fix your issue.

    https://knowledge.broadcom.com/external/article?articleId=97304


  • 4.  RE: robot not starting after windows patching

    Posted 21 hours ago
    For windows servers we have a policy to use "start delayed", especially on heavy servers (eg SQL, Sharepoint), which usually resolves start problems, if their is not an underlying cause.

    sc config nimbuswatcherservice start= delayed-auto

    And you are good to go

    ------------------------------
    Knows a little about UIM/DXim, AE, Automic
    ------------------------------