DX UIM install issues on RHEL8 - 13 java probes have no port and cannot access archive
search cancel

DX UIM install issues on RHEL8 - 13 java probes have no port and cannot access archive

book

Article ID: 261041

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM) CA Unified Infrastructure Management On-Premise (Nimsoft / UIM) CA Unified Infrastructure Management SaaS (Nimsoft / UIM)

Issue/Introduction

We've freshly installed DX UIM on a Primary hub, but are unable to access the archive through the Admin Console and various java probes including the Automated Deployment Engine are showing as yellow in the Admin Console probes overview.


In the Infrastructure Manager (IM), the same java probes were displayed as green and had PIDs but no ports. We also noticed that at times, 1 or more of the java probe PIDs were very high values which seemed unusual.

Environment

  • Release: UIM 20.4
  • hub, any version
  • RHEL 8
  • Fresh, new install in POC environment
  • MySQL 5.7

Cause

  • hub truncating the probe names due to the NimBUS address length being too long
  • During the installation the customer used the defaults that the installer suggested for the Domain Name, Primary Hub Name and Primary Robot Name but the strings were already too long
  • The NimBUS address includes both the full robot address and the probe_name and the total combined length must not be more than 128 characters
  • The UIM Server installer uses defaults but the domain/hub names the customer already had planned were very long. So the final length of the NimBUS addresses (domain/hub/robot/probe) surpassed the allowable NimBUS address length of 128 for a subset of java (CORE infrastructure/service) probes.  
  • Once the probe name was added to the end of the NimBUS address during the initial installation of the UIM server, it became too long (for 13 longer-named java probes, but only a subset of the java probes), e.g., baseline_engine,  maintenance_mode, prediction_engine, automated_deployment_engine, etc.

Resolution

hub.log

hub: Warning! probeport2pds: Exceeded buffer size. Truncated string /<domain>/<hub>/<robot>/discovery_age
hub: Warning! probeport2pds: Exceeded buffer size. Truncated string /<domain>/<hub>/<robot>/prediction_en
hub: Warning! probeport2pds: Exceeded buffer size. Truncated string /<domain>/<hub>/<robot>/baseline_engi
hub: Warning! probeport2pds: Exceeded buffer size. Truncated string /<domain>/<hub>/<robot>/alarm_enrichm

NimBUS address for a small subset of java probes with names longer than 13 characters, was longer than a total of 128 characters and the hub was truncating the probe names down to 127.

Example (note the length of the NiBUS address was 127 chars).

NimBUS address-> <Domain/hub/robot/probe>

Character lengths-> 40, 37,33,13, for a total of 123 characters plus the slashes = 127

  • Once the NimBUS address was shortened, instead of using the suggested defaults during the re-installation, the issue disappeared.
  • The NimBUS address string limit is 128 - hub complains, as you can see from the hub.log, and truncates the probe name at the end of the string.
  • So to avoid the problem, the customer had to reinstall UIM using shorter domain/hub names.
  • The resolution was to install from scratch again but this time use shorter domain and hub names so that the NimBUS address for some of the probes didn't surpass 128 characters.

Additional Information

  • Suggestion made to Development that the hub installer generates an error if the combination of names does not leave enough room for the probe names.
  • NimBUS address character limit:
    • The NimBUS address includes the full domain, hub and robot address and the probe_name and the total combined length must NOT be more than 128 characters.
    • The underlying issue was that the total, final length of the NimBUS address was too long (128 characters).
Powered by Wolken Software