wasp not coming up in 20.1 after silent install

[Keith Clay]

I did a silent install of 9.02 and wasp was running.  I then did a silent install of 20.1 and wasp won't run now.  It is saying all the webapps are invalid.  I've attached a listing of the war files


Jul 13 12:55:30:225 DEBUG [main, com.nimsoft.nimbus.probe.service.wasp.Probe] Loading webappsJul 13 12:55:30:225 DEBUG [main, com.nimsoft.nimbus.probe.service.wasp.Probe] Loading webappsJul 13 12:55:30:225 INFO  [main, com.nimsoft.nimbus.probe.service.wasp.Probe] catalina_home = c:/Program Files (x86)/Nimsoft/probes/service/waspJul 13 12:55:30:265 INFO  [main, com.nimsoft.nimbus.probe.service.wasp.Probe] Webapp /mps deployed at /mps from c:\Program Files (x86)\Nimsoft\probes\service\wasp\webapps\mpsJul 13 12:55:30:275 INFO  [main, com.nimsoft.nimbus.probe.service.wasp.Probe] catalina_home = c:/Program Files (x86)/Nimsoft/probes/service/waspJul 13 12:55:30:276 INFO  [main, com.nimsoft.nimbus.probe.service.wasp.Probe] Webapp /uimapi deployed at /uimapi from uimapiJul 13 12:55:30:277 INFO  [main, com.nimsoft.nimbus.probe.service.wasp.Probe] catalina_home = c:/Program Files (x86)/Nimsoft/probes/service/waspJul 13 12:55:30:278 INFO  [main, com.nimsoft.nimbus.probe.service.wasp.Probe] Webapp  deployed at  from c:\Program Files (x86)\Nimsoft\probes\service\wasp\webapps\ROOTJul 13 12:55:30:278 INFO  [main, com.nimsoft.nimbus.probe.service.wasp.Probe] catalina_home = c:/Program Files (x86)/Nimsoft/probes/service/waspJul 13 12:55:30:279 INFO  [main, com.nimsoft.nimbus.probe.service.wasp.Probe] Webapp /uimesdplatelemetry deployed at /uimesdplatelemetry from c:\Program Files (x86)\Nimsoft\probes\service\wasp\webapps\uimesdplatelemetryJul 13 12:55:30:279 INFO  [main, com.nimsoft.nimbus.probe.service.wasp.Probe] catalina_home = c:/Program Files (x86)/Nimsoft/probes/service/waspJul 13 12:55:30:280 INFO  [main, com.nimsoft.nimbus.probe.service.wasp.Probe] Webapp /adminconsoleapp deployed at /adminconsoleapp from c:\Program Files (x86)\Nimsoft\probes\service\wasp\webapps\adminconsoleappJul 13 12:55:30:281 INFO  [main, com.nimsoft.nimbus.probe.service.wasp.Probe] catalina_home = c:/Program Files (x86)/Nimsoft/probes/service/waspJul 13 12:55:30:282 INFO  [main, com.nimsoft.nimbus.probe.service.wasp.Probe] Webapp /uimhome deployed at /uimhome from c:\Program Files (x86)\Nimsoft\probes\service\wasp\webapps\uimhomeJul 13 12:55:30:322 INFO  [main, com.nimsoft.nimbus.probe.service.wasp.Probe] HTTP connector uses HTTP/1.1 protocol handled by org.apache.coyote.http11.Http11NioProtocolJul 13 12:55:30:331 INFO  [main, com.nimsoft.nimbus.probe.service.wasp.Probe] HTTP connector max threads 500Jul 13 12:55:30:336 INFO  [main, com.nimsoft.nimbus.probe.service.wasp.Probe] HTTP connector compression = onJul 13 12:55:30:337 INFO  [main, com.nimsoft.nimbus.probe.service.wasp.Probe] HTTP connector compressionMinSize = 2048Jul 13 12:55:30:340 INFO  [main, com.nimsoft.nimbus.probe.service.wasp.Probe] HTTP connector compressableMimeType = text/html,text/xml,text/plain,text/css,text/javascript,application/javascript,application/json,application/xmlJul 13 12:55:30:345 INFO  [main, com.nimsoft.nimbus.probe.service.wasp.Probe] HTTP connector URIEncoding = UTF-8Jul 13 12:55:30:345 INFO  [main, com.nimsoft.nimbus.probe.service.wasp.Probe] No HTTPS port found in configuration file. HTTPS connector disabled.Jul 13 12:55:30:348 INFO  [main, com.nimsoft.nimbus.probe.service.wasp.Probe] AJP connector uses AJP/1.3 protocol handled by org.apache.coyote.ajp.AjpNioProtocolJul 13 12:55:30:348 INFO  [main, com.nimsoft.nimbus.probe.service.wasp.Probe] AJP connector max threads 250Jul 13 12:55:30:577 DEBUG [main, com.nimsoft.nimbus.probe.service.wasp.WaspLifecycleListener] Memory Status: Max Limit: 3641MB, Allocated: 491MB, Free: 413MB, Used: 78MBJul 13 12:55:30:579 DEBUG [main, com.nimsoft.nimbus.probe.service.wasp.WaspLifecycleListener] Memory Status: Max Limit: 3641MB, Allocated: 491MB, Free: 413MB, Used: 78MBJul 13 12:55:30:632 DEBUG [main, com.nimsoft.nimbus.probe.service.wasp.WaspLifecycleListener] Memory Status: Max Limit: 3641MB, Allocated: 491MB, Free: 408MB, Used: 83MBJul 13 12:55:36:010 INFO  [Catalina-utility-1, org.apache.catalina.core.ContainerBase.[wasp-engine].[localhost].[/]] No Spring WebApplicationInitializer types detected on classpathJul 13 12:56:00:891 ERROR [Catalina-utility-1, org.apache.catalina.core.ContainerBase] startInternal() A child container failed during startJul 13 12:56:00:891 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@69082ca4] 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) at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:841) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1384) at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1374) 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 start component [org.apache.catalina.webresources.StandardRoot@69082ca4] at org.apache.catalina.util.LifecycleBase.handleSubClassException(LifecycleBase.java:440) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:198) at org.apache.catalina.core.StandardContext.resourcesStart(StandardContext.java:4800) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:4935) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1384) at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1374) 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:909) ... 11 moreCaused by: java.lang.IllegalArgumentException: The main resource set specified [C:\Program Files (x86)\Nimsoft\probes\service\wasp\webapps\mps] is not valid at org.apache.catalina.webresources.StandardRoot.createMainResourceSet(StandardRoot.java:752) at org.apache.catalina.webresources.StandardRoot.startInternal(StandardRoot.java:709) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) ... 20 more
Jul 13 12:56:00:892 ERROR [Catalina-utility-1, org.apache.catalina.core.ContainerBase] startInternal() A child container failed during startJul 13 12:56:00:892 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@497514f4] 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) at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:841) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1384) at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1374) 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 start component [org.apache.catalina.webresources.StandardRoot@497514f4] at org.apache.catalina.util.LifecycleBase.handleSubClassException(LifecycleBase.java:440) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:198) at org.apache.catalina.core.StandardContext.resourcesStart(StandardContext.java:4800) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:4935) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1384) at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1374) 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:909) ... 11 moreCaused by: java.lang.IllegalArgumentException: The main resource set specified [C:\Program Files (x86)\Nimsoft\probes\service\wasp\webapps\uimesdplatelemetry] is not valid at org.apache.catalina.webresources.StandardRoot.createMainResourceSet(StandardRoot.java:752) at org.apache.catalina.webresources.StandardRoot.startInternal(StandardRoot.java:709) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)

