Re: Re: Solr 3.5 not starting on CentOS 6 or RHEL 5
Nope, I don't have a custom /tmp mount in fstab, I just have a basic CentOS 6 install for development and testing... Full everyone read/write permissions are in place on /tmp too. > Is /tmp a separate file system? There are problems with people > mounting /tmp with 'noexec' as a security precaution, which then > causes Solr to fail. Russ Bernhardt Systems Office Dudley Knox Library, Naval Postgraduate School Monterey, CA
Solr 3.5 not starting on CentOS 6 or RHEL 5
A software package we use recently upgraded to Solr 3.5 (from 1.4.1) and now we're having problems getting the Solr server to start up under RHEL 5 or CentOS 6. I upgraded our local install of Java to the latest from Oracle and it didn't help, even removed the local OpenJDK just to be sure. When starting jetty manually (with java -jar start.jar) I get the following messages: 2012-02-13 07:52:55.954::INFO: Logging to STDERR via org.mortbay.log.StdErrLog 2012-02-13 07:52:56.120::INFO: jetty-6.1.11 2012-02-13 07:52:56.184::INFO: Extract jar:file:/opt/vufind/solr/jetty/webapps/solr.war!/ to /tmp/Jetty_0_0_0_0_8080_solr.war__solr__7k9npr/webapp 2012-02-13 07:52:56.702::WARN: Failed startup of context org.mortbay.jetty.webapp.WebAppContext@15aaf0b3{/solr,jar:file:/opt/vufind/solr/jetty/webapps/solr.war!/} java.util.zip.ZipException: error in opening zip file at java.util.zip.ZipFile.open(Native Method) at java.util.zip.ZipFile.(Unknown Source) at java.util.jar.JarFile.(Unknown Source) at java.util.jar.JarFile.(Unknown Source) at org.mortbay.jetty.webapp.TagLibConfiguration.configureWebApp(TagLibConfiguration.java:168) at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1217) at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:513) at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:448) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39) at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152) at org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:156) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39) at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39) at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130) at org.mortbay.jetty.Server.doStart(Server.java:222) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39) at org.mortbay.xml.XmlConfiguration.main(XmlConfiguration.java:977) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.mortbay.start.Main.invokeMain(Main.java:194) at org.mortbay.start.Main.start(Main.java:512) at org.mortbay.start.Main.main(Main.java:119) 2012-02-13 07:52:56.713::INFO: Opened /opt/vufind/solr/jetty/logs/2012_02_13.request.log 2012-02-13 07:52:56.740::INFO: Started SelectChannelConnector@0.0.0.0:8080 Jetty starts up just fine but shows a 503 error when attempting to access localhost:8080/solr/. The temp directory structure does exist in /tmp/. Any ideas? Thanks, Russ Bernhardt Systems Analyst Library Information Systems Naval Postgraduate School, Monterey CA