wasp probe not working after upgrade to 20.4 and 'Group Management Failed' error in OC
Article ID: 239421
Updated On:
Products
Issue/Introduction
The Operator Console was updated to version 20.4 but the wasp probe does not load. The operator console was reinstalled but one does not work.
Also when selecting OC error shows as 'Group Management Failed.'
Environment
Release : 20.4
Component : UIM OPERATOR CONSOLE - WASP & CORE
Cause
- leftover/invalid webapp versions
Resolution
Apr 13 09:15:10:607 ERROR [Catalina-utility-1, org.apache.catalina.core.ContainerBase] startInternal() A child container failed during start
Apr 13 09:15:10:607 ERROR [Catalina-utility-1, org.apache.catalina.core.ContainerBase] java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: Failed to start component [org.apache.catalina.webresources.StandardRoot@726f0f68]...
etc
etc
...
Caused by: java.lang.IllegalArgumentException: The main resource set specified [E:\Program Files (x86)\Nimsoft\probes\service\wasp\webapps\mps] is not valid
at org.apache.catalina.webresources.StandardRoot.createMainResourceSet(StandardRoot.java:751)
at org.apache.catalina.webresources.StandardRoot.startInternal(StandardRoot.java:708)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
... 20 more
same goes for the following wasp webapps on the OC machine as well:
Caused by: java.lang.IllegalArgumentException: The main resource set specified [E:\Program Files (x86)\Nimsoft\probes\service\wasp\webapps\mcs-ui-app] is not valid
Caused by: java.lang.IllegalArgumentException: The main resource set specified [E:\Program Files (x86)\Nimsoft\probes\service\wasp\webapps\alarmviewer-api] is not valid
Typically this is because something (such as a virus scanner or security/user permissions) is preventing wasp from extracting the webapp folder from the war file.
$\Nimsoft\probes\service\wasp\webapps
One option is to discover the offending application or Group policy and then run the installer again, and/or delete the offending wasp webapp and deploy the latest wasp webapp versions.
--------------------------------------------------------------------------------------------------------------------------
Admin Console wasp (Primary hub)
1. Deactivate wasp
2. Save off the wasp folder in case you need it later
3. Delete the existing wasp folder.
4. Redeploy the wasp 20.40 from the local archive anew (if you haven't already)
5. Reinstall the Admin Console by deploying the following packages to the Primary hub:
- wasp: 20.40
- uimhome: 20.4.0
- adminconsoleapp: 20.40
- uimesdplatelemetry: 20.40
- mps: 20.100
"Group Management Failed"
When selecting Settings 'cogwheel' icon in the Operator Console in UIM 20.3.3, an error occurs.
So, now also on the OC robot machine deploy:
- mcsuiapp_portlet 20.40
- wasp_alarmviewer-api 20.40
Restart the wasp probe(s)
Then check the Admin Console
Hit the web admin console url, e.g.,
http://<primary_hub_hostname>/adminconsoleapp
Admin Console should then load.
Then check the Operator Console (OC)
Select the OC 'Settings' icon again, and the 'Group Management Failed' error should no longer occur.
Note that after you deploy those 20.40 version and get it working, you should download and deploy the hotfixes from the hotfix site to address the most recent Apache log4j vulnerabilities.
Many of the probes now have a 20.41 version which addresses this. Please refer to the hotfix site:
https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/release-announcements/CA-Unified-Infrastructure-Management-Hotfix-Index/7233?r=2&r=1
See-> Operator Console 20.4 - Cumulative Update 1
https://support.broadcom.com/web/ecx/solutiondetails?aparNo=99111410&os=MULTI-PLATFORM
Feedback
