Fresh installon or upgrade of WASP probe failing: ERROR main() Fatal error!

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

We did a fresh installation of DXUIM (or Upgrade) on Windows 2019 server. The installation finished successfully but the wasp probe on Primary DX UIM server is in error state and does not come up.

I see the same error in the wasp log file as shown in the below tec doc: wasp doesn't start after UIM clean install. Fatal error! (broadcom.com)

I checked and the antivirus on the server is already disabled.

Error seen in wasp.log

Apr 20 05:13:55:625 ERROR [main, com.nimsoft.nimbus.probe.service.wasp.Probe] main() Fatal error!
Apr 20 05:13:55:625 ERROR [main, com.nimsoft.nimbus.probe.service.wasp.Probe] main() org.apache.catalina.LifecycleException: A child container failed during start
Apr 20 05:13:55:625 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:938)
at org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:263)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
at org.apache.catalina.core.StandardService.startInternal(StandardService.java:432)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:927)
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:751)
at com.nimsoft.nimbus.probe.service.wasp.Probe.main(Probe.java:119)
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:926)
... 9 more
Caused by: org.apache.catalina.LifecycleException: A child container failed during start
at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:938)
at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:835)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1396)
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1386)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)

Environment

DX UIM 23.4.*
OS: seen on windows2019

Cause

This is a non-reproducible rare issue. In some environments war files are not extracting properly.

Resolution

To resolve this issue:

1. Go to the <webapps> section in the wasp.cfg

2. Check whether each webapp section contains a property called "doc_base"

If not there add doc_base = <webapp name>

for eg:

<uimapi>
reloadable = true
cross_context = true
load_on_startup = true
unpack_war = true
doc_base = uimapi
path = /uimapi
</uimapi>

3. Restart the wasp