Bot stalls in High Density Robot configuration

Help Robot
#1

Hi there! We are running a High Density Robot configuration with our enterprise licensing - Orchestrator version 2019.10.14. Orchestrator and Robot Agent are on a different servers. Currently we have four bots which are set to trigger in every 1 min – running concurrently – Runtimes parameter is set to 5 . All of the hardware and software specifications for these servers are higher than UiPath’s recommendation for High Density Robot configuration. We have an issue where the bots get stalled after certain period of time. At that point we either have to restart the Robot Agent Service or restart the server to bring everything back to normal state. But it repeats to the problem. We could not determine the trend of the time interval of failure. Server CPU, Memory, and Disk utilizations are all between 30 to 60% - never reaches to 100%. What could be root cause of this problem. Please advise how to troubleshoot? Has anyone run to similar issue? Please help.

#2

Only odd issues I’ve come across is over a RDP session the UiRobot host’s desktop/explorer.exe is flickering every seconds. Attempting to connect by local console fails and have only mitigated through a reboot.

Can we provide more details on what you mean by stalled?

  • Does the running processes ‘freeze’ up on a certain activity neither errorring out nor processing forward?
  • Does the schedule jobs start pending?

What information can you provide about the jobs and triggers?

  • Is it a single process scheduled 4 times every minute?
  • Single process schedule once every minute and allocated dynamically 4 times?
  • Four different processes each schedule once every minute?

What version of Software / OS are you running?

  • Orchestrator (19.10.14)
  • Robot ?
  • Windows ?

Up to date on your OS patches? Any changes or patches applied since you started seeing the issue?

Have you reviewed your UiPath Robot and Orchestrator logs within the Event Viewer?

You could try enabling low level tracing on the Robot, don’t forget to turn it off afterwards!

#3

@codemonkee Here is the information you have asked for:
•Does the running processes ‘freeze’ up on a certain activity neither errorring out nor processing forward?

  • I did not notice running process getting frozen. However, no new process will start from the Orchestrator or from the Robot Agent tray.
    •Does the schedule jobs start pending?
  • It shows as successful in job

What information can you provide about the jobs and triggers?
•Is it a single process scheduled 4 times every minute?

  • No. We have four processes - four bots - dedicated each of the processes to each bot.
    •Single process schedule once every minute and allocated dynamically 4 times?
    •Four different processes each schedule once every minute?
  • Yes, correct.

What version of Software / OS are you running?
•Orchestrator (19.10.14)

  • Yes, that’s the version we are using
    •Robot ?
  • I believe it’s 19.10.14 as well
    •Windows ?
  • Orchestrator - Windows 2016
  • Robot agent - Windows 2019

Once again, thanks for your time looking into it. Looking forward to hear from you soon.

#4

We were able to resolve the issue by setting “Login to Console” as false (disabled). High Density Robots requires this setting. Although this parameter is set to False or Disabled, I had to force it. Once done stall issue got resolved. Thanks to all for your time looking into it.

#5

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.