Looks like there are other bugs being filed for this, in master the commit is 2f135be15f1850280d27585153de2650f13f1dcb. Unless we hear back from Noa or someone working on the Debian packaging soon, I think we should revert the commit. It may break Debian packaging at the cost of fixing CentOS packaging, which is why I hesitate (perhaps there's just a tweak that needs to be done to the CentOS packaging), but since the CentOS was there first, and there are a team of testers waiting on it, we should probably roll it back until we can include whatever fix with it.
On Wed, Feb 27, 2013 at 11:53 PM, Marcus Sorensen <shadow...@gmail.com> wrote: > I see we're still moving forward with committing to 4.1. So am I the > only one who can't get the management server to start? > > On Wed, Feb 27, 2013 at 2:57 PM, Marcus Sorensen <shadow...@gmail.com> wrote: >> For visibility, I'm sending this out separately to the dev list. >> >> Unable to start management server from installed RPM build artifacts >> as of commit >> >> commit 78e8d184288fcde0a6ef6b6f126424407601e8ca >> Date: Tue Feb 26 21:14:39 2013 +0100 >> >> CLOUDSTACK-1415: Debian & Ubuntu packaging work >> >> Commit prior to this works. If I revert the commit, current HEAD works >> (but maybe this breaks Debian and Ubuntu packaging?). >> >> Getting this in the catalina.out for management server: >> >> Feb 27, 2013 2:12:05 PM org.apache.catalina.core.AprLifecycleListener init >> INFO: The APR based Apache Tomcat Native library which allows optimal >> performance in production environments was not found on the >> java.library.path: >> /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib >> Feb 27, 2013 2:12:05 PM org.apache.tomcat.util.net.NioSelectorPool >> getSharedSelector >> INFO: Using a shared selector for servlet write/read >> Feb 27, 2013 2:12:05 PM org.apache.coyote.http11.Http11NioProtocol init >> INFO: Initializing Coyote HTTP/1.1 on http-8080 >> Feb 27, 2013 2:12:05 PM org.apache.tomcat.util.net.NioSelectorPool >> getSharedSelector >> INFO: Using a shared selector for servlet write/read >> Feb 27, 2013 2:12:05 PM org.apache.coyote.http11.Http11NioProtocol init >> INFO: Initializing Coyote HTTP/1.1 on http-7080 >> Feb 27, 2013 2:12:05 PM org.apache.catalina.startup.Catalina load >> INFO: Initialization processed in 710 ms >> Feb 27, 2013 2:12:05 PM org.apache.catalina.core.StandardService start >> INFO: Starting service Catalina >> Feb 27, 2013 2:12:05 PM org.apache.catalina.core.StandardEngine start >> INFO: Starting Servlet Engine: Apache Tomcat/6.0.24 >> Feb 27, 2013 2:12:05 PM org.apache.catalina.startup.HostConfig >> deployDirectory >> INFO: Deploying web application directory client >> Feb 27, 2013 2:12:06 PM org.apache.catalina.loader.WebappClassLoader >> validateJarFile >> INFO: >> validateJarFile(/usr/share/cloudstack-management/webapps/client/WEB-INF/lib/geronimo-servlet_3.0_spec-1.0.jar) >> - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending >> class: javax/servlet/Servlet.class >> log4j:ERROR Could not parse url >> [file:/usr/share/cloudstack-management/webapps/client/WEB-INF/classes/log4j-cloud.xml]. >> java.io.FileNotFoundException: >> /usr/share/cloudstack-management/webapps/client/WEB-INF/classes/log4j-cloud.xml >> (No such file or directory) >> at java.io.FileInputStream.open(Native Method) >> at java.io.FileInputStream.<init>(FileInputStream.java:138) >> at java.io.FileInputStream.<init>(FileInputStream.java:97) >> at >> sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:90) >> at >> sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:188) >> at >> org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown Source) >> at >> org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(Unknown >> Source) >> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) >> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) >> at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) >> at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) >> at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source) >> at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:177) >> at >> org.apache.log4j.xml.DOMConfigurator$2.parse(DOMConfigurator.java:612) >> at >> org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:711) >> at >> org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:618) >> at >> org.apache.log4j.xml.DOMConfigurator.configure(DOMConfigurator.java:743) >> at >> org.springframework.util.Log4jConfigurer.initLogging(Log4jConfigurer.java:69) >> at >> org.springframework.web.util.Log4jWebConfigurer.initLogging(Log4jWebConfigurer.java:151) >> at >> org.springframework.web.util.Log4jConfigListener.contextInitialized(Log4jConfigListener.java:45) >> at >> org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3972) >> at >> org.apache.catalina.core.StandardContext.start(StandardContext.java:4467) >> at >> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791) >> at >> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771) >> at >> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:526) >> at >> org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1041) >> at >> org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:964) >> at >> org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:502) >> at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1277) >> at >> org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:321) >> at >> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) >> at >> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053) >> at org.apache.catalina.core.StandardHost.start(StandardHost.java:722) >> at >> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045) >> at >> org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) >> at >> org.apache.catalina.core.StandardService.start(StandardService.java:516) >> at >> org.apache.catalina.core.StandardServer.start(StandardServer.java:710) >> at org.apache.catalina.startup.Catalina.start(Catalina.java:593) >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> at >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) >> at >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) >> at java.lang.reflect.Method.invoke(Method.java:601) >> at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289) >> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414) >> log4j:WARN No appenders could be found for logger >> (org.springframework.web.context.ContextLoader). >> log4j:WARN Please initialize the log4j system properly. >> Feb 27, 2013 2:12:28 PM org.apache.catalina.core.StandardContext start >> SEVERE: Error listenerStart >> Feb 27, 2013 2:12:28 PM org.apache.catalina.core.StandardContext start >> SEVERE: Context [/client] startup failed due to previous errors >> Feb 27, 2013 2:12:28 PM org.apache.catalina.loader.WebappClassLoader >> clearReferencesJdbc >> SEVERE: A web application registered the JBDC driver >> [com.mysql.jdbc.Driver] but failed to unregister it when the web >> application was stopped. To prevent a memory leak, the JDBC Driver has >> been forcibly unregistered. >> Feb 27, 2013 2:12:28 PM org.apache.catalina.loader.WebappClassLoader >> clearReferencesThreads >> SEVERE: A web application appears to have started a thread named >> [Timer-0] but has failed to stop it. This is very likely to create a >> memory leak. >> Feb 27, 2013 2:12:28 PM org.apache.catalina.loader.WebappClassLoader >> clearReferencesThreads >> SEVERE: A web application appears to have started a thread named >> [ClusteredAgentManager Timer] but has failed to stop it. This is very >> likely to create a memory leak. >> Feb 27, 2013 2:12:28 PM org.apache.catalina.loader.WebappClassLoader >> clearReferencesThreads >> SEVERE: A web application appears to have started a thread named >> [Abandoned connection cleanup thread] but has failed to stop it. This >> is very likely to create a memory leak. >> Feb 27, 2013 2:12:28 PM org.apache.catalina.loader.WebappClassLoader >> clearThreadLocalMap >> SEVERE: A web application created a ThreadLocal with key of type >> [org.springframework.core.NamedThreadLocal] (value [Prototype beans >> currently in creation]) and a value of type [null] (value [null]) but >> failed to remove it when the web application was stopped. To prevent a >> memory leak, the ThreadLocal has been forcibly removed. >> Feb 27, 2013 2:12:28 PM org.apache.catalina.loader.WebappClassLoader >> clearThreadLocalMap >> SEVERE: A web application created a ThreadLocal with key of type >> [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@808e5cc]) and a >> value of type [com.cloud.utils.db.Transaction] (value [ : ]) but >> failed to remove it when the web application was stopped. To prevent a >> memory leak, the ThreadLocal has been forcibly removed. >> Feb 27, 2013 2:12:28 PM org.apache.catalina.loader.WebappClassLoader >> clearThreadLocalMap >> SEVERE: A web application created a ThreadLocal with key of type >> [org.springframework.core.NamedThreadLocal] (value [Current AOP method >> invocation]) and a value of type [null] (value [null]) but failed to >> remove it when the web application was stopped. To prevent a memory >> leak, the ThreadLocal has been forcibly removed.
