Automated Deployment Engine is very slow

[Legacy User]

Hi Guys!

 

I have a problem when I try to deploy a robot in USM, like the title said the ADE probe is very slow. When I check the log, I found the problem is in the process of copying "nimsoft-robot-x64.exe". The file is only 14MB, but the copying process can take more than 4 hours. This problem only happens when I deploy the robot to Windows, when I deploy the robot to Linux everything run smoothly.

 

I've tried the step that I found in this KB, but it still does not help.

Automated Deployment Engine is very slow or timing out.

USM Deployment Wizard Fails

 

Here's the logs on level 3 :

04182018 11:23:02,284 [AsyncTracker] INFO JobHandle - JobId: 8b4309fe5e4046dab2ed16579c37a1a2 1 tasks remaining...
04182018 11:23:04,021 [pool-4-thread-1] INFO AbstractDeploymentStrategy - Executing command Preprocess on target cauimdb
04182018 11:23:04,024 [pool-4-thread-1] INFO WindowsStrategy$Preprocess - Checking cauimdb for NimbusWatcherService...
04182018 11:23:04,026 [pool-4-thread-1] INFO WindowsTransport - Executing command isServiceRunning NimbusWatcherService on target cauimdb
04182018 11:23:04,183 [pool-4-thread-1] INFO WindowsStrategy$Preprocess - Robot is not running on: cauimdb
04182018 11:23:04,185 [pool-4-thread-1] INFO AbstractDeploymentStrategy - Executing command Preclean on target cauimdb
04182018 11:23:04,187 [pool-4-thread-1] INFO WindowsStrategy$Preclean - Removing previous temporary resources nms-robot-vars.cfg and nimsoft-robot-x64.exe
04182018 11:23:04,188 [pool-4-thread-1] INFO WindowsTransport - Executing command del C:\tmp\nms-robot-vars.cfg on target cauimdb
04182018 11:23:04,205 [pool-4-thread-1] INFO WindowsTransport - Executing command del C:\tmp\nms-robot-vars*.txt on target cauimdb
04182018 11:23:04,217 [pool-4-thread-1] INFO WindowsTransport - Executing command del C:\tmp\nimsoft-robot-x64.exe on target cauimdb
04182018 11:23:04,237 [pool-4-thread-1] INFO WindowsTransport - Executing command rmdir C:\tmp\ on target cauimdb
04182018 11:23:04,263 [pool-4-thread-1] INFO WindowsStrategy$Preclean - Removed nms-robot-vars.cfg :true
04182018 11:23:04,264 [pool-4-thread-1] INFO WindowsStrategy$Preclean - Removed nms-robot-vars*.txt files :true
04182018 11:23:04,264 [pool-4-thread-1] INFO WindowsStrategy$Preclean - Removed nimsoft-robot-x64.exe: true
04182018 11:23:04,266 [pool-4-thread-1] INFO WindowsStrategy$Preclean - Removed C:\tmp\: true
04182018 11:23:04,266 [pool-4-thread-1] INFO AbstractDeploymentStrategy - Executing command Copy on target cauimdb
04182018 11:23:04,691 [pool-4-thread-1] INFO ConfigCreate - Writing out config information for cauimdb to temporary log file...
04182018 11:23:04,694 [pool-4-thread-1] INFO WindowsStrategy$Copy - Creating temporary directory "C:\tmp\"
04182018 11:23:04,695 [pool-4-thread-1] INFO WindowsTransport - Executing command mkdir "C:\tmp\" on target cauimdb
04182018 11:23:06,706 [pool-4-thread-1] INFO WindowsStrategy$Copy - Creating network share: net share robot_share="C:\tmp" /GRANT:administrator,Full
04182018 11:23:06,707 [pool-4-thread-1] INFO WindowsTransport - Executing command net share robot_share="C:\tmp" /GRANT:administrator,Full on target cauimdb
04182018 11:23:13,719 [pool-4-thread-1] INFO WindowsStrategy$Copy - Copying exe "C:\Program Files (x86)\Nimsoft\probes\service\automated_deployment_engine\ade_package_temp\e8c828a0-7128-455d-ae7b-fa6414cc4f90\generic\nimsoft-robot-x64.exe" and answer file to cauimdb\robot_share

 

Thank you!

[RowanCollis]

Do you have some low priority set for SMB traffic on your network ?

 

[Legacy User]

No, I don't. I've tried transferring a 15mb file from the primary hub to the target computer it could be finished in less than 1 minute.

[Gene Howard]

you might try following the steps in the logs, create temp directory and share then do a copy and see how long that takes.

We have seen where antivirus on the target machine can cause a slow down as well.

[Legacy User]

I've tried that step, I copied the "nimsoft-robot-x64.exe" file to the target computer for less than 5 seconds. Currently I do not install any antivirus on this computer. Here's the logs on level 5 :

 

04192018 11:19:29,786 [pool-4-thread-1] INFO WindowsStrategy$Copy - Copying exe "C:\Program Files (x86)\Nimsoft\probes\service\automated_deployment_engine\ade_package_temp\7704e266-78f7-42d6-a3ca-de6eb42f520e\generic\nimsoft-robot-x64.exe" and answer file to cauimdb\robot_share
04192018 11:19:38,116 [attach_socket] TRACE AutomatedDeploymentEngineProbe - Retrieving job_ids for type 'host'
04192018 11:19:38,119 [attach_socket] TRACE TrackerUtil - Creating JobID list PDS...
04192018 11:19:38,119 [attach_socket] TRACE TrackerUtil - JobID retrieved : f70d5d50b80441d588cafb528ba7e447
04192018 11:19:38,119 [attach_socket] TRACE TrackerUtil - JobID retrieved : e987093fd8e744c7b88a8d54e6d39286
04192018 11:19:38,124 [attach_socket] TRACE AutomatedDeploymentEngineProbe - Retrieving status message(s) for f70d5d50b80441d588cafb528ba7e447 using Locale(en_US)
04192018 11:19:38,124 [attach_socket] TRACE ADEH2Dal - Retrieved DBJob from database -> DBJob{jobId='f70d5d50b80441d588cafb528ba7e447', jobName='Deploy robot to cauimdb', jobDescription='Automated deployment job Created at 1524161957083', startTime=1524161957918, stopTime=0, jobStatus='Running'}
04192018 11:19:38,125 [attach_socket] TRACE TrackerUtil - -- createPSDForDBTask -- retrieving status message using Locale(en_US)
04192018 11:19:38,127 [attach_socket] TRACE TrackerUtil - -- createPDSForDBTask -- retrieving status message for using Locale(en_US) failed. Using default Locale(en_US)
04192018 11:19:38,128 [attach_socket] TRACE AutomatedDeploymentEngineProbe - ADE - get_status callback PDS dump:
04192018 11:19:40,660 [FileMonitorThread] TRACE FileMonitor - File C:\Program Files (x86)\Nimsoft\probes\service\automated_deployment_engine\host-profiles.xml has not changed. Deployment cancelled.
04192018 11:19:40,661 [FileMonitorThread] TRACE FileMonitor - File C:\Program Files (x86)\Nimsoft\probes\service\automated_deployment_engine\submit_job.xml has not changed. Deployment cancelled.

[Legacy User]

Thanks for the answer, this case is solved!!
The problem is very simple, because the time on the target computer is out of sync with the actual time.