Operators Console Groups without number of contained devices just show 0
Article ID: 207173
Updated On:
Products
Issue/Introduction
In the "Groups" tab all groups are populated, but without number of contained devices:
When we run Developer Tools in the browser we get errors related to api (https://IP/operatorconsole_portlet/api/v2) with status code 500.
Environment
Release: 20.3.2
Component: OPERATOR CONSOLE
Cause
grouping-api-model-2.0.5.jar and grouping-api-service-local-2.0.5.jar files found in the location [UIM Install Path]\probes\service\wasp\lib\services of Operator Console robot were the cause of the issue.
They have now been replaced by grouping-api-model-2.0.6.jar and grouping-api-service-local-2.0.6.jar
The following errors are seen in the policy_management.log in the Operator Console robot:
2021-01-20 09:32:39,652 INFO com.ca.uim.policy.management.events.service.HeartBeatService:readConfig:142 [Catalina-utility-1] - HA Master is running at http://<masked_adminconsole_ip_when_creating_this_techdoc>:0/adminconsoleapp
2021-01-20 09:32:39,652 DEBUG com.ca.uim.policy.management.events.service.HeartBeatService:registerThisNode:243 [Catalina-utility-1] - Registering the policy node to master@http://<masked_adminconsole_ip_when_creating_this_techdoc>:0/adminconsoleapp
2021-01-20 09:32:39,652 ERROR com.ca.uim.policy.management.events.service.HeartBeatService:registerThisNode:307 [Catalina-utility-1] - Registration of this policy node to master failed, java.net.ConnectException: connect: Address is invalid on local machine, or port is not valid on remote machine
2021-01-20 09:32:39,652 DEBUG com.ca.uim.policy.management.events.service.HeartBeatService:registerThisNode:243 [Timer-1] - Registering the policy node to master@http://<masked_adminconsole_ip_when_creating_this_techdoc>:0/adminconsoleapp
2021-01-20 09:32:39,652 ERROR com.ca.uim.policy.management.events.service.HeartBeatService:registerThisNode:307 [Timer-1] - Registration of this policy node to master failed, java.net.ConnectException: connect: Address is invalid on local machine, or port is not valid on remote machine
2021-01-20 09:37:39,652 DEBUG com.ca.uim.policy.management.events.service.HeartBeatService:registerThisNode:243 [Timer-1] - Registering the policy node to master@http://<masked_adminconsole_ip_when_creating_this_techdoc>:0/adminconsoleapp
2021-01-20 09:37:39,652 ERROR com.ca.uim.policy.management.events.service.HeartBeatService:registerThisNode:307 [Timer-1] - Registration of this policy node to master failed, java.net.ConnectException: connect: Address is invalid on local machine, or port is not valid on remote machine
Resolution
Update UIM to release 20.3.2 with the latest fixes, please be aware the patch list has been further updated as can be seen below:
In this case, installing ump_operatorconsole_2.08_HF3 resolved the issue. Please find the procedure to install ump_operatorconsole_2.08_HF3 below:
Steps to apply the patch:
1. Deploy the ump_operatorconsole_2.08_HF3.zip from your local drive to the UIM Server Local Archive.
2. Deploy ump_operatorconsole installation package (version 2.08hf3) from the Archive folder to the Operator Console robot.
3. Download grouping_api_2.0.6_bundle.zip from Hotfix site. Unzip the grouping_api_2.0.6_bundle.zip to some temporary folder on Operator Console Robot.
4. Deactivate wasp probe on Operator Console robot. Copy files grouping-api-model-2.0.6.jar & grouping-api-service-local-2.0.6.jar from temporary folder to [UIM Install Path]\probes\service\wasp\lib\services on Operator Console robot.
5. Move/Delete files grouping-api-model-2.0.5.jar & grouping-api-service-local-2.0.5.jar from [UIM Install Path]\probes\service\wasp\lib\services, if exists.
6. Activate wasp probe.
Additional Information
The UIM 20.3.2 fixes can be downloaded from the below link, please ensure to read the instructions in the Patch Information before applying the fixes:
Feedback
