You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The default docker image for VIVO does not work on MacOS Sonoma 14.5
To Reproduce
Steps to reproduce the behavior:
try to run the vivo:latest image, or build a new image following the instructions in the readme. Tomcat fails to start with a null pointer exception.
To confirm that this wasn't a problem with the VIVO war file, I created an empty Docker file with just the tomcat image that runs catalina run . Same failure occurs. Switching to another image (tomcat:9.0.48-jdk11-openjdk-slim) resolved the problem and
I was able to run VIVO.
Screenshots
vivo | 02-Feb-2025 21:14:27.829 INFO [main] org.apache.catalina.core.AprLifecycleListener.initializeSSL OpenSSL successfully initialized [OpenSSL 1.1.1n 15 Mar 2022]
vivo | 02-Feb-2025 21:14:27.867 SEVERE [main] org.apache.catalina.startup.Catalina.load Error initializing Catalina
vivo | org.apache.catalina.LifecycleException: Failed to initialize component [StandardServer[8005]]
vivo | at org.apache.catalina.util.LifecycleBase.handleSubClassException(LifecycleBase.java:440)
vivo | at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:139)
vivo | at org.apache.catalina.startup.Catalina.load(Catalina.java:724)
vivo | at org.apache.catalina.startup.Catalina.load(Catalina.java:746)
vivo | at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
vivo | at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
vivo | at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
vivo | at java.base/java.lang.reflect.Method.invoke(Method.java:566)
vivo | at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:305)
vivo | at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:475)
vivo | Caused by: java.lang.NullPointerException
vivo | at java.base/jdk.internal.platform.cgroupv2.CgroupV2Subsystem.getInstance(CgroupV2Subsystem.java:81)
vivo | at java.base/jdk.internal.platform.CgroupSubsystemFactory.create(CgroupSubsystemFactory.java:113)
vivo | at java.base/jdk.internal.platform.CgroupMetrics.getInstance(CgroupMetrics.java:167)
vivo | at java.base/jdk.internal.platform.SystemMetrics.instance(SystemMetrics.java:29)
vivo | at java.base/jdk.internal.platform.Metrics.systemMetrics(Metrics.java:58)
vivo | at java.base/jdk.internal.platform.Container.metrics(Container.java:43)
vivo | at jdk.management/com.sun.management.internal.OperatingSystemImpl.<init>(OperatingSystemImpl.java:182)
vivo | at jdk.management/com.sun.management.internal.PlatformMBeanProviderImpl.getOperatingSystemMXBean(PlatformMBeanProviderImpl.java:281)
vivo | at jdk.management/com.sun.management.internal.PlatformMBeanProviderImpl$3.nameToMBeanMap(PlatformMBeanProviderImpl.java:198)
vivo | at java.management/java.lang.management.ManagementFactory.lambda$getPlatformMBeanServer$0(ManagementFactory.java:487)
vivo | at java.base/java.util.stream.ReferencePipeline$7$1.accept(ReferencePipeline.java:271)
vivo | at java.base/java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:177)
vivo | at java.base/java.util.HashMap$ValueSpliterator.forEachRemaining(HashMap.java:1693)
vivo | at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)
vivo | at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)
vivo | at java.base/java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:150)
vivo | at java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:173)
vivo | at java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
vivo | at java.base/java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:497)
vivo | at java.management/java.lang.management.ManagementFactory.getPlatformMBeanServer(ManagementFactory.java:488)
vivo | at org.apache.tomcat.util.modeler.Registry.getMBeanServer(Registry.java:463)
vivo | at org.apache.catalina.util.LifecycleMBeanBase.initInternal(LifecycleMBeanBase.java:55)
vivo | at org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:997)
vivo | at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:136)
vivo | ... 8 more
vivo | 02-Feb-2025 21:14:27.868 INFO [main] org.apache.catalina.startup.Catalina.load Server initialization in [148] milliseconds
vivo | 02-Feb-2025 21:14:27.965 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Catalina]
vivo | 02-Feb-2025 21:14:27.966 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: [Apache Tomcat/9.0.65]
vivo | 02-Feb-2025 21:14:27.976 INFO [main] org.apache.catalina.startup.HostConfig.deployWAR Deploying web application archive [/usr/local/tomcat/webapps/ROOT.war]
Environment (please complete the following information):
OS: Mac, Apple M3 Pro chip, Sonoma 14.5
Tomcat image 9-jdk11-openjdk
VIVO version [tested with 14, 15, latest]
The text was updated successfully, but these errors were encountered:
Describe the bug
The default docker image for VIVO does not work on MacOS Sonoma 14.5
To Reproduce
Steps to reproduce the behavior:
try to run the vivo:latest image, or build a new image following the instructions in the readme. Tomcat fails to start with a null pointer exception.
To confirm that this wasn't a problem with the VIVO war file, I created an empty Docker file with just the tomcat image that runs catalina run . Same failure occurs. Switching to another image (tomcat:9.0.48-jdk11-openjdk-slim) resolved the problem and
I was able to run VIVO.
Screenshots
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: