System VMs not starting
I've been trying to get an new install of CloudStack 4.2 working with a Vsphere
cluster. I've went through creating my zone with advanced networking. I can see
the system VMs but they are not started. The secondary storage vm seems to keep
appearing and disappearing however. When I look in vcenter I see that vms are
being created one after another named root-2 and then root-192, root-193 etc.
They keep creating one after another until I shutdown the management service.
Here is part of the management-server.log
Has anyone seen this before. I've seen some references to bugs that sound like
this problem that were supposedly fixed back in August. I don' t know if I have
an earlier build of 4.2, but I downloaded and compiled it just last week and
I'm having this issue.
2013-12-05 00:07:28,642 WARN [utils.crypt.EncryptionSecretKeyChecker]
(Timer-2:null) Encryption already enabled, is check() called twice?
2013-12-05 00:07:29,394 DEBUG [cloud.server.ConfigurationServerImpl]
(Timer-2:null) mount: warning: /systemvm_mnt seems to be mounted read-only.
2013-12-05 00:07:30,316 INFO [xen.resource.XenServerConnectionPool]
(Timer-2:null) XenServer Connection Pool Configs:
manage.xenserver.pool.master=true; sleep.interval.on.error=1
2013-12-05 00:07:30,997 WARN [utils.crypt.EncryptionSecretKeyChecker]
(Timer-2:null) Encryption already enabled, is check() called twice?
2013-12-05 00:07:34,050 WARN [apache.cloudstack.alerts]
(Cluster-Notification-1:null) alertType:: 14 // dataCenterId:: 0 // podId:: 0
// clusterId:: null // message:: Management server node 10.2.150.100 is up
2013-12-05 00:07:34,071 WARN [cloud.cluster.ClusterManagerImpl]
(Cluster-Notification-1:null) Notifying management server join event took 39 ms
2013-12-05 00:08:33,140 ERROR [storage.resource.VmwareStorageProcessor]
(DirectAgent-2:esxi2.ammscloud.com) clone volume from base image failed due to
Exception: java.lang.RuntimeException
java.lang.RuntimeException: The name 'ROOT-2' already exists.
2013-12-05 00:08:33,145 DEBUG [agent.transport.Request] (DirectAgent-2:null)
Seq 1-1861287941: Processing: { Ans: , MgmtId: 146454222325, via: 1, Ver: v1,
Flags: 110,
[{"org.apache.cloudstack.storage.command.CopyCmdAnswer":{"result":false,"details":"java.lang.RuntimeException:
The name 'ROOT-2' already exists.","wait":0}}] }
2013-12-05 00:08:33,163 WARN [storage.datastore.ObjectInDataStoreManagerImpl]
(consoleproxy-1:null) Unsupported data object (VOLUME,
org.apache.cloudstack.storage.datastore.PrimaryDataStoreImpl@4838d3f7), no need
to delete from object in store ref table
2013-12-05 00:08:33,164 DEBUG [cloud.storage.VolumeManagerImpl]
(consoleproxy-1:null) Unable to create
Vol[2|vm=2|ROOT]:java.lang.RuntimeException: The name 'ROOT-2' already exists.
2013-12-05 00:08:33,169 INFO [cloud.vm.VirtualMachineManagerImpl]
(consoleproxy-1:null) Unable to contact resource.
com.cloud.exception.StorageUnavailableException: Resource [StoragePool:4] is
unreachable: Unable to create Vol[2|vm=2|ROOT]:java.lang.RuntimeException: The
name 'ROOT-2' already exists.
2013-12-05 00:08:56,958 ERROR [storage.resource.VmwareStorageProcessor]
(DirectAgent-4:esxi1.ammscloud.com) clone volume from base image failed due to
Exception: java.lang.RuntimeException
java.lang.RuntimeException: File [iSCSI-Datastore-1] ROOT-203/ROOT-203.vmdk was
not found
2013-12-05 00:08:56,960 DEBUG [agent.transport.Request] (DirectAgent-4:null)
Seq 2-2058223621: Processing: { Ans: , MgmtId: 146454222325, via: 2, Ver: v1,
Flags: 110,
[{"org.apache.cloudstack.storage.command.CopyCmdAnswer":{"result":false,"details":"java.lang.RuntimeException:
File [iSCSI-Datastore-1] ROOT-203/ROOT-203.vmdk was not found","wait":0}}] }
2013-12-05 00:08:56,978 WARN [storage.datastore.ObjectInDataStoreManagerImpl]
(secstorage-1:null) Unsupported data object (VOLUME,
org.apache.cloudstack.storage.datastore.PrimaryDataStoreImpl@6e0e449e), no need
to delete from object in store ref table
2013-12-05 00:08:56,979 DEBUG [cloud.storage.VolumeManagerImpl]
(secstorage-1:null) Unable to create
Vol[203|vm=203|ROOT]:java.lang.RuntimeException: File [iSCSI-Datastore-1]
ROOT-203/ROOT-203.vmdk was not found
2013-12-05 00:08:56,980 INFO [cloud.vm.VirtualMachineManagerImpl]
(secstorage-1:null) Unable to contact resource.
com.cloud.exception.StorageUnavailableException: Resource [StoragePool:4] is
unreachable: Unable to create Vol[203|vm=203|ROOT]:java.lang.RuntimeException:
File [iSCSI-Datastore-1] ROOT-203/ROOT-203.vmdk was not found
2013-12-05 00:08:57,231 DEBUG [cloud.capacity.CapacityManagerImpl]
(consoleproxy-1:null) VM state transitted from :Starting to Stopped with event:
OperationFailedvm's original host id: null new host id: null host id before
state transition: 2
2013-12-05 00:08:57,272 WARN [cloud.consoleproxy.ConsoleProxyManagerImpl]
(consoleproxy-1:null) Exception while trying to start console proxy
com.cloud.exception.InsufficientServerCapacityException: Unable to cre
Apt-get non-oss repository
Does anyone know if there are any CloudStack apt-get repositories available with the non-oss version of CloudStack built in? I'm having difficulty building the Deb packages from source and was wondering if someone had already done this. David Vosbury
Adding vmware support to my cloudstack install
I have an oss CloudStack install that I installed using a repo (installed using apt-get). I want to add the vmware support so I can use CloudStack with my vsphere cluster. Is there a way to do this without doing a complete reinstall? I've read that you have compile with the SDK for VMWare which I've tried with some limited success. I can get the compile to work, but when I try to compile to a deb package it fails on the AWS SDK compile. I haven't found a way around this yet. I'd like to just add the vmware support to my existing install if possible. Does anyone know how to do this? David Vosbury
RE: Issue building Deb packages from source
The jar files are in the maven repository. If they are corrupted where would I get replacements? Or is there some environment variable for maven that I have set so that it can find these jars? -Original Message- From: David Nalley [mailto:da...@gnsa.us] Sent: Friday, November 29, 2013 9:41 AM To: dev@cloudstack.apache.org Subject: Re: Issue building Deb packages from source Yes this - maven has either a corrupted jar or wasn't able to get the jar and is now complaining. --David On Fri, Nov 29, 2013 at 7:20 AM, Wei ZHOU wrote: > This is because the incorrect .jar file or .pom file is missing in the > maven repository, I think. > > > 2013/11/29 Saksham Srivastava > >> Can you try replacing -Dnonoss with -Dnoredist >> >> Thanks, >> Saksham >> >> -Original Message- >> From: Vosbury, David [mailto:david.vosb...@systemsmadesimple.com] >> Sent: Friday, November 29, 2013 5:31 PM >> To: dev@cloudstack.apache.org >> Subject: Issue building Deb packages from source >> >> >> >> Original Message >> Subject: Issue building Deb packages from source >> From: "Vosbury, David" >> To: d...@cloudsrack.apache.org >> CC: >> >> I'm not sure if this is a question for the users or the Dev list so >> I'm posting to both. >> >> I'm new to building CloudStack from source. I'm having some >> difficulty creating my Deb packages. I'm trying to compile with the nonoss >> options. >> I've been going through the documentation for building from source >> and I'm using the nonoss option to get the vmware support. When >> following the build docs I get successful compiles when running mvn >> clean install -Dnonoss and when doing mvn -P deps -Dnonoss (although >> I do get a message at the end of the compile that it couldn't find >> the deps profile, but the compile shows successful). When I try to >> compile to my deb packages I get an error message at the end and It also >> doesn't look like the nonoss modules build. >> It looks like a default oss build. Here is the error messages I get >> back when trying to compile the debs. Please help as I have an >> upcoming deadline to get this CloudStack install up and running and >> this is really holding me up. It seems like maybe I need to change >> something in the configuration for the deb build, but I'm not sure >> where to do that. It also seems like the deb build is failing with >> the aws api module build. Is there a way to remove that from the >> build if that is the issue? I don't need aws support at this time. Is >> there an option I need to add when doing the deb build to get the nonoss >> modules to build? Anyway, here's the error message. >> >> >> >> [INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ >> cloud-awsapi >> --- >> >> [INFO] Compiling 1296 source files to >> /home/dvosbury/apache-cloudstack-4.2.0-src >> >> /awsapi/target/classes >> >> [INFO] - >> >> [ERROR] COMPILATION ERROR : >> >> [INFO] - >> >> [ERROR] error: error reading >> /home/dvosbury/.m2/repository/org/apache/axis2/mex/ >> >> 1.5.4/mex-1.5.4-impl.jar; error in opening zip file >> >> [ERROR] error: error reading >> /home/dvosbury/.m2/repository/org/apache/axis2/axis >> >> 2-mtompolicy/1.5.4/axis2-mtompolicy-1.5.4.jar; error in opening zip >> file >> >> [ERROR] error: error reading >> /home/dvosbury/.m2/repository/org/apache/ws/commons >> >> /axiom/axiom-dom/1.2.10/axiom-dom-1.2.10.jar; error in opening zip >> file >> >> [ERROR] error: error reading >> /home/dvosbury/.m2/repository/org/opensaml/opensaml >> >> 1/1.1/opensaml1-1.1.jar; error in opening zip file >> >> [ERROR] error: error reading >> /home/dvosbury/.m2/repository/commons-lang/commons- >> >> lang/2.3/commons-lang-2.3.jar; error in opening zip file >> >> [INFO] 5 errors >> >> [INFO] - >> >> [INFO] >> - >> --- >> >> [INFO] Reactor Summary: >> >> [INFO] >> >> [INFO] Apache CloudStack . SUCCESS >> [1.890s] >> >> [INFO] Apache CloudStack Utils
Issue building Deb packages from source
Original Message Subject: Issue building Deb packages from source From: "Vosbury, David" To: d...@cloudsrack.apache.org CC: I'm not sure if this is a question for the users or the Dev list so I'm posting to both. I’m new to building CloudStack from source. I’m having some difficulty creating my Deb packages. I’m trying to compile with the nonoss options. I’ve been going through the documentation for building from source and I’m using the nonoss option to get the vmware support. When following the build docs I get successful compiles when running mvn clean install –Dnonoss and when doing mvn –P deps –Dnonoss (although I do get a message at the end of the compile that it couldn’t find the deps profile, but the compile shows successful). When I try to compile to my deb packages I get an error message at the end and It also doesn’t look like the nonoss modules build. It looks like a default oss build. Here is the error messages I get back when trying to compile the debs. Please help as I have an upcoming deadline to get this CloudStack install up and running and this is really holding me up. It seems like maybe I need to change something in the configuration for the deb build, but I’m not sure where to do that. It also seems like the deb build is failing with the aws api module build. Is there a way to remove that from the build if that is the issue? I don’t need aws support at this time. Is there an option I need to add when doing the deb build to get the nonoss modules to build? Anyway, here’s the error message. [INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ cloud-awsapi --- [INFO] Compiling 1296 source files to /home/dvosbury/apache-cloudstack-4.2.0-src /awsapi/target/classes [INFO] - [ERROR] COMPILATION ERROR : [INFO] - [ERROR] error: error reading /home/dvosbury/.m2/repository/org/apache/axis2/mex/ 1.5.4/mex-1.5.4-impl.jar; error in opening zip file [ERROR] error: error reading /home/dvosbury/.m2/repository/org/apache/axis2/axis 2-mtompolicy/1.5.4/axis2-mtompolicy-1.5.4.jar; error in opening zip file [ERROR] error: error reading /home/dvosbury/.m2/repository/org/apache/ws/commons /axiom/axiom-dom/1.2.10/axiom-dom-1.2.10.jar; error in opening zip file [ERROR] error: error reading /home/dvosbury/.m2/repository/org/opensaml/opensaml 1/1.1/opensaml1-1.1.jar; error in opening zip file [ERROR] error: error reading /home/dvosbury/.m2/repository/commons-lang/commons- lang/2.3/commons-lang-2.3.jar; error in opening zip file [INFO] 5 errors [INFO] - [INFO] [INFO] Reactor Summary: [INFO] [INFO] Apache CloudStack . SUCCESS [1.890s] [INFO] Apache CloudStack Utils ... SUCCESS [10.227s] [INFO] Apache CloudStack API . SUCCESS [10.884s] [INFO] Apache CloudStack Framework ... SUCCESS [0.072s] [INFO] Apache CloudStack Framework - REST SUCCESS [2.908s] [INFO] Apache CloudStack Framework - IPC . SUCCESS [4.501s] [INFO] Apache CloudStack Cloud Engine SUCCESS [0.062s] [INFO] Apache CloudStack Cloud Engine API SUCCESS [5.064s] [INFO] Apache CloudStack Cloud Engine Internal Components API SUCCESS [1.810s] [INFO] Apache CloudStack Cloud Engine Schema Component ... SUCCESS [9.314s] [INFO] Apache CloudStack Core SUCCESS [7.708s] [INFO] Apache CloudStack Agents .. SUCCESS [5.966s] [INFO] Apache CloudStack Framework - Jobs SUCCESS [1.623s] [INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [1.682s] [INFO] Apache CloudStack Server .. SUCCESS [18.616s] [INFO] Apache CloudStack Usage Server SUCCESS [5.502s] [INFO] Apache XenSource XAPI . SUCCESS [5.961s] [INFO] Apache CloudStack Cloud Engine Compute Component .. SUCCESS [1.753s] [INFO] Apache CloudStack Cloud Engine Orchestration Component SUCCESS [5.525s] [INFO] Apache
