VIVO 1.13.0 error Can't write to Vitro home directory: '/opt/vivo/home'

[Andrés]

Hi, i installed VIVO 1.13.0 and when VIVO startup i get the next error:

Can't write to Vitro home directory: '/opt/vivo/home'

The directory exist and the permissions are correct.

I installed it according to the installation instructions.

What could be the problem?

We are stuck at this point without being able to move forward.

Thank you very much.

Andrés

Debian 11

Tomcat9

openjdk 11.0.18

Vivo 1.13.0

Vivo error log:

2023-03-16 16:24:29,519 ERROR [StartupStatus] From ApplicationSetup: Failed to initialize the Application.
java.lang.IllegalStateException: Can't write to Vitro home directory: '/opt/vivo/home'.
at edu.cornell.mannlib.vitro.webapp.application.VitroHomeDirectory$HomeDirectoryFinder.confirmValidDirectory(VitroHomeDirectory.java:183)
at edu.cornell.mannlib.vitro.webapp.application.VitroHomeDirectory$HomeDirectoryFinder.<init>(VitroHomeDirectory.java:83)
at edu.cornell.mannlib.vitro.webapp.application.VitroHomeDirectory.find(VitroHomeDirectory.java:27)
at edu.cornell.mannlib.vitro.webapp.application.ApplicationSetup.contextInitialized(ApplicationSetup.java:45)
at edu.cornell.mannlib.vitro.webapp.startup.StartupManager.initialize(StartupManager.java:175)
at edu.cornell.mannlib.vitro.webapp.startup.StartupManager.contextInitialized(StartupManager.java:65)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4716)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5177)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:717)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:690)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:706)
at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1093)
at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1810)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
at java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:118)
at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:1013)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:428)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1520)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:309)
at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:123)
at org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:423)
at org.apache.catalina.util.LifecycleBase.setState(LifecycleBase.java:366)
at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:936)
at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:843)
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.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
at java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:140)
at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:909)
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.Catalina.start(Catalina.java:772)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:342)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:477)
2023-03-16 16:24:29,521 INFO  [StartupManager] Called 'contextInitialized' on all listeners.
2023-03-16 16:24:29,560 INFO  [JSessionStripFilter] Filtering: no jsessionids will be generated.
2023-03-16 16:24:29,562 ERROR [ConfigurationProperties] ConfigurationProperties bean has not been set.
2023-03-16 16:24:29,562 WARN  [DummyConfigurationProperties] ConfigurationProperties has not been initialized: getProperty("Vitro.defaultNamespace")
2023-03-16 16:24:29,562 WARN  [DummyConfigurationProperties] ConfigurationProperties has not been initialized: getProperty("http.createCacheHeaders")
2023-03-16 16:24:30,218 ERROR [ConfigurationProperties] ConfigurationProperties bean has not been set.
2023-03-16 16:31:12,836 ERROR [ConfigurationProperties] ConfigurationProperties bean has not been set.
2023-03-16 16:31:16,585 ERROR [ConfigurationProperties] ConfigurationProperties bean has not been set.
2023-03-16 16:31:17,236 ERROR [ConfigurationProperties] ConfigurationProperties bean has not been set.

[Dragan Ivanovic]

Hello Andrés,

Thank you for your email. Please check whether a user which is running tomcat also has write permission for /opt/vivo/home.

If you can't resolve the issue, I suggest to join the VIVO slack for further discussion. Also, the most effective way to resolve the issue such as this one is to visit our regular weekly call on Tuesday at 4pm Central European Time (11am Eastern time).

Regards,

Dragan Ivanovic

--
You received this message because you are subscribed to the Google Groups "VIVO Tech" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vivo-tech+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vivo-tech/74cb320e-06ad-44bb-bd12-2ac9975b3916n%40googlegroups.com.

Virus-free.www.avg.com

[Andrés]

Thanks Dragan,

Yes the tomcat user have write permission in this directory.
I will send this cuestion in slack.

Thank you very much.
Andrés

[Georgy Litvinov]

Hello Andrés,

If you use standard tomcat that goes with Debian 11 then the directory should be allowed in tomcat service configuration.
https://salsa.debian.org/java-team/tomcat9/blob/master/debian/README.Debian#L38

Regards,
Georgy Litvinov

[Andrés Segovia]

Thanks Georgy, this tip resolved the problem.

Thank you very much.

Andrés

You received this message because you are subscribed to a topic in the Google Groups "VIVO Tech" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/vivo-tech/6tB2qsrjR50/unsubscribe.
To unsubscribe from this group and all its topics, send an email to vivo-tech+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vivo-tech/ca628a0f-c6d6-44e4-bd9d-e2fa4ef50df6n%40googlegroups.com.