Re: Unable to start system VMS with new install of 4.4
Try restarting libvirt and cloudstack-agent, if that does not work please reopen the bug and attach management server logs and agent logs. Thanks Harikrishna On 25-Aug-2014, at 7:57 am, Alex Dodson wrote: > Hello, > > I am trying to get an install of Cloudstack 4.4 with kvm hypervisors. I > follow the install guide to a letter. I can mount the nfs stores fine on the > hv host. When I check cloudstack-agent.err on the hypervisor host I am > trying to install on the logs are filled with the below. > > libvir: QEMU Driver error : Domain not found: no domain with matching name > 'v-1-VM' > libvir: QEMU Driver error : Domain not found: no domain with matching name > 's-45-VM' > libvir: LXC Driver error : Domain not found: No domain with matching name > 's-45-VM' > libvir: QEMU Driver error : Domain not found: no domain with matching name > 's-45-VM' > > The error from the management-server.log when I try to launch secondary > storage and console proxy vms is: > > 2014-08-25 01:53:36,955 WARN [o.a.c.s.SecondaryStorageManagerImpl] > (secstorage-1:ctx-798c8678) Exception while trying to start secondary storage > vm > java.lang.RuntimeException: Job failed due to exception Resource [Host:1] is > unreachable: Host 1: Unable to start instance due to Unable to get answer > that is of class com.cloud.agent.api.StartAnswer > > > > > This issue https://issues.apache.org/jira/browse/CLOUDSTACK-7217 appears to > related > This is installed on a rhel6 box with the following versions of packages that > may be relevant below. > > rpm -qa *cloud* > cloudstack-common-4.4.0-NONOSS_3.el6.x86_64 > cloudstack-agent-4.4.0-NONOSS_3.el6.x86_64 > > rpm -qa *qemu* > qemu-img-0.12.1.2-2.415.el6.3ceph.x86_64 > qemu-kvm-0.12.1.2-2.415.el6.3ceph.x86_64 > > rpm -qa libvirt > libvirt-0.10.2-29.el6_5.9.x86_64 > > I can see what appears to be the original system vm template via ID in the > primary storage mounted via the hypervisor node as well but the centos 5.5 vm > never becomes ready. Any other templates I attempt to create via the web > interface never become ready either. > > > Any pointers as to how I can fix this? It is hard to get anywhere with this > issue going on. > > thanks, > > Alex > >
CS 4.4: openvswitch network service providers (plugins)
Hello all, I am using OpenVswitch to configure birdges and want to enable plugin for it. At CS 4.4 there are 2 plugins with the same name: one is „Ovs“ the other is „OVS“. When I try to enable „OVS“ - it does nothing and management server log is empty. When I try to enable „Ovs“ it shows error: Api Discovery plugin was unable to find an api by that name or process any apis Is there any prerequisites to enabe this plug-in ? Or is this a bug, because at CS4.3 I didn’t have any problems activating Ovs. Thanks, Vadim Kimlaychuk
Management don't start after upgrading
Hi all, I am trying to upgrade CloudStack from 4.3.0 to 4.4.0 on Ubuntu systems. Following the guide, I stop and upgraded the management server and the agents but, when I try to restart the management I see these error messages in /var/log/syslog (the log file /var/log/cloudstack/management/management-server.log is stopped at the moment before the upgrade): Aug 25 14:23:30 csman44 jsvc.exec[2182]: Aug 25, 2014 2:23:30 PM org.apache.catalina.core.StandardService start#012INFO: Starting service Catalina Aug 25 14:23:30 csman44 jsvc.exec[2182]: Aug 25, 2014 2:23:30 PM org.apache.catalina.core.StandardEngine start#012INFO: Starting Servlet Engine: Apache Tomcat/6.0.35 Aug 25 14:23:30 csman44 jsvc.exec[2182]: Aug 25, 2014 2:23:30 PM org.apache.catalina.startup.HostConfig deployDirectory#012INFO: Deploying web application directory client Aug 25 14:23:31 csman44 jsvc.exec[2182]: Aug 25, 2014 2:23:31 PM org.apache.catalina.loader.WebappClassLoader validateJarFile#012INFO: validateJarFile(/usr/share/cloudstack-management/webapps/client/WEB-INF/lib/servlet-api-2.5-20081211.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class Aug 25 14:23:31 csman44 jsvc.exec[2182]: Aug 25, 2014 2:23:31 PM org.apache.catalina.loader.WebappClassLoader validateJarFile#012INFO: validateJarFile(/usr/share/cloudstack-management/webapps/client/WEB-INF/lib/tomcat-embed-core-7.0.30.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class Aug 25 14:23:31 csman44 jsvc.exec[2182]: Aug 25, 2014 2:23:31 PM org.apache.tomcat.util.modeler.Registry registerComponent#012SEVERE: Null component Catalina:type=JspMonitor,name=jsp,WebModule=//localhost/client,J2EEApplication=none,J2EEServer=none Aug 25 14:23:31 csman44 jsvc.exec[2182]: Aug 25, 2014 2:23:31 PM org.apache.catalina.startup.HostConfig deployDirectory#012SEVERE: Error deploying web application directory client#012java.lang.UnsupportedClassVersionError: org/apache/cloudstack/spring/module/web/CloudStackContextLoaderListener : Unsupported major.minor version 51.0 (unable to load class org.apache.cloudstack.spring.module.web.CloudStackContextLoaderListener)#012#011at org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappClassLoader.java:2822)#012#011at org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.java:1159)#012#011at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1647)#012#011at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1526)#012#011at org.apache.catalina.startup.WebAnnotationSet.loadClassAnnotation(WebAnnotationSet.java:145)#012#011at org.apache.catalina.startup.WebAnnotationSet.loadApplicationListenerAnnotations(WebAnnotationSet.java:73)#012#011at org.apache.catalina.startup.WebAnnotationSet.loadApplicationAnnotations Aug 25 14:23:31 csman44 jsvc.exec[2182]: (WebAnnotationSet.java:56)#012#011at org.apache.catalina.startup.ContextConfig.applicationAnnotationsConfig(ContextConfig.java:297)#012#011at org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:1078)#012#011at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:261)#012#011at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)#012#011at org.apache.catalina.core.StandardContext.start(StandardContext.java:4612)#012#011at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:799)#012#011at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:779)#012#011at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:601)#012#011at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1079)#012#011at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:1002)#012#011at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:506)#012#011at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1317)#012#011at org.apache.catali Aug 25 14:23:31 csman44 jsvc.exec[2182]: na.startup.HostConfig.lifecycleEvent(HostConfig.java:324)#012#011at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)#012#011at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1065)#012#011at org.apache.catalina.core.StandardHost.start(StandardHost.java:840)#012#011at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1057)#012#011at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463)#012#011at org.apache.catalina.core.StandardService.start(StandardService.java:525)#012#011at org.apache.catalina.core.StandardServer.start(StandardServer.java:754)#012#011at org.apache.catalina.startup.Catalina.start(Catalina.java:595)#012#011at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)#012#011at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java
Re: Management don't start after upgrading
It seems to start with java6, while acs 4.4 requires java7. I'm not that familiar with ubuntu, but check if you can specify the default java version somehow, or remove java6 if you don't need it for anything else. Erik On Mon, Aug 25, 2014 at 2:44 PM, Ugo Vasi wrote: > Hi all, > I am trying to upgrade CloudStack from 4.3.0 to 4.4.0 on Ubuntu systems. > Following the guide, I stop and upgraded the management server and the > agents but, when I try to restart the management I see these error messages > in /var/log/syslog (the log file /var/log/cloudstack/ > management/management-server.log is stopped at the moment before the > upgrade): > > Aug 25 14:23:30 csman44 jsvc.exec[2182]: Aug 25, 2014 2:23:30 PM > org.apache.catalina.core.StandardService start#012INFO: Starting service > Catalina > Aug 25 14:23:30 csman44 jsvc.exec[2182]: Aug 25, 2014 2:23:30 PM > org.apache.catalina.core.StandardEngine start#012INFO: Starting Servlet > Engine: Apache Tomcat/6.0.35 > Aug 25 14:23:30 csman44 jsvc.exec[2182]: Aug 25, 2014 2:23:30 PM > org.apache.catalina.startup.HostConfig deployDirectory#012INFO: Deploying > web application directory client > Aug 25 14:23:31 csman44 jsvc.exec[2182]: Aug 25, 2014 2:23:31 PM > org.apache.catalina.loader.WebappClassLoader validateJarFile#012INFO: > validateJarFile(/usr/share/cloudstack-management/webapps/ > client/WEB-INF/lib/servlet-api-2.5-20081211.jar) - jar not loaded. See > Servlet Spec 2.3, section 9.7.2. Offending class: > javax/servlet/Servlet.class > Aug 25 14:23:31 csman44 jsvc.exec[2182]: Aug 25, 2014 2:23:31 PM > org.apache.catalina.loader.WebappClassLoader validateJarFile#012INFO: > validateJarFile(/usr/share/cloudstack-management/webapps/ > client/WEB-INF/lib/tomcat-embed-core-7.0.30.jar) - jar not loaded. See > Servlet Spec 2.3, section 9.7.2. Offending class: > javax/servlet/Servlet.class > Aug 25 14:23:31 csman44 jsvc.exec[2182]: Aug 25, 2014 2:23:31 PM > org.apache.tomcat.util.modeler.Registry registerComponent#012SEVERE: Null > component Catalina:type=JspMonitor,name=jsp,WebModule=//localhost/ > client,J2EEApplication=none,J2EEServer=none > Aug 25 14:23:31 csman44 jsvc.exec[2182]: Aug 25, 2014 2:23:31 PM > org.apache.catalina.startup.HostConfig deployDirectory#012SEVERE: Error > deploying web application directory > client#012java.lang.UnsupportedClassVersionError: > org/apache/cloudstack/spring/module/web/CloudStackContextLoaderListener : > Unsupported major.minor version 51.0 (unable to load class > org.apache.cloudstack.spring.module.web.CloudStackContextLoaderListener)#012#011at > org.apache.catalina.loader.WebappClassLoader.findClassInternal( > WebappClassLoader.java:2822)#012#011at org.apache.catalina.loader. > WebappClassLoader.findClass(WebappClassLoader.java:1159)#012#011at > org.apache.catalina.loader.WebappClassLoader.loadClass( > WebappClassLoader.java:1647)#012#011at org.apache.catalina.loader. > WebappClassLoader.loadClass(WebappClassLoader.java:1526)#012#011at > org.apache.catalina.startup.WebAnnotationSet.loadClassAnnotation( > WebAnnotationSet.java:145)#012#011at org.apache.catalina.startup. > WebAnnotationSet.loadApplicationListenerAnnotat > ions(WebAnnotationSet.java:73)#012#011at org.apache.catalina.startup. > WebAnnotationSet.loadApplicationAnnotations > Aug 25 14:23:31 csman44 jsvc.exec[2182]: (WebAnnotationSet.java:56)#012#011at > org.apache.catalina.startup.ContextConfig.applicationAnnotationsConfig( > ContextConfig.java:297)#012#011at org.apache.catalina.startup. > ContextConfig.start(ContextConfig.java:1078)#012#011at > org.apache.catalina.startup.ContextConfig.lifecycleEvent( > ContextConfig.java:261)#012#011at org.apache.catalina.util. > LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)#012#011at > org.apache.catalina.core.StandardContext.start(StandardContext.java:4612)#012#011at > org.apache.catalina.core.ContainerBase.addChildInternal( > ContainerBase.java:799)#012#011at org.apache.catalina.core. > ContainerBase.addChild(ContainerBase.java:779)#012#011at > org.apache.catalina.core.StandardHost.addChild(StandardHost.java:601)#012#011at > org.apache.catalina.startup.HostConfig.deployDirectory( > HostConfig.java:1079)#012#011at org.apache.catalina.startup. > HostConfig.deployDirectories(HostConfig.java:1002)#012#011at > org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:506)#012#011at > org.apache.catalina.startup.HostConfig.start(HostConfig.java:1317)#012#011at > org.apache.catali > Aug 25 14:23:31 csman44 jsvc.exec[2182]: na.startup.HostConfig. > lifecycleEvent(HostConfig.java:324)#012#011at org.apache.catalina.util. > LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)#012#011at > org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1065)#012#011at > org.apache.catalina.core.StandardHost.start(StandardHost.java:840)#012#011at > org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1057)#012#011at > org.apache.catalina.core.StandardEngine.start( > StandardEngine.java:463)#
Re: Management don't start after upgrading
Ok, I've installed java7 (): apt-get install openjdk-7-jre-headless openjdk-7-jre-lib icedtea-7-jre-cacao icedtea-7-jre-jamvm Now the web interface is working. Il 25/08/2014 14:47, Erik Weber ha scritto: It seems to start with java6, while acs 4.4 requires java7. I'm not that familiar with ubuntu, but check if you can specify the default java version somehow, or remove java6 if you don't need it for anything else. Erik On Mon, Aug 25, 2014 at 2:44 PM, Ugo Vasi wrote: Hi all, I am trying to upgrade CloudStack from 4.3.0 to 4.4.0 on Ubuntu systems. Following the guide, I stop and upgraded the management server and the agents but, when I try to restart the management I see these error messages in /var/log/syslog (the log file /var/log/cloudstack/ management/management-server.log is stopped at the moment before the upgrade): Aug 25 14:23:30 csman44 jsvc.exec[2182]: Aug 25, 2014 2:23:30 PM org.apache.catalina.core.StandardService start#012INFO: Starting service Catalina Aug 25 14:23:30 csman44 jsvc.exec[2182]: Aug 25, 2014 2:23:30 PM org.apache.catalina.core.StandardEngine start#012INFO: Starting Servlet Engine: Apache Tomcat/6.0.35 Aug 25 14:23:30 csman44 jsvc.exec[2182]: Aug 25, 2014 2:23:30 PM org.apache.catalina.startup.HostConfig deployDirectory#012INFO: Deploying web application directory client Aug 25 14:23:31 csman44 jsvc.exec[2182]: Aug 25, 2014 2:23:31 PM org.apache.catalina.loader.WebappClassLoader validateJarFile#012INFO: validateJarFile(/usr/share/cloudstack-management/webapps/ client/WEB-INF/lib/servlet-api-2.5-20081211.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class Aug 25 14:23:31 csman44 jsvc.exec[2182]: Aug 25, 2014 2:23:31 PM org.apache.catalina.loader.WebappClassLoader validateJarFile#012INFO: validateJarFile(/usr/share/cloudstack-management/webapps/ client/WEB-INF/lib/tomcat-embed-core-7.0.30.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class Aug 25 14:23:31 csman44 jsvc.exec[2182]: Aug 25, 2014 2:23:31 PM org.apache.tomcat.util.modeler.Registry registerComponent#012SEVERE: Null component Catalina:type=JspMonitor,name=jsp,WebModule=//localhost/ client,J2EEApplication=none,J2EEServer=none Aug 25 14:23:31 csman44 jsvc.exec[2182]: Aug 25, 2014 2:23:31 PM org.apache.catalina.startup.HostConfig deployDirectory#012SEVERE: Error deploying web application directory client#012java.lang.UnsupportedClassVersionError: org/apache/cloudstack/spring/module/web/CloudStackContextLoaderListener : Unsupported major.minor version 51.0 (unable to load class org.apache.cloudstack.spring.module.web.CloudStackContextLoaderListener)#012#011at org.apache.catalina.loader.WebappClassLoader.findClassInternal( WebappClassLoader.java:2822)#012#011at org.apache.catalina.loader. WebappClassLoader.findClass(WebappClassLoader.java:1159)#012#011at org.apache.catalina.loader.WebappClassLoader.loadClass( WebappClassLoader.java:1647)#012#011at org.apache.catalina.loader. WebappClassLoader.loadClass(WebappClassLoader.java:1526)#012#011at org.apache.catalina.startup.WebAnnotationSet.loadClassAnnotation( WebAnnotationSet.java:145)#012#011at org.apache.catalina.startup. WebAnnotationSet.loadApplicationListenerAnnotat ions(WebAnnotationSet.java:73)#012#011at org.apache.catalina.startup. WebAnnotationSet.loadApplicationAnnotations Aug 25 14:23:31 csman44 jsvc.exec[2182]: (WebAnnotationSet.java:56)#012#011at org.apache.catalina.startup.ContextConfig.applicationAnnotationsConfig( ContextConfig.java:297)#012#011at org.apache.catalina.startup. ContextConfig.start(ContextConfig.java:1078)#012#011at org.apache.catalina.startup.ContextConfig.lifecycleEvent( ContextConfig.java:261)#012#011at org.apache.catalina.util. LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)#012#011at org.apache.catalina.core.StandardContext.start(StandardContext.java:4612)#012#011at org.apache.catalina.core.ContainerBase.addChildInternal( ContainerBase.java:799)#012#011at org.apache.catalina.core. ContainerBase.addChild(ContainerBase.java:779)#012#011at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:601)#012#011at org.apache.catalina.startup.HostConfig.deployDirectory( HostConfig.java:1079)#012#011at org.apache.catalina.startup. HostConfig.deployDirectories(HostConfig.java:1002)#012#011at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:506)#012#011at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1317)#012#011at org.apache.catali Aug 25 14:23:31 csman44 jsvc.exec[2182]: na.startup.HostConfig. lifecycleEvent(HostConfig.java:324)#012#011at org.apache.catalina.util. LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)#012#011at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1065)#012#011at org.apache.catalina.core.StandardHost.start(StandardHost.java:840)#012#011at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1057)#012#011at org.apache.c
CS 4.4: openvswitch network service providers (plugins)
Hello all, I am using OpenVswitch to configure birdges and want to enable plugin for it. At CS 4.4 there are 2 plugins with the same name: one is „Ovs“ the other is „OVS“. When I try to enable „OVS“ - it does nothing and management server log is empty. When I try to enable „Ovs“ it shows error: Api Discovery plugin was unable to find an api by that name or process any apis Is there any prerequisites to enabe this plug-in ? Or is this a bug, because at CS4.3 I didn’t have any problems activating Ovs. Thanks, Vadim Kimlaychuk
Move VR to another PrimaryStorage
Hello all. I'm just try to move the root disk of one of my VirtualRouters but I can't see how can i do that. any idea how can I do that ? thanks -- Hollman Eduardo Enciso R. http://algolibre.com @hollman
Re: Move VR to another PrimaryStorage
Not sure if this is supported by ACS. However, the usual way to migrate vm from one storage to another is to shutdown a vm and click on the one of the buttons (that looks like the cross with arrows), select the destination storage and click OK. If this option is not available for a virtual router, then it means that you can't do it. If you want to make your system vms to start on a particular primary storage you will need to change the systemvm offering and add the tag for the primary storage that you want to use. After that, delete the virtual router and do the Network restart with clean up ticked. It should recreate the VR using the tags and put it on the desired primary storage. Andrei - Original Message - From: "Hollman Enciso R." To: users@cloudstack.apache.org Sent: Monday, 25 August, 2014 4:23:02 PM Subject: Move VR to another PrimaryStorage Hello all. I'm just try to move the root disk of one of my VirtualRouters but I can't see how can i do that. any idea how can I do that ? thanks -- Hollman Eduardo Enciso R. http://algolibre.com @hollman
Primary Storage
I presented 2TB of primary storage (esx,vmfs) to cloudstack. It sees it, but in the management console it shows it as 4TB vs 2TB. Anyone else seen this doubling effect?
acs 4.4 and GUI madness
Hello guys, I've had a few issues with the acs 4.4 GUI and I am wondering if anyone else is noticing it as well? It seems like things are all over the place and do not fit in their pre-defined areas. Things like Dashboard is messed up and firewall rules are practically unusable. I am noticing it throughout the application. I am using Chrome, but Firefox is having the same issues. Did something go wrong during the update? Andrei
Re: CS 4.4: openvswitch network service providers (plugins)
Vadim I know this response is not helpful, but please kindly log this issue under https://issues.apache.org/jira/browse/CLOUDSTACK/ Thanks ilya On 8/25/14, 6:47 AM, Vadim Kimlaychuk wrote: Hello all, I am using OpenVswitch to configure birdges and want to enable plugin for it. At CS 4.4 there are 2 plugins with the same name: one is „Ovs“ the other is „OVS“. When I try to enable „OVS“ - it does nothing and management server log is empty. When I try to enable „Ovs“ it shows error: Api Discovery plugin was unable to find an api by that name or process any apis Is there any prerequisites to enabe this plug-in ? Or is this a bug, because at CS4.3 I didn’t have any problems activating Ovs. Thanks, Vadim Kimlaychuk
Re: acs 4.4 and GUI madness
Andrei 4.4 has some quirks, unless you have a specific reason, i'd suggest you remain in 4.3 until 4.4.1 is out. In the meantime, please log this issue and include a screenshot of what you are seeing - so it can get addressed in the next release. Thanks ilya On 8/25/14, 1:30 PM, Andrei Mikhailovsky wrote: Hello guys, I've had a few issues with the acs 4.4 GUI and I am wondering if anyone else is noticing it as well? It seems like things are all over the place and do not fit in their pre-defined areas. Things like Dashboard is messed up and firewall rules are practically unusable. I am noticing it throughout the application. I am using Chrome, but Firefox is having the same issues. Did something go wrong during the update? Andrei
RE: Primary Storage
So I think I found the answer to this. After looking through the logs I found this Found storage pool esx_lun201 of type VMFS with overprovisioning factor 2Total over provisioned capacity calculated is 2 * 2198754820096Total over provisioned capacity of the pool esx_lun201 id: 1 is 4397509640192 This correlates to the global setting storage.overprovisioning.factor, which says available storage will be (actual storage * the over provisioning factor). Which in my case comes out to 4TB... Just posting in case anybody else was wondering.. > From: mphilli7...@hotmail.com > To: users@cloudstack.apache.org > Subject: Primary Storage > Date: Mon, 25 Aug 2014 14:08:06 -0500 > > I presented 2TB of primary storage (esx,vmfs) to cloudstack. It sees it, but > in the management console it shows it as 4TB vs 2TB. Anyone else seen this > doubling effect? >
Template not ready...
All, So I'm looking at the default centos 5.3 template, and it is in a "No" ready state. The only secondary storage warning\error I see in the log is the following "There is no secondary storage VM for secondary storage host secStorage". Ideas?
CloudStack MS wont start post db outage
I'm experiencing an issue with bringing up one of 2 management hosts due to db outage. Sample layout: Host A - had running MS Host B - MS was down due to maintenance Host C - dedicated database host The database outage occurred on host C and cloudstack ms gracefully stopped it self. As a result, i'm not able to bring up the Host A, but i could start MS on Host B. IIRC, there was something cloudstack was doing to replay the uncommitted transactions or possible kept some cached files that prevent Host A from starting. Would anyone know where it may be and what can be purged from the Host A to bring it up? Thanks ilya
Logging...
Seems the logging level in 4.4 has been toned down, how do you crank it up to verbose levels?
Re: CloudStack MS wont start post db outage
Here’s a shot in the dark…. Any chance there are duplicate entries in the mshost table for your MS? On Aug 25, 2014, at 1:50 PM, ilya musayev wrote: > I'm experiencing an issue with bringing up one of 2 management hosts due to > db outage. > > Sample layout: > Host A - had running MS > Host B - MS was down due to maintenance > Host C - dedicated database host > > The database outage occurred on host C and cloudstack ms gracefully stopped > it self. As a result, i'm not able to bring up the Host A, but i could start > MS on Host B. > > IIRC, there was something cloudstack was doing to replay the uncommitted > transactions or possible kept some cached files that prevent Host A from > starting. > > Would anyone know where it may be and what can be purged from the Host A to > bring it up? > > Thanks > ilya >
cloud.keystore
In case anyone runs into the issue of cloud.keystore not being created on install on cloudstack, you can do the following. Stop cloudstack, run the following command keytool -genkey -keystore /etc/cloudstack/management/cloudmanagementserver.keystore -storepass vmops.com -keypass vmops.com -keyalg RSA -validity 3650 -dname cn="CloudstackUser",ou="Your Server FQDN",o="Your Server FQDN",c="Unknown", then restart cloudstack. According to the developers this issue will be fixed in 4.5
Re: Problem in running marvin
Thanks for the argument "install" I tried, the above specified line but I didnt know the argument - " install". On Sun, Aug 24, 2014 at 9:54 AM, Santhosh Edukulla < santhosh.eduku...@citrix.com> wrote: > Hi Sandeep, > > under /tools/marvin, run "python setup.py install", > provided you were able to build cloudstack, It should install marvin. > > Thanks! > Santhosh > > From: ilya musayev [ilya.mailing.li...@gmail.com] > Sent: Saturday, August 23, 2014 7:32 PM > To: users@cloudstack.apache.org > Subject: Re: Problem in running marvin > > Sandeep > > This question is better suited for developers mailing list - in case you > don't get a response here. > > Regards > ilya > On 8/22/14, 8:16 AM, sandeep khandekar wrote: > > Dear cloudstackers, > > > > I am trying to run the following command > > > > > http://docs.cloudstack.apache.org/en/master/developer_guide.html#installing-from-source > > > > > > under section using simulator > > * mvn -Pdeveloper,marvin.setup > > -Dmarvin.config=/home/cloudstack/cloudstack/setup/dev/basic.cfg -pl > > :cloud-marvin integration-test* > > > > I get the following error > > Traceback (most recent call last): > >File "deployAndRun.py", line 24, in > > from marvinInit import MarvinInit > >File "/home/cloudstack/cloudstack/tools/marvin/marvin/marvinInit.py", > > line 28, in > > from marvin import configGenerator > > *ImportError: No module named marvin* > > [INFO] > > > > [INFO] BUILD FAILURE > > [INFO] > > > > [INFO] Total time: 9.677s > > [INFO] Finished at: Fri Aug 22 20:42:50 IST 2014 > > [INFO] Final Memory: 30M/306M > > [INFO] > > > > [ERROR] Failed to execute goal > > org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (pre-integration-test) on > > project cloud-marvin: Command execution failed. Process exited with an > > error: 1 (Exit value: 1) -> [Help 1] > > [ERROR] > > [ERROR] To see the full stack trace of the errors, re-run Maven with the > -e > > switch. > > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > > [ERROR] > > [ERROR] For more information about the errors and possible solutions, > > please read the following articles: > > [ERROR] [Help 1] > > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > > > > Thankyou. > > -- SANDEEP KHANDEKAR Assistant Professor Department of Computer science and engineering Sreenidhi Institute of science and Technology Hyderabad
Re: CloudStack MS wont start post db outage
Nope, thats not the case :( On 8/25/14, 3:16 PM, Carlos Reátegui wrote: Here’s a shot in the dark…. Any chance there are duplicate entries in the mshost table for your MS? On Aug 25, 2014, at 1:50 PM, ilya musayev wrote: I'm experiencing an issue with bringing up one of 2 management hosts due to db outage. Sample layout: Host A - had running MS Host B - MS was down due to maintenance Host C - dedicated database host The database outage occurred on host C and cloudstack ms gracefully stopped it self. As a result, i'm not able to bring up the Host A, but i could start MS on Host B. IIRC, there was something cloudstack was doing to replay the uncommitted transactions or possible kept some cached files that prevent Host A from starting. Would anyone know where it may be and what can be purged from the Host A to bring it up? Thanks ilya
RE: Template not ready...
Hi, Is SSVM up and running in your setup? If not please bring it up. If it is already running destroy it and MS will create it and once ssvm is up again it will try to download all the templates which are not in ready state. -Sanjeev -Original Message- From: Michael Phillips [mailto:mphilli7...@hotmail.com] Sent: Tuesday, August 26, 2014 2:19 AM To: users@cloudstack.apache.org Subject: Template not ready... All, So I'm looking at the default centos 5.3 template, and it is in a "No" ready state. The only secondary storage warning\error I see in the log is the following "There is no secondary storage VM for secondary storage host secStorage". Ideas?
Re: CloudStack MS wont start post db outage
What error are you seeing in the logs? On Aug 25, 2014, at 9:04 PM, ilya musayev wrote: > Nope, thats not the case :( > On 8/25/14, 3:16 PM, Carlos Reátegui wrote: >> Here’s a shot in the dark…. >> Any chance there are duplicate entries in the mshost table for your MS? >> >> On Aug 25, 2014, at 1:50 PM, ilya musayev >> wrote: >> >>> I'm experiencing an issue with bringing up one of 2 management hosts due to >>> db outage. >>> >>> Sample layout: >>> Host A - had running MS >>> Host B - MS was down due to maintenance >>> Host C - dedicated database host >>> >>> The database outage occurred on host C and cloudstack ms gracefully stopped >>> it self. As a result, i'm not able to bring up the Host A, but i could >>> start MS on Host B. >>> >>> IIRC, there was something cloudstack was doing to replay the uncommitted >>> transactions or possible kept some cached files that prevent Host A from >>> starting. >>> >>> Would anyone know where it may be and what can be purged from the Host A to >>> bring it up? >>> >>> Thanks >>> ilya >>> >
RE: Template not ready...
All of this was related to the bug I noted on the JIRA ticket cloudstack-6378. I had to generate the keystore file properly using the keytool command. This is a bug that apparently should be fixed in 4.5 > From: sanjeev.neelar...@citrix.com > To: users@cloudstack.apache.org > Subject: RE: Template not ready... > Date: Tue, 26 Aug 2014 04:05:51 + > > Hi, > > Is SSVM up and running in your setup? If not please bring it up. If it is > already running destroy it and MS will create it and once ssvm is up again it > will try to download all the templates which are not in ready state. > > -Sanjeev > > > -Original Message- > From: Michael Phillips [mailto:mphilli7...@hotmail.com] > Sent: Tuesday, August 26, 2014 2:19 AM > To: users@cloudstack.apache.org > Subject: Template not ready... > > All, >So I'm looking at the default centos 5.3 template, and it is in a "No" > ready state. The only secondary storage warning\error I see in the log is the > following "There is no secondary storage VM for secondary storage host > secStorage". > Ideas? >
Re: cloud.keystore
Michael Thanks for sharing. Regards ilya On 8/25/14, 8:22 PM, Michael Phillips wrote: In case anyone runs into the issue of cloud.keystore not being created on install on cloudstack, you can do the following. Stop cloudstack, run the following command keytool -genkey -keystore /etc/cloudstack/management/cloudmanagementserver.keystore -storepass vmops.com -keypass vmops.com -keyalg RSA -validity 3650 -dname cn="CloudstackUser",ou="Your Server FQDN",o="Your Server FQDN",c="Unknown", then restart cloudstack. According to the developers this issue will be fixed in 4.5
Console Proxy
Console Doesn't work...did I miss something? I did the following. Changed consoleproxy.url.domain to our domain, uploaded wilcard cert and intermediate. Created entries in external dns for our IP's in format x-x-x-x. Did all that and I still can't view the console of instances. What am I missing?
RE: Console Proxy
When I select the console of an instance I would expect to see it trying to connect on x-x-x-x.domain.com, however all I see is the IP address of the management server...Is there another global setting that needs to be changed? > From: mphilli7...@hotmail.com > To: users@cloudstack.apache.org > Subject: Console Proxy > Date: Mon, 25 Aug 2014 23:54:13 -0500 > > Console Doesn't work...did I miss something? > I did the following. Changed consoleproxy.url.domain to our domain, uploaded > wilcard cert and intermediate. Created entries in external dns for our IP's > in format x-x-x-x. Did all that and I still can't view the console of > instances. What am I missing?
RE: Console Proxy
Please check the management log when you click on console proxy .it will tell you exact url. Try to check manually whether it resolve manually (try dns resolution of that url). Hope you followed the order which CS recommends.(root, intermediate and final server certificate) Regards Sadhu -Original Message- From: Michael Phillips [mailto:mphilli7...@hotmail.com] Sent: 26 August 2014 10:27 To: users@cloudstack.apache.org Subject: RE: Console Proxy When I select the console of an instance I would expect to see it trying to connect on x-x-x-x.domain.com, however all I see is the IP address of the management server...Is there another global setting that needs to be changed? > From: mphilli7...@hotmail.com > To: users@cloudstack.apache.org > Subject: Console Proxy > Date: Mon, 25 Aug 2014 23:54:13 -0500 > > Console Doesn't work...did I miss something? > I did the following. Changed consoleproxy.url.domain to our domain, uploaded > wilcard cert and intermediate. Created entries in external dns for our IP's > in format x-x-x-x. Did all that and I still can't view the console of > instances. What am I missing?
Re: Console Proxy
On Tue, Aug 26, 2014 at 6:54 AM, Michael Phillips wrote: > Console Doesn't work...did I miss something? > I did the following. Changed consoleproxy.url.domain to our domain, Just to avoid confusion, if you want to use wildcard, ie. x-y-z-zz.yourdomain.com you have to set the consoleproxy.url.domain to '*. yourdomain.com', ie. you have to include the literal star. -- Erik
Re: Console Proxy
Hi, You might need to destroy and recreate the console proxy instance - it is listening to HTTP by default in 4.3+, and when you change domain to your own domain in the global config it needs to reprogram to listen on port 443 instead. Thanks, Amogh On 8/25/14 11:02 PM, "Erik Weber" wrote: >On Tue, Aug 26, 2014 at 6:54 AM, Michael Phillips > >wrote: > >> Console Doesn't work...did I miss something? >> I did the following. Changed consoleproxy.url.domain to our domain, > > >Just to avoid confusion, if you want to use wildcard, ie. >x-y-z-zz.yourdomain.com you have to set the consoleproxy.url.domain to '*. >yourdomain.com', ie. you have to include the literal star. > > >-- >Erik
RE: Console Proxy
Wrote a blog on realhost ip "Things you should consider while changing the relahostip" in wiki. hope that will help. https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=43188254 Please review and update with your findings/comments. Regards Sadhu -Original Message- From: Erik Weber [mailto:terbol...@gmail.com] Sent: 26 August 2014 11:33 To: users@cloudstack.apache.org Subject: Re: Console Proxy On Tue, Aug 26, 2014 at 6:54 AM, Michael Phillips wrote: > Console Doesn't work...did I miss something? > I did the following. Changed consoleproxy.url.domain to our domain, Just to avoid confusion, if you want to use wildcard, ie. x-y-z-zz.yourdomain.com you have to set the consoleproxy.url.domain to '*. yourdomain.com', ie. you have to include the literal star. -- Erik
Re: acs 4.4 and GUI madness
Hello all, When 4.4.1 is planned? As described https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.4.1+BugFix+Release it should be out... On 2014.08.25. 23:40, ilya musayev wrote: > Andrei > > 4.4 has some quirks, unless you have a specific reason, i'd suggest you > remain in 4.3 until 4.4.1 is out. > > In the meantime, please log this issue and include a screenshot of what > you are seeing - so it can get addressed in the next release. > > Thanks > ilya > > On 8/25/14, 1:30 PM, Andrei Mikhailovsky wrote: >> Hello guys, >> >> I've had a few issues with the acs 4.4 GUI and I am wondering if >> anyone else is noticing it as well? It seems like things are all over >> the place and do not fit in their pre-defined areas. Things like >> Dashboard is messed up and firewall rules are practically unusable. I >> am noticing it throughout the application. I am using Chrome, but >> Firefox is having the same issues. >> >> Did something go wrong during the update? >> >> Andrei >
