DX Unified Infrastructure Management

  • Private Community

  • 1.  Robot is inactive - how we can handle it?

    Posted Jan 02, 2017 07:11 AM

    Hi.

    I have seen the message: "Robot is inactive" for remote robots. I have remote secondary hub and tunnel server configured. I believe it was caused because the network latency.

    I'm thinking in change hub paremeter "hub_request_timeout", but I would like to know if it is the right parameter to change.

    Now it is set to 30s but I want to change to 120s.

    Are there other parameter I have to check? Is "hub_request_timeout" the right parameter to change?

     

    Regards,

     

    Nelson



  • 2.  Re: Robot is inactive - how we can handle it?

    Posted Jan 02, 2017 09:11 AM

    But robot inactive will trigger mostly if there is any issue with agent .May be the Nimsoft service may be stopped ,check the controller logs for more info.



  • 3.  Re: Robot is inactive - how we can handle it?

    Posted Jan 02, 2017 04:36 PM

    Yes,you can try updating the below timeout to control the robot inactive messages because of latency 

     



  • 4.  Re: Robot is inactive - how we can handle it?

    Posted Jan 03, 2017 09:31 AM

    Hi,

     

    It is also worth checking the niscache on the robots. If there is a lot of data in this dir then it can cause a "robot inactive" effect and still be active. 

    These can be cleared by either stopping the controller and removing the contents of the file or via the callback in the controller (in expert mode)