New PR opened to solve this issue. Jira: https://issues.apache.org/jira/browse/CLOUDSTACK-9780 Github: https://github.com/apache/cloudstack/pull/1938
Please review... *Will STEVENS* Lead Developer <https://goo.gl/NYZ8KK> On Fri, Feb 3, 2017 at 12:32 PM, Will Stevens <wstev...@cloudops.com> wrote: > Thanks for the tip Nicolas. > > It turns out that 'jenv' was not setting the JAVA_HOME even though it had > Java8 configured as the active Java version. > > Because of this, the file '/etc/cloudstack/management/classpath.conf' was > defaulting to Java7. > > I commented that section and made it default to Java8 and everything works > again. > > --- > export CLASSPATH > #if ([ -z "$JAVA_HOME" ] || [ ! -d "$JAVA_HOME" ]) && [ -d > /usr/lib/jvm/jre-1.7.0 ]; then > # export JAVA_HOME=/usr/lib/jvm/jre-1.7.0 > #fi > if ([ -z "$JAVA_HOME" ] || [ ! -d "$JAVA_HOME" ]) && [ -d > /usr/lib/jvm/jre-1.8.0 ]; then > export JAVA_HOME=/usr/lib/jvm/jre-1.8.0 > fi > PATH=$JAVA_HOME/bin:/sbin:/usr/sbin:$PATH > export PATH > --- > > Thanks for the help everyone... > > > > *Will STEVENS* > Lead Developer > > <https://goo.gl/NYZ8KK> > > On Fri, Feb 3, 2017 at 11:57 AM, Rafael Weingärtner < > rafaelweingart...@gmail.com> wrote: > >> The others already answered this one: >> "Unsupported major.minor version 52.0" >> >> I am assuming you are compiling with 1.8, and it seems you are using 1.7 >> or >> lower version. >> >> >> On Fri, Feb 3, 2017 at 11:48 AM, Nicolas Vazquez <nicovazque...@gmail.com >> > >> wrote: >> >> > Hi Will, >> > >> > Did you try modifying /etc/cloudstack/management/classpath.conf file >> for >> > Tomcat to run using java 8? >> > >> > 2017-02-03 13:43 GMT-03:00 Daan Hoogland <daan.hoogl...@shapeblue.com>: >> > >> > > that's what wat cought my eye as well, and this is important for >> users to >> > > consider, So to must first upgrade java and then ACS. >> > > >> > > ________________________________ >> > > From: Milamber <milam...@apache.org> >> > > Sent: 03 February 2017 17:40:37 >> > > To: dev@cloudstack.apache.org >> > > Subject: Re: Upgrade fails on Master >> > > >> > > >> > > Probably an issue with your java version on your Centos machine? now >> CS >> > > 4.10 need Java 8 to run. >> > > >> > > >> > > On 03/02/2017 15:12, Will Stevens wrote: >> > > > That was the 'management-server.log'... >> > > > >> > > > Here is the 'catalina.out' log. >> > > > >> > > > --- snip --- >> > > > Feb 03, 2017 2:22:56 PM org.apache.catalina.loader.Web >> appClassLoader >> > > > validateJarFile >> > > > INFO: >> > > > validateJarFile(/usr/share/cloudstack-management/webapps/ >> > > client/WEB-INF/lib/tomcat-embed-core-8.0.30.jar) >> > > > - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending >> class: >> > > > javax/servlet/Servlet.class >> > > > Feb 03, 2017 2:22:56 PM org.apache.tomcat.util.modeler.Registry >> > > > registerComponent >> > > > SEVERE: Null component >> > > > Catalina:type=JspMonitor,name=jsp,WebModule=//localhost/ >> > > client,J2EEApplication=none,J2EEServer=none >> > > > Feb 03, 2017 2:22:56 PM org.apache.catalina.startup.HostConfig >> > > > deployDirectory >> > > > SEVERE: Error deploying web application directory client >> > > > java.lang.UnsupportedClassVersionError: >> > > > org/apache/cloudstack/spring/module/web/CloudStackContextLoa >> derListene >> > r >> > > : >> > > > Unsupported major.minor version 52.0 (unable to load class >> > > > org.apache.cloudstack.spring.module.web.CloudStackContextLoa >> derListene >> > r) >> > > > at >> > > > org.apache.catalina.loader.WebappClassLoader.findClassInternal( >> > > WebappClassLoader.java:2334) >> > > > at >> > > > org.apache.catalina.loader.WebappClassLoader.findClass( >> > > WebappClassLoader.java:976) >> > > > at >> > > > org.apache.catalina.loader.WebappClassLoader.loadClass( >> > > WebappClassLoader.java:1450) >> > > > at >> > > > org.apache.catalina.loader.WebappClassLoader.loadClass( >> > > WebappClassLoader.java:1329) >> > > > at >> > > > org.apache.catalina.startup.WebAnnotationSet.loadClassAnnotation( >> > > WebAnnotationSet.java:145) >> > > > at >> > > > org.apache.catalina.startup.WebAnnotationSet. >> > > loadApplicationListenerAnnotations(WebAnnotationSet.java:73) >> > > > at >> > > > org.apache.catalina.startup.WebAnnotationSet. >> > loadApplicationAnnotations( >> > > WebAnnotationSet.java:56) >> > > > at >> > > > org.apache.catalina.startup.ContextConfig. >> > applicationAnnotationsConfig( >> > > ContextConfig.java:294) >> > > > at org.apache.catalina.startup.ContextConfig.start( >> > > ContextConfig.java:1046) >> > > > at >> > > > org.apache.catalina.startup.ContextConfig.lifecycleEvent( >> > > ContextConfig.java:265) >> > > > at >> > > > org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent( >> > > LifecycleSupport.java:142) >> > > > at org.apache.catalina.core.StandardContext.start( >> > > StandardContext.java:4650) >> > > > 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:142) >> > > > 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:606) >> > > > at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289) >> > > > at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414) >> > > > >> > > > Feb 03, 2017 2:22:56 PM org.apache.coyote.http11.Http11NioProtocol >> > start >> > > > INFO: Starting Coyote HTTP/1.1 on http-8080 >> > > > Feb 03, 2017 2:22:56 PM org.apache.jk.common.ChannelSocket init >> > > > INFO: JK: ajp13 listening on /0.0.0.0:20400 >> > > > Feb 03, 2017 2:22:56 PM org.apache.jk.server.JkMain start >> > > > INFO: Jk running ID=0 time=0/37 config=null >> > > > Feb 03, 2017 2:22:56 PM org.apache.catalina.startup.Catalina start >> > > > INFO: Server startup in 1203 ms >> > > > --- snip --- >> > > > >> > > > The packages were built on a CentOS6 Jenkins slave and are being run >> > on a >> > > > CentOS 6.8 VM. >> > > > >> > > > Any ideas??? >> > > > >> > > > *Will STEVENS* >> > > > Lead Developer >> > > > >> > > > <https://goo.gl/NYZ8KK> >> > > > >> > > > On Fri, Feb 3, 2017 at 9:45 AM, Rafael Weingärtner < >> > > > rafaelweingart...@gmail.com> wrote: >> > > > >> > > >> Is the log you posted a piece of catalina.out or the >> > > management-server.log? >> > > >> >> > > >> Normally when the container (in this case Tomcat) does not go up, I >> > try >> > > to >> > > >> check the container log files, which may contain log entries that >> are >> > > not >> > > >> logged in the application log file. For tomcat, I normally check >> the >> > > >> catalina.out. >> > > >> >> > > >> On Fri, Feb 3, 2017 at 9:40 AM, Will Stevens < >> > williamstev...@gmail.com> >> > > >> wrote: >> > > >> >> > > >>> Hey All, >> > > >>> I have been doing the same upgrade path for months. It basically >> > goes >> > > >> like >> > > >>> this. I am running CentOS6.8. >> > > >>> >> > > >>> - Build code with jenkins and publish to a repo >> > > >>> - Backup /etc/cloudstack/management/db.properties -> >> > db.properties.bck >> > > >>> - Update my /etc/yum.repos.d/cloudstack.repo file to point to the >> > new >> > > >>> build >> > > >>> - Since it is the same version as the last time (4.10), I have to >> > > remove >> > > >>> the old packages >> > > >>> -- sudo yum -y remove cloudstack-management cloudstack-common >> > > >>> cloudstack-usage >> > > >>> - Install the new packages >> > > >>> -- sudo yum -y install cloudstack-management cloudstack-usage >> > > >>> - Copy the db.properties.bck to db.properties >> > > >>> - Restart the service >> > > >>> >> > > >>> I recently pulled in the latest code from master and now I get >> > > different >> > > >>> behavior. >> > > >>> >> > > >>> When I install the packages, I get this: >> > > >>> --- snip --- >> > > >>> Running Transaction >> > > >>> Installing : cloudstack-common-4.10.0.0-SNAPSHOT.el6.x86_64 >> > > >> 1/3 >> > > >>> Installing : cloudstack-management-4.10.0.0 >> -SNAPSHOT.el6.x86_64 >> > > >> 2/3 >> > > >>> Unable to determine ssl settings for server.xml, please run >> > > >>> cloudstack-setup-management manually >> > > >>> Unable to determine ssl settings for tomcat.conf, please run >> > > >>> cloudstack-setup-management manually >> > > >>> Installing : cloudstack-usage-4.10.0.0-SNAPSHOT.el6.x86_64 >> > > >> 3/3 >> > > >>> Replacing db.properties with management server db.properties >> > > >>> Replacing key with management server key >> > > >>> Verifying : cloudstack-common-4.10.0.0-SNAPSHOT.el6.x86_64 >> > > >> 1/3 >> > > >>> Verifying : cloudstack-usage-4.10.0.0-SNAPSHOT.el6.x86_64 >> > > >> 2/3 >> > > >>> Verifying : cloudstack-management-4.10.0.0 >> -SNAPSHOT.el6.x86_64 >> > > >> 3/3 >> > > >>> Installed: >> > > >>> cloudstack-management.x86_64 0:4.10.0.0-SNAPSHOT.el6 >> > > >>> cloudstack-usage.x86_64 0:4.10.0.0-SNAPSHOT.el6 >> > > >>> >> > > >>> >> > > >>> Dependency Installed: >> > > >>> cloudstack-common.x86_64 0:4.10.0.0-SNAPSHOT.el6 >> > > >>> >> > > >>> Complete! >> > > >>> --- snip -- >> > > >>> >> > > >>> I check what files are in the '/etc/cloudstack/management' folder. >> > > >>> >> > > >>> --- snip relevant --- >> > > >>> server-nonssl.xml >> > > >>> server-ssl.xml >> > > >>> server.xml -> /etc/cloudstack/management/server-nonssl.xml >> > > >>> tomcat6.conf -> /etc/cloudstack/management/tomcat6-nonssl.conf >> > > >>> tomcat6-nonssl.conf >> > > >>> tomcat6-ssl.conf >> > > >>> tomcat-users.xml >> > > >>> --- snip relevant --- >> > > >>> >> > > >>> I notice that 'server.xml' is there, but 'tomcat.conf' is not. >> > > >>> >> > > >>> I run 'cloudstack-setup-management' as it says in the >> instructions. >> > > >>> >> > > >>> --- >> > > >>> $ sudo cloudstack-setup-management >> > > >>> Starting to configure CloudStack Management Server: >> > > >>> Configure Firewall ... [OK] >> > > >>> Configure CloudStack Management Server ...[OK] >> > > >>> CloudStack Management Server setup is Done! >> > > >>> --- >> > > >>> >> > > >>> It does not seem to have changed anything in >> > > '/etc/cloudstack/management' >> > > >>> folder. >> > > >>> >> > > >>> I try to start the CloudStack Management service and then tail the >> > log >> > > >> and >> > > >>> I get this in the logs and the service does not start. >> > > >>> >> > > >>> --- snip --- >> > > >>> 2017-01-18 20:01:19,134 INFO [o.a.c.s.l. >> > CloudStackExtendedLifeCycle] >> > > >>> (Thread-90:null) (logid:) stopping bean >> ClusterServiceServletAdapter >> > > >>> 2017-01-18 20:01:19,135 ERROR [c.c.c.ClusterServiceServletCo >> ntainer] >> > > >>> (Thread-10:null) (logid:) Unexpected exception >> > > >>> java.net.SocketException: Socket closed >> > > >>> at java.net.PlainSocketImpl.socketAccept(Native Method) >> > > >>> at java.net.AbstractPlainSocketImpl.accept( >> > > AbstractPlainSocketImpl.java: >> > > >>> 398) >> > > >>> at java.net.ServerSocket.implAccept(ServerSocket.java:530) >> > > >>> at java.net.ServerSocket.accept(ServerSocket.java:498) >> > > >>> at >> > > >>> com.cloud.cluster.ClusterServiceServletContainer$ >> ListenerThread.run( >> > > >>> ClusterServiceServletContainer.java:131) >> > > >>> 2017-01-18 20:01:19,135 INFO [o.a.c.s.l. >> > CloudStackExtendedLifeCycle] >> > > >>> (Thread-90:null) (logid:) stopping bean ClusterManagerImpl >> > > >>> 2017-01-18 20:01:19,135 INFO [c.c.c.ClusterManagerImpl] >> > > (Thread-90:null) >> > > >>> (logid:) Stopping Cluster manager, msid : 7617392934992 >> > > >>> --- snip --- >> > > >>> >> > > >>> I am not sure what changed on master that would have caused this, >> but >> > > >>> apparently something is unhappy. >> > > >>> >> > > >>> Any ideas for how to resolve this and make sure upgrades still >> work >> > for >> > > >>> ACS? >> > > >>> >> > > >>> Thanks, >> > > >>> >> > > >>> Will >> > > >>> >> > > >> >> > > >> >> > > >> -- >> > > >> Rafael Weingärtner >> > > >> >> > > >> > > >> > > daan.hoogl...@shapeblue.com >> > > www.shapeblue.com >> > > 53 Chandos Place, Covent Garden, Utrecht Utrecht 3531 VENetherlands >> > > @shapeblue >> > > >> > > >> > > >> > > >> > >> >> >> >> -- >> Rafael Weingärtner >> > >
