ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

UIM 20.4 CU1 - Wasp probe not starting, no address or port and pid recycles - Post deployment of CU1

book

Article ID: 238742

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

This technical article documents an issue faced with the operator console wasp probe after the deployment of the CU1 patch via AC. 

Operator Console 20.4 - Cumulative Update 1 SolutionDetails - Support Portal - Broadcom support portal

Symptoms of the issue: 

1. Wasp probe in green status however, it does not have an address or port, and the pid continue to recycle (every 5-15 minutes). 

2. The wasp probe log file displayed the following errors 5-10 minutes after the start up attempt: 

Apr 05 16:15:09:859 DBLOW [Catalina-utility-1, com.nimsoft.selfservice.v2.controller.TemplateController] TemplateController.getTemplateBluePrint:451: Fetching blueprint for template 1463
Apr 05 16:15:39:160 DEBUG [Catalina-utility-1, com.ca.uim.mcs.db.DataSourceManager] DataSourceManager.findDataSource:91: Running inside wasp
Apr 05 16:15:43:550 ERROR [Catalina-utility-1, org.apache.catalina.core.ContainerBase] startInternal() A child container failed during start
Apr 05 16:15:43:566 ERROR [Catalina-utility-1, org.apache.catalina.core.ContainerBase] java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: Failed to initialize component [[email protected]]
 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)
 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)
 at java.lang.Thread.run(Thread.java:748)
Caused by: org.apache.catalina.LifecycleException: Failed to initialize component [[email protected]]
 at org.apache.catalina.util.LifecycleBase.handleSubClassException(LifecycleBase.java:440)
 at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:139)
 at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:173)
 at org.apache.catalina.webresources.StandardRoot.startInternal(StandardRoot.java:726)
 at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
 at org.apache.catalina.core.StandardContext.resourcesStart(StandardContext.java:4885)
 at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5023)
 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 org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
 at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:134)
 at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:919)
 ... 11 more
Caused by: java.lang.IllegalArgumentException: java.util.zip.ZipException: error in opening zip file
 at org.apache.catalina.webresources.AbstractSingleArchiveResourceSet.initInternal(AbstractSingleArchiveResourceSet.java:143)
 at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:136)
 ... 23 more
Caused by: java.util.zip.ZipException: error in opening zip file
 at java.util.zip.ZipFile.open(Native Method)
 at java.util.zip.ZipFile.<init>(ZipFile.java:225)
 at java.util.zip.ZipFile.<init>(ZipFile.java:155)
 at java.util.jar.JarFile.<init>(JarFile.java:166)
 at java.util.jar.JarFile.<init>(JarFile.java:130)
 at org.apache.tomcat.util.compat.JreCompat.jarFileNewInstance(JreCompat.java:241)
 at org.apache.tomcat.util.compat.JreCompat.jarFileNewInstance(JreCompat.java:226)
 at org.apache.catalina.webresources.AbstractSingleArchiveResourceSet.initInternal(AbstractSingleArchiveResourceSet.java:140)

Environment

Release : 20.4

Component : UIM OPERATOR CONSOLE - WASP & CORE

Resolution

1. Deactivate the wasp probe on the OC robot.

2. Manually deploy the following packages (via IM or AC) 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

Note: These are the packages within the CU1 patch. The oc_cumulative_update-20.4.1.zip (Metapack) & metapack_helper-20.4.1.zip (Metapack Helper) packages do not need deployment during this manual task. 

3. Once the packages are deployed (finished), start the OC wasp probe and confirm the issue is now resolved. 

Note: in some cases when wasp doesn't start after the above steps, please do the following:
- Stop the wasp probe in OC
- Deploy ump_operatorconsole-20.4.1 ( the latest patch)
- Deploy UMP 20.4 
- RDP to the OC machine and Delete the work folder which is located in Nimsoft/probes/service/wasp
- Start the wasp probe