wasp probe not working post upgrade to 20.4 GA not taking a port and taking a very long time to start
Article ID: 241806
Updated On:
Products
Issue/Introduction
The Operator Console (OC) was updated to UIM version 20.4 but the wasp probe does not start and throws a Max. restarts in the wasp.log and/or takes a very long time to start.
How can we uninstall, reinstall and configure wasp in 20.40?
Environment
- Release: 20.4/20.41/20.42
- Component: UIM OPERATOR CONSOLE - WASP & CORE
- wasp probe
Cause
- wasp.cfg - possible corruption
Resolution
Here are the steps to safely uninstall, reinstall and configure wasp in 20.40.
(All steps and results tested in UIM 20.4/20.41/20.42)
On the Operator Console (OC) robot,
1. Copy and save (backup) the entire wasp folder in a safe place for later restore of 1 or more sections if needed.
2. Deactivate wasp
3. Rt-click and delete the wasp probe.
4. Delete the existing, current wasp probe folder.
5. Restart the OC Nimsoft Robot Watcher service.
6. Redeploy the wasp probe v20.40 from your local archive on the Primary hub.
7. Under the wasp <setup> section, set the data_engine key in wasp.cfg to the NimBUS address of the data_engine on the Primary hub,
e.g., data_engine = /<uim_domai>/<uim_hub>/<uim_robot>/data_engine
8. wasp should start and get a port and a PID but if not, rt-click and Deactivate wasp.
9. Activate wasp.
10. Redeploy the version-specific wasp webapps from the local archive on the Primary hub.
ump 20.40
wasp_alarmviewer_api 20.40
wasp_service_wrapper 20.40
nisapi_wasp 20.40
ump_operatorconsole 20.40
ump_cabi 4.25
ump_slm 20.40
ump_reportscheduler 20.10
mcsuiapp_portlet 20.40
ump_dashboard 20.40
ump_accountadmin 20.40
policy_management_ws 20.40
11. Set the loglevel to 5, and set a logsize of 50000.
12. Set the Java min/max memory settings to at least 2048 and 4096 respectively as a start.
13. Update wasp.cfg ump_common section in wasp to the appropriate probe locations, eg.,
<ump_common>
nas = /<uim_domain>/<uim_hub>/<uim_robot>/nas
sla_engine = /<uim_domain>/<uim_hub>/<uim_robot>/sla_engine
automated_deployment_engine = /<uim_domain>/<uim_hub>/<uim_robot>/automated_deployment_engine
discovery_server =/<uim_domain>/<uim_hub>/<uim_robot>discovery_server
lists_use_java_cache = false
mcs_ui_app_url = /<uim_domain>/<uim_hub>/<uim_robot>/mcs-ui-app/
policy_management_ws = /<uim_domain>/<uim_hub>/<uim_robot>/policy_management_ws
maintenance_mode = /<uim_domain>/<uim_hub>/<uim_robot>/maintenance_mode
ems = /<uim_domain>/<uim_hub>/<uim_robot>/ems
mpse = /<uim_domain>/<uim_hub>/<uim_robot>/mpse
sla_engine = /<uim_domain>/<uim_hub>/<uim_robot>/sla_engine
udm_manager = /<uim_domain>/<uim_hub>/<uim_robot>/udm_manager (if still applicable to the UIM 20.4 CU version you're running)
</ump_common>
16. Access the OC Portal and the pages should render as expected
http://<your_oc_robot><example.com>/operatorconsole_portlet/overview
17. Manually deploy the updated, version-specific OC webapp components for OC 20.4 CU <#> from here:
DX Unified Infrastructure Management - Cumulative Updates & Patches
18. Deploy these packages listed below, manually to the OC Robot.
mcsuiapp_portlet-20.4.1.zip
policy_management_ws-20.4.1.zip
uim_reportscheduler-20.4.1.zip
ump_dashboard-20.4.1.zip
ump_operatorconsole-20.4.1.zip
ump_slm-20.4.1.zip
wasp_alarmviewer_api-20.4.1.zip
19. Activate wasp.
20. The wasp probe should then start up within 3-5 minutes without any significant delay.
Additional Information
Alternatively, this approach can also be tested:
- In IM, Deactivate the OC robot wasp probe
- RDP and login to the OC Robot machine
- Open wasp.cfg ~\Nimsoft\probes\service\wasp
- Select the wasp probe section <ump_common>
- Edit the ump_common section by adding a new parameter/key
wasp = /<domain name>/<hub name>/<OC_robot_name>/wasp
Other:
wasp probe not working after upgrade to 20.4 and 'Group Management Failed' error in OC
Feedback