[David Michel]

based on the webapps this is wasp at the primary hub
set wasp to deactivate 
rename these folders:
$\Nimsoft\probes\service\wasp\work
$\Nimsoft\probes\service\wasp\webapps\ROOT
C:\Windows\Temp\liferay OR the /tmp folder on unix
activate wasp
clear browser history from beginning of time

------------------------------
Support Engineer
Broadcom
------------------------------

[Keith Clay]

Renamed those two folders. I couldn't find a liferay directory under c:\windows\temp. Regardless, wasp still won't start.  I can't do a silent install of 20.1 and wasp work.  If I do a gui install it works fine, but with silent install wasp never works. I've tried it on two different servers. 9.02 wasp installs fine in silent mode, 20.1 doesn't.

How could I diagnose this?

[Keith Clay]

I copied the wasp directory from a working installation that I used gui to install and it works fine.  It appears the silent install doesn't work correctly for wasp under 20.1

[James Christensen]

Hi Keith,
The problem may be related to the uimapi version. I ran into a similar problem with a UMP 20.1 install where the wasp wouldn't start (just kept on restarting) and had a similar error in the log (Jul 13 12:56:00:892 ERROR [Catalina-utility-1, org.apache.catalina.core.ContainerBase] startInternal() A child container failed during start). The issue turned out to be an older version of the webservices_rest webapp. In your case, the uimapi webapp is not deployed as part of the upgrade and there is a 20.1 version of it (just like the webservices_rest webapp). If you disable the uimapi webapp prior to running the silent install upgrade, it just may work. Then upgrade the uimapi webapp after the silent install.

------------------------------
[Designation]
[City]
------------------------------