primary hub wasp probe in green but without port and address

book

Article ID: 224284

calendar_today

Updated On:

Products

DX Infrastructure Management

Issue/Introduction

The adminconsoleapp and uimhome stopped working.

The primary hub wasp is on green but without port and address

Next error appears in primary hub wasp logs

Sep 17 11:27:33:351 ERROR [main, com.nimsoft.nimbus.probe.service.wasp.Probe] main() Fatal error!
Sep 17 11:27:33:351 ERROR [main, com.nimsoft.nimbus.probe.service.wasp.Probe] main() org.apache.catalina.LifecycleException: A child container failed during start
Sep 17 11:27:33:351 ERROR [main, com.nimsoft.nimbus.probe.service.wasp.Probe] org.apache.catalina.LifecycleException: A child container failed during start
 at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:928)
 at org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:262)
 at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
 at org.apache.catalina.core.StandardService.startInternal(StandardService.java:434)
 at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
 at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:930)
 at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
 at org.apache.catalina.startup.Tomcat.start(Tomcat.java:486)
 at com.nimsoft.nimbus.probe.service.wasp.Probe.doit(Probe.java:745)
 at com.nimsoft.nimbus.probe.service.wasp.Probe.main(Probe.java:117)
Caused by: java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: A child container failed during start
 at java.util.concurrent.FutureTask.report(FutureTask.java:122)
 at java.util.concurrent.FutureTask.get(FutureTask.java:192)
 at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:916)

This seems to have started after apply September patches for UIM 20.3.3

Cause

An antivirus can cause this behavior, and this is documented in 

https://knowledge.broadcom.com/external/article/187777/wasp-doesnt-start-after-uim-clean-instal.html

Another possible cause is that a package/webapp not intended to be deployed in primary hub was deployed by mistake.

In 20.3.3, the minimum-required webapp section names are:

1. ROOT
2. uimesdplatelemetry
3. mps
4. uimhome
5. adminconsoleapp

If for instance a package like mcs-ws is deployed in primary hub, you can experience the behavior reported in this document the next time the wasp is restarted.

Environment

Release : 20.3

Component : UIM - UMP_ADMINCONSOLE2

Resolution

To resolve the problem, just remove the package deployed by mistake.

The instructions for this can be found in 

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

Attachments