VM????????
VMrouter?? WARN [network.router.VirtualNetworkApplianceManagerImpl] (RouterMonitor-1:) Error while collecting network stats from router: r-1321-VM from host: 2; details: Exception: com.cloud.utils.exception.CloudRuntimeException Message: callHostPlugin failed for cmd: routerProxy with args args: netusage.sh 169.254.2.198 -g, due to Failed to create input stream: Read timed out Stack: com.cloud.utils.exception.CloudRuntimeException: callHostPlugin failed for cmd: routerProxy with args args: netusage.sh 169.254.2.198 -g, due to Failed to create input stream: Read timed out at com.cloud.hypervisor.xen.resource.CitrixResourceBase.callHostPlugin(CitrixResourceBase.java:3713) at com.cloud.hypervisor.xen.resource.XenServer56Resource.networkUsage(XenServer56Resource.java:150) at com.cloud.hypervisor.xen.resource.CitrixResourceBase.getNetworkStats(CitrixResourceBase.java:2037) at com.cloud.hypervisor.xen.resource.XenServer56Resource.execute(XenServer56Resource.java:211) at com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:53) at com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:187) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679)
Re: XMPP Server on CloudStack Management Server
You could definitely use xmpp as command and control in your instances. This has been done before : http://archipelproject.org You could write xmpp hooks to call the cloudstack api as well I used to be involved in this project: https://github.com/legastero/Kestrel Which allowed you to run batch processing jobs on pools of VMs using XMPP. On Jun 1, 2014, at 5:59 AM, hossein zabolzadeh zabolza...@gmail.com wrote: @David Thanks. On Sun, Jun 1, 2014 at 2:16 PM, Nux! n...@li.nux.ro wrote: On 01.06.2014 10:21, hossein zabolzadeh wrote: @David AMQP is not instance messaging. Does the cloudstack use AMPQ for its message passing mechanism? http://www.chipchilders.com/blog/2013/7/16/tapping-into- apache-cloudstack-events-via-amqp.html -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro
Re: Usage Server in 4.3
On May 30, 2014, at 1:07 PM, Fabrice Brazier fabrice.braz...@apalia.net wrote: Thanks Sébastien. Fabrice -Message d'origine- De : sebgoa [mailto:run...@gmail.com] Envoyé : vendredi 30 mai 2014 18:37 À : users@cloudstack.apache.org Objet : Re: Usage Server in 4.3 On May 30, 2014, at 5:02 PM, Fabrice Brazier fabrice.braz...@apalia.net wrote: Hi David, There was an issue with mysql connector. Starting 4.3 mysql connector is no longer bundled with ACS. I created a symbolic link to make it available to usage server: ln -s /usr/share/java/mysql-connector-java.jar /usr/share/cloudstack-usage/lib/mysql-connector-java.jar This issue is being added to 4.3 release docs. I will do that today, and FWIW this issue is fixed in 4.4 and master. Let me know if there are further issues: http://docs.cloudstack.apache.org/projects/cloudstack-installation/en/latest/installation.html#install-on-ubuntu Usage server is working fine now. Regards, Fabrice -Message d'origine- De : David Matteson [mailto:dmatte...@a2hosting.com] Envoyé : vendredi 30 mai 2014 16:52 À : users@cloudstack.apache.org Objet : Usage Server in 4.3 Hey all, We upgraded to 4.3 yesterday and now the usage server gives the following error: java.sql.SQLException: No suitable driver found for jdbc:mysql://127.0.0.1:3306/cloud?autoReconnect=trueprepStmtCacheSize =517 cachePrepStmts=true Anyone else run into this or have a solution? Thanks!
Re: Problem when using Cloudstack Login API
On Sun, Jun 1, 2014 at 10:51 PM, dimas yoga pratama smid...@gmail.com
wrote:
Hi All,
I'm doing an experiment on using Cloudstack API.
From what I read here
http://cloudstack.apache.org/docs/api/apidocs-4.3/user/login.html when the
login succeeds,it will generate cookie JSESSIONID.
My question is, when I create login page, and succsfull login will redirect
to another page, do I have to pass JSESSIONID to another page like
SESSIONKEY?
Here's an example with curl.
Remember that parameters has to be encoded if they contain any kind of
special characters.
Login:
curl -i '
http://localhost:8080/client/api?command=loginuser=adminpassword=MyPasswordresponse=json
'
returns a snippet like this:
Set-Cookie: JSESSIONID=07CA185081E6A476775ECA9D190EF1F8; Path=/client
{ loginresponse : { timeout : 1800, lastname : cloud,
registered : false, username : admin, firstname : admin,
domainid : 6f920fbd-94fc-11e3-b2e0-0050568c15a3, type : 1, userid
: d68e7072-94fc-11e3-b2e0-0050568c15a3, sessionkey :
WxjAu9zZzbmrBGDarnW1cVfm+/g=, account : admin } }
Then you take the JSESSIONID and sessionkey and pass them as Ove said.
List Zones example using above
curl -i -H Cookie: JSESSIONID=07CA185081E6A476775ECA9D190EF1F8;
Path=/client '
http://localhost:8008/client/api?command=listZonessessionkey=WxjAu9zZzbmrBGDarnW1cVfm%2B%2Fg%3Dresponse=json
'
--
Erik Weber
CS 4.3 Centos default template not ready
Hi, Is there a way to force download the default centos template for cloudstack 4.3? I have checked all means of why it is not downloading. The CS setup was refreshed from a setup done before. I flushed all tables, deleted previous files in nfs mounts and re-run cloudstack database setup previous before stumbling into this problem of cloudstack template not downloading. The systemvm template however successfully downloaded, both sysvm and console proxy vm is started on my Xen 6.2 ... anyone has any tips where i could look at to resolve this? Blog.CripperZ.SG - Tech Tips Talk #CripperzProdigy (Irc.Freenode.Net)
RE: CS 4.3 Centos default template not ready
Take a look at https://cwiki.apache.org/confluence/display/CLOUDSTACK/SSVM,+templates,+Secondary+storage+troubleshooting This guides you through trouble shooting SSVM issues. One thing I always check after the SSVM has come on line is that the System VM Template has a value in the size property. If it doesn’t its because the SSVM either cannot read Sec Storage, or cannot communicate back to the Management Server. The status of the CentOS Template normally gives you some clues such as 'no root to host' etc Regards Geoff Higginbottom D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581 geoff.higginbot...@shapeblue.com -Original Message- From: CP Yahoo Mail [mailto:cripp...@yahoo.com.sg] Sent: 02 June 2014 08:56 To: users@cloudstack.apache.org Subject: CS 4.3 Centos default template not ready Hi, Is there a way to force download the default centos template for cloudstack 4.3? I have checked all means of why it is not downloading. The CS setup was refreshed from a setup done before. I flushed all tables, deleted previous files in nfs mounts and re-run cloudstack database setup previous before stumbling into this problem of cloudstack template not downloading. The systemvm template however successfully downloaded, both sysvm and console proxy vm is started on my Xen 6.2 ... anyone has any tips where i could look at to resolve this? Blog.CripperZ.SG - Tech Tips Talk #CripperzProdigy (Irc.Freenode.Net) Find out more about ShapeBlue and our range of CloudStack related services IaaS Cloud Design Buildhttp://shapeblue.com/iaas-cloud-design-and-build// CSForge – rapid IaaS deployment frameworkhttp://shapeblue.com/csforge/ CloudStack Consultinghttp://shapeblue.com/cloudstack-consultancy/ CloudStack Infrastructure Supporthttp://shapeblue.com/cloudstack-infrastructure-support/ CloudStack Bootcamp Training Courseshttp://shapeblue.com/cloudstack-training/ This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Shape Blue Ltd is a company incorporated in England Wales. ShapeBlue Services India LLP is a company incorporated in India and is operated under license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is operated under license from Shape Blue Ltd. ShapeBlue is a registered trademark.
CloudStack and IPv6
Hello everyone Soon I'm going to get /64 IPv6 block and I'm wondering if anyone has any experience dealing with IPv6 . I would like to use IPv6 for my public traffic, however I would like to maintain IPv4 for internal / private networks. Can this be achieved with IPv6? Dean
[URGENT] cannot access management server after restarting service
Hi, Ok this is my problem, I change parameter in global settings, and I unset some value and I restarted the management server using service cloudstack-management restart. I tried to access the MS back in http://10.151.32.51:8080/client/ and no luck, it returned 404 resource not available. Is it a bug or something? How I can get my MS back? looking forward for your answer,
Re: [URGENT] cannot access management server after restarting service
On Mon, Jun 2, 2014 at 11:20 PM, dimas yoga pratama smid...@gmail.com wrote: Hi, Ok this is my problem, I change parameter in global settings, and I unset some value and I restarted the management server using service cloudstack-management restart. I tried to access the MS back in http://10.151.32.51:8080/client/ and no luck, it returned 404 resource not available. Is it a bug or something? How I can get my MS back? looking forward for your answer, What does your management log say? -- Erik Weber
Re: [URGENT] cannot access management server after restarting service
You should probably start by including what parameter(s) you changed and any relavent log entries. On Jun 2, 2014, at 2:20 PM, dimas yoga pratama smid...@gmail.com wrote: Hi, Ok this is my problem, I change parameter in global settings, and I unset some value and I restarted the management server using service cloudstack-management restart. I tried to access the MS back in http://10.151.32.51:8080/client/ and no luck, it returned 404 resource not available. Is it a bug or something? How I can get my MS back? looking forward for your answer,
Re: [URGENT] cannot access management server after restarting service
I accidentally unset vm limit in global settings, how to restore it? is it possible to change it via database? On Tue, Jun 3, 2014 at 4:38 AM, dimas yoga pratama smid...@gmail.com wrote: Ok I found the error now, How I revert back my configuration? 2014-06-03 04:13:41,608 ERROR [c.c.r.ResourceLimitManagerImpl] (main:null) NumberFormatException during configuration java.lang.NumberFormatException: null at java.lang.Long.parseLong(Long.java:404) at java.lang.Long.parseLong(Long.java:483) at com.cloud.resourcelimit.ResourceLimitManagerImpl.configure(ResourceLimitManagerImpl.java:231) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle$3.with(CloudStackExtendedLifeCycle.java:117) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.with(CloudStackExtendedLifeCycle.java:156) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.configure(CloudStackExtendedLifeCycle.java:113) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.start(CloudStackExtendedLifeCycle.java:59) at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:167) at org.springframework.context.support.DefaultLifecycleProcessor.access$200(DefaultLifecycleProcessor.java:51) at org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:339) at org.springframework.context.support.DefaultLifecycleProcessor.startBeans(DefaultLifecycleProcessor.java:143) at org.springframework.context.support.DefaultLifecycleProcessor.onRefresh(DefaultLifecycleProcessor.java:108) at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:945) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:482) 2014-06-03 04:13:41,609 ERROR [o.a.c.s.l.CloudStackExtendedLifeCycle] (main:null) Failed to configure ResourceLimitManagerImpl javax.naming.ConfigurationException: Configuration failed due to NumberFormatException, see log for the stacktrace at com.cloud.resourcelimit.ResourceLimitManagerImpl.configure(ResourceLimitManagerImpl.java:241) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle$3.with(CloudStackExtendedLifeCycle.java:117) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.with(CloudStackExtendedLifeCycle.java:156) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.configure(CloudStackExtendedLifeCycle.java:113) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.start(CloudStackExtendedLifeCycle.java:59) at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:167) at org.springframework.context.support.DefaultLifecycleProcessor.access$200(DefaultLifecycleProcessor.java:51) at org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:339) On Tue, Jun 3, 2014 at 4:22 AM, Bret Mette bret.me...@dbihosting.com wrote: You should probably start by including what parameter(s) you changed and any relavent log entries. On Jun 2, 2014, at 2:20 PM, dimas yoga pratama smid...@gmail.com wrote: Hi, Ok this is my problem, I change parameter in global settings, and I unset some value and I restarted the management server using service cloudstack-management restart. I tried to access the MS back in http://10.151.32.51:8080/client/ and no luck, it returned 404 resource not available. Is it a bug or something? How I can get my MS back? looking forward for your answer,
Re: [URGENT] cannot access management server after restarting service
Yes its definitely possible, look for configuration table in cloud db. For ease of use, install mysql workbench, if you haven't done so already. On 6/2/14, 3:04 PM, dimas yoga pratama wrote: I accidentally unset vm limit in global settings, how to restore it? is it possible to change it via database? On Tue, Jun 3, 2014 at 4:38 AM, dimas yoga pratama smid...@gmail.com wrote: Ok I found the error now, How I revert back my configuration? 2014-06-03 04:13:41,608 ERROR [c.c.r.ResourceLimitManagerImpl] (main:null) NumberFormatException during configuration java.lang.NumberFormatException: null at java.lang.Long.parseLong(Long.java:404) at java.lang.Long.parseLong(Long.java:483) at com.cloud.resourcelimit.ResourceLimitManagerImpl.configure(ResourceLimitManagerImpl.java:231) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle$3.with(CloudStackExtendedLifeCycle.java:117) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.with(CloudStackExtendedLifeCycle.java:156) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.configure(CloudStackExtendedLifeCycle.java:113) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.start(CloudStackExtendedLifeCycle.java:59) at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:167) at org.springframework.context.support.DefaultLifecycleProcessor.access$200(DefaultLifecycleProcessor.java:51) at org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:339) at org.springframework.context.support.DefaultLifecycleProcessor.startBeans(DefaultLifecycleProcessor.java:143) at org.springframework.context.support.DefaultLifecycleProcessor.onRefresh(DefaultLifecycleProcessor.java:108) at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:945) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:482) 2014-06-03 04:13:41,609 ERROR [o.a.c.s.l.CloudStackExtendedLifeCycle] (main:null) Failed to configure ResourceLimitManagerImpl javax.naming.ConfigurationException: Configuration failed due to NumberFormatException, see log for the stacktrace at com.cloud.resourcelimit.ResourceLimitManagerImpl.configure(ResourceLimitManagerImpl.java:241) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle$3.with(CloudStackExtendedLifeCycle.java:117) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.with(CloudStackExtendedLifeCycle.java:156) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.configure(CloudStackExtendedLifeCycle.java:113) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.start(CloudStackExtendedLifeCycle.java:59) at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:167) at org.springframework.context.support.DefaultLifecycleProcessor.access$200(DefaultLifecycleProcessor.java:51) at org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:339) On Tue, Jun 3, 2014 at 4:22 AM, Bret Mette bret.me...@dbihosting.com wrote: You should probably start by including what parameter(s) you changed and any relavent log entries. On Jun 2, 2014, at 2:20 PM, dimas yoga pratama smid...@gmail.com wrote: Hi, Ok this is my problem, I change parameter in global settings, and I unset some value and I restarted the management server using service cloudstack-management restart. I tried to access the MS back in http://10.151.32.51:8080/client/ and no luck, it returned 404 resource not available. Is it a bug or something? How I can get my MS back? looking forward for your answer,
RE: [URGENT] cannot access management server after restarting service
Make sure that tomcat server is running. Please check /var/log/cloudstack/management/catalina.out file for any errors in bringing up tomcat server. -Sanjeev -Original Message- From: ilya musayev [mailto:ilya.mailing.li...@gmail.com] Sent: Tuesday, June 03, 2014 4:02 AM To: users@cloudstack.apache.org Subject: Re: [URGENT] cannot access management server after restarting service Yes its definitely possible, look for configuration table in cloud db. For ease of use, install mysql workbench, if you haven't done so already. On 6/2/14, 3:04 PM, dimas yoga pratama wrote: I accidentally unset vm limit in global settings, how to restore it? is it possible to change it via database? On Tue, Jun 3, 2014 at 4:38 AM, dimas yoga pratama smid...@gmail.com wrote: Ok I found the error now, How I revert back my configuration? 2014-06-03 04:13:41,608 ERROR [c.c.r.ResourceLimitManagerImpl] (main:null) NumberFormatException during configuration java.lang.NumberFormatException: null at java.lang.Long.parseLong(Long.java:404) at java.lang.Long.parseLong(Long.java:483) at com.cloud.resourcelimit.ResourceLimitManagerImpl.configure(ResourceLimitManagerImpl.java:231) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle$3.with(CloudStackExtendedLifeCycle.java:117) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.with(CloudStackExtendedLifeCycle.java:156) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.configure(CloudStackExtendedLifeCycle.java:113) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.start(CloudStackExtendedLifeCycle.java:59) at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:167) at org.springframework.context.support.DefaultLifecycleProcessor.access$200(DefaultLifecycleProcessor.java:51) at org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:339) at org.springframework.context.support.DefaultLifecycleProcessor.startBeans(DefaultLifecycleProcessor.java:143) at org.springframework.context.support.DefaultLifecycleProcessor.onRefresh(DefaultLifecycleProcessor.java:108) at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:945) at org.springframework.context.support.AbstractApplicationContext.refres h(AbstractApplicationContext.java:482) 2014-06-03 04:13:41,609 ERROR [o.a.c.s.l.CloudStackExtendedLifeCycle] (main:null) Failed to configure ResourceLimitManagerImpl javax.naming.ConfigurationException: Configuration failed due to NumberFormatException, see log for the stacktrace at com.cloud.resourcelimit.ResourceLimitManagerImpl.configure(ResourceLimitManagerImpl.java:241) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle$3.with(CloudStackExtendedLifeCycle.java:117) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.with(CloudStackExtendedLifeCycle.java:156) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.configure(CloudStackExtendedLifeCycle.java:113) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.start(CloudStackExtendedLifeCycle.java:59) at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:167) at org.springframework.context.support.DefaultLifecycleProcessor.access$200(DefaultLifecycleProcessor.java:51) at org.springframework.context.support.DefaultLifecycleProcessor$Lifecyc leGroup.start(DefaultLifecycleProcessor.java:339) On Tue, Jun 3, 2014 at 4:22 AM, Bret Mette bret.me...@dbihosting.com wrote: You should probably start by including what parameter(s) you changed and any relavent log entries. On Jun 2, 2014, at 2:20 PM, dimas yoga pratama smid...@gmail.com wrote: Hi, Ok this is my problem, I change parameter in global settings, and I unset some value and I restarted the management server using service cloudstack-management restart. I tried to access the MS back in http://10.151.32.51:8080/client/ and no luck, it returned 404 resource not available. Is it a bug or something? How I can get my MS back? looking forward for your answer,
