DX IM - Unable to install Nimsoft robot on Ubuntu 18.04.5 LTS

book

Article ID: 221665

calendar_today

Updated On:

Products

DX Infrastructure Management

Issue/Introduction

Unable to install Nimsoft on Ubuntu 18.04.5 LTS

have followed below url without success

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

 

ug 10 11:07:56:373 1 Nimbus: 'controller' stopped (pid=15677) RET = 255
Aug 10 11:08:02:374 1 Nimbus: 'controller' started (pid=15700)
Aug 10 11:08:02:374 1 Nimbus: 'controller' started (pid=15700)
Aug 10 11:08:02:374 0 Nimbus: 'controller' FAILED to start (exec) (-1) Unknown error -1
Aug 10 11:08:04:374 1 Nimbus: 'controller' stopped (pid=15700) RET = 255
Aug 10 11:08:10:375 1 Nimbus: 'controller' started (pid=15721)
Aug 10 11:08:10:375 1 Nimbus: 'controller' started (pid=15721)
Aug 10 11:08:10:375 0 Nimbus: 'controller' FAILED to start (exec) (-1) Unknown error -1
Aug 10 11:08:12:375 1 Nimbus: 'controller' stopped (pid=15721) RET = 255
Aug 10 11:08:18:376 1 Nimbus: 'controller' started (pid=15735)
Aug 10 11:08:18:376 1 Nimbus: 'controller' started (pid=15735)
Aug 10 11:08:18:376 0 Nimbus: 'controller' FAILED to start (exec) (-1) Unknown error -1
Aug 10 11:08:20:376 1 Nimbus: 'controller' stopped (pid=15735) RET = 255
Aug 10 11:08:26:377 1 Nimbus: 'controller' started (pid=15744)
Aug 10 11:08:26:377 1 Nimbus: 'controller' started (pid=15744)
Aug 10 11:08:26:377 0 Nimbus: 'controller' FAILED to start (exec) (-1) Unknown error -1
Aug 10 11:08:28:377 1 Nimbus: 'controller' stopped (pid=15744) RET = 255
Aug 10 11:08:34:378 1 Nimbus: 'controller' started (pid=15775)
Aug 10 11:08:34:378 1 Nimbus: 'controller' started (pid=15775)
Aug 10 11:08:34:378 0 Nimbus: 'controller' FAILED to start (exec) (-1) Unknown error -1
Aug 10 11:08:36:378 1 Nimbus: 'controller' stopped (pid=15775) RET = 255
Aug 10 11:08:42:379 1 Nimbus: 'controller' started (pid=15789)
Aug 10 11:08:42:379 1 Nimbus: 'controller' started (pid=15789)
Aug 10 11:08:42:379 0 Nimbus: 'controller' FAILED to start (exec) (-1) Unknown error -1
Aug 10 11:08:44:379 1 Nimbus: 'controller' stopped (pid=15789) RET = 255
Aug 10 11:08:50:380 1 Nimbus: 'controller' started (pid=15804)
Aug 10 11:08:50:380 1 Nimbus: 'controller' started (pid=15804)
Aug 10 11:08:50:380 0 Nimbus: 'controller' FAILED to start (exec) (-1) Unknown error -1
Aug 10 11:08:52:380 1 Nimbus: 'controller' stopped (pid=15804) RET = 255
Aug 10 11:08:52:380 1 Nimbus: Too many retries used starting 'controller', next start in 1200 seconds
[email protected]:/opt/nimsoft/bin#
 
<controller>
   domain = MaaS2-Central-Domain
   robotip = 172.20.17.86
   robotname = SLOG-PROD-VM01
   robotip_alias = 
   controller_port = 
   spooler_port = 
   hubip = 172.20.49.7
   hubdomain = 
   first_probe_port = 48005
   hub = oim-ss-vm01
   hubrobotname = oim-ss-vm01
   hubport = 48002
   access_0 = 0
   access_1 = 1
   access_2 = 2
   access_3 = 3
   access_4 = 4
   secondary_domain = 
   secondary_hub = 
   secondary_hubrobotname = 
   secondary_hubip = 
   secondary_hubport = 
   secondary_hub_dns_name = 
   secondary_robotip_alias = 
   robot_mode = 
   os_user1 = mabrlAzure
   os_user2 = CA_Monitoring Service_2.0
   set_qos_source = 
   system_uptime_qos = 
   autoremove = 
   default_priority_level = 
   proxy_mode = 
   proxy_log = 
   hub_update_interval = 
   loglevel = 5
   logsize = 
   logfile = 
   config_lock_timeout = 
   port_alive_check = 
   port_alive_include_local = 
   startup_timeout = 
   suspend_on_loopback_only = 
   temporary_hub_broadcast = 
   do_not_broadcast = 
   unmanaged_security = 
   send_alive = 
   alarm_level_comfail_restart = 
   alarm_level_dispatch_error = 
   alarm_level_max_restarts = 
   alarm_level_start_error = 
   alarm_level_suspended = 
   alarm_level_timed_not_finished = 
   alarm_level_timed_error_return = 
   alarm_level_unregister = 
   alarm_level_request_error = 
   alarm_level_postinstall = 
   audit = 
   audit_max_config_size = 
   audit_checkpoint_count = 
   alarm_timeout = 
   wait_after_unregister = 
   tz_offset = 
   config_locking = 
   capture_output = 
   default_fail_window = 
   max_restarts = 
   ip_version = ipv4 ipv6
   ssl_mode = 0
   ssl_cipher = RC4-SHA
</controller>

- UIM version    20.3
- Primary hub version   9.33HF1
- Primary hub robot version  9.33HF1
- Primary hub system o/s  Windows Server 2012 R2
- HA probe version on primary  No HA probe

- Secondary hub version  9.33HF1
- Secondary hub robot version  9.33HF1
- Secondary hub system o/s  
- HA probe version on secondary Windows Server 2012 R2

Environment

Release : 20.3

Component : UIM - ROBOT

Resolution

https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/unified-infrastructure-management/20-3/installing/deploy-robots/install-multiple-robots-on-a-single-host.html#concept.dita_dd239f0edaffff94b8a528a7fd4e927fb72e8811_InstallMultipleRobotsonaLinuxHost