Single robot failed connection to hub.

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

Robot unable to connect to hub: error in controller log below and could not change the loglevel to level 5

----- Robot controller 7.80 [Build 7.80.3132, Jun  1 2015] started -----
Aug 29 05:38:43:336 [4340] Controller:  Name   = XXXX, IP = XX.XX.XX.XX. Port = 48000
Aug 29 05:38:43:336 [4340] Controller:  OS     = Windows / Windows Server 2019 Standard, 64-bit / Service Pack 0 Build 17763
Aug 29 05:38:43:336 [4340] Controller:  Domain = none
Aug 29 05:38:43:336 [4340] Controller:  Loglevel = 0, Logfile = controller.log
Aug 29 05:38:43:383 [4340] Controller:  Running as user SYSTEM
Aug 29 05:38:43:383 [4340] Controller: ----- 
Aug 29 05:38:43:383 [4340] Controller: Stopping processes from previous run
Aug 29 05:38:43:383 [4340] Controller: ProcessControl: Sending ^C signal to spooler (8872)...
Aug 29 05:38:43:445 [4340] Controller: ProcessControl: Unable to send stop signal to process spooler (8872)
Aug 29 05:38:43:445 [4340] Controller: ProcessControl: Process 8872 not found
Aug 29 05:38:43:445 [4340] Controller: ProcessControl: Sending ^C signal to hdb (8660)...
Aug 29 05:38:43:445 [4340] Controller: ProcessControl: Unable to send stop signal to process hdb (8660)
Aug 29 05:38:43:445 [4340] Controller: ProcessControl: Process 8660 not found
Aug 29 05:38:43:445 [4340] Controller: Controller on nairvdc01 port 48000 started

Environment

Release : 20.3

Component : UNIFIED INFRASTRUCTURE MGMT

Resolution

Copied and edited the robot config file from a working robot and connectivity was restored.