• Sign In
  1. Messages

Labkey 14.3 on RHEL 7 - Broken

Installation Forum (Inactive)

View Message

view list print
Labkey 14.3 on RHEL 7 - Broken hcrissma  2015-03-07 05:51
Status: Closed
 
Following the manual install directions I get error on tomcat start. Labkey doesn't start. Appears to be related to this https://www.labkey.org/announcements/home/Server/Forum/thread.view?rowId=10323. Windows install is not an option.

Apache Tomcat/7.0.54

ERROR ModuleLoader 2015-03-05 14:28:43,056 localhost-startStop-1 : Failure occurred during ModuleLoader init.
org.labkey.api.util.ConfigurationException: This server does not appear to be compiled for production mode
        at org.labkey.api.module.ModuleLoader.verifyProductionModeResources(ModuleLoader.java:438)
        at org.labkey.api.module.ModuleLoader.doInit(ModuleLoader.java:311)
        at org.labkey.api.module.ModuleLoader.init(ModuleLoader.java:256)
        at org.apache.catalina.core.ApplicationFilterConfig.initFilter(ApplicationFilterConfig.java:279)
        at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:260)
        at org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:105)
        at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:4809)
        at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5485)
        at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
        at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
        at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
        at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:632)
        at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:672)
        at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1862)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
        at java.util.concurrent.FutureTask.run(FutureTask.java:262)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:745)
 
 
jeckels responded:  2015-03-08 15:40
Hello,

Can you attach all of the log files from your Tomcat logs directory? I suspect that the server is having trouble finding many of the files required for the deployment, but happens to perform this particular check before noticing that other files that aren't specific to production builds are missing as well. The log files, especially catalina.log and labkey.log, probably contain other messages that can help diagnose the underlying issue.

Thanks,
Josh
 
jeckels responded:  2015-03-10 09:32
Hi Hugh,

Thanks for passing along your logs. The relevant error message is in the catalina.*.log files. It looks to be a problem extracting the .module files, which can usually be solved by granting the user running the Tomcat process write permission to the modules directory:

...
SEVERE: Unable to create directory /opt/labkey/modules/announcements, there may be a problem with file permissions
Mar 03, 2015 10:57:09 AM sun.reflect.NativeMethodAccessorImpl invoke0
SEVERE: Unable to create directory /opt/labkey/modules/announcements/META-INF, there may be a problem with file permissions
Mar 03, 2015 10:57:09 AM sun.reflect.NativeMethodAccessorImpl invoke0
SEVERE: Unable to extract the module archive /opt/labkey/modules/announcements.module!
java.io.IOException: Failed to process /opt/labkey/modules/announcements.module
...

We'll look to improve the error message you see in the browser to better point at the root cause.

Thanks,
Josh
 
hcrissma responded:  2015-03-23 12:49
There were multiple issues. The initial problem was that the tomcat user did not have the correct permissions labkey folder. Next, Rhel 7 did not have the tomcat-dbcp.jar in the /usr/share/tomcat/lib directory. I had to get jar from maven. Now it is working correctly.

Hugh