Re:回复: cloudstack主存使用ceph挂载失败。
我是这样填的 。
RADOS Monitor:172.16.100.5
RADOS POOL: pool
RADOS User: admin
RADOS Secret: AQDRJf9TgAdxBxAAVLF0d2RsefehcLT9WaYReg==
另外 ceph配置文件里 验证都是none
auth cluster required = none
auth service required = none
auth client required = none
auth supported = none
在2014年08月29 12时56分, aix.niuyaix.n...@gmail.com写道:
RADOS User: 怎么填的？
把创建主存储的信息加一下 RADOS User: 是否用了client.x 如果是请把client.去掉 再次尝试
2014-08-29
aix.niuy
发件人：gufei gufei...@163.com
发送时间：2014-08-29 11:29
主题：cloudstack主存使用ceph挂载失败。
收件人：users-cn@cloudstack.apache.orgusers-cn@cloudstack.apache.org
抄送：
使用ceph挂载主存储时失败 ，但可以在命令行使用rbd挂载。哪位有这方面的经验。
日志
2014-08-29 11:23:06,808{GMT} WARN [cloud.agent.Agent]
(agentRequest-Handler-5:) Caught:
com.cloud.utils.exception.CloudRuntimeException: Failed to create storage pool:
6e029116-7061-3eaa-a00d-5d9acdc7c413
at
com.cloud.hypervisor.kvm.storage.LibvirtStorageAdaptor.createStoragePool(LibvirtStorageAdaptor.java:524)
at
com.cloud.hypervisor.kvm.storage.KVMStoragePoolManager.createStoragePool(KVMStoragePoolManager.java:277)
at
com.cloud.hypervisor.kvm.storage.KVMStoragePoolManager.createStoragePool(KVMStoragePoolManager.java:271)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:2813)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1325)
at com.cloud.agent.Agent.processRequest(Agent.java:501)
at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808)
at com.cloud.utils.nio.Task.run(Task.java:84)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
回复: Re:回复: cloudstack主存使用ceph挂载失败。
没有做过不验证的测试，再等等其他人吧
2014-08-29
aix.niuy
发件人：gufei gufei...@163.com
发送时间：2014-08-29 14:38
主题：Re:回复: cloudstack主存使用ceph挂载失败。
收件人：users-cn@cloudstack.apache.orgusers-cn@cloudstack.apache.org
抄送：
我是这样填的 。
RADOS Monitor:172.16.100.5
RADOS POOL: pool
RADOS User: admin
RADOS Secret: AQDRJf9TgAdxBxAAVLF0d2RsefehcLT9WaYReg==
另外 ceph配置文件里 验证都是none
auth cluster required = none
auth service required = none
auth client required = none
auth supported = none
在2014年08月29 12时56分, aix.niuyaix.n...@gmail.com写道:
RADOS User: 怎么填的？
把创建主存储的信息加一下 RADOS User: 是否用了client.x 如果是请把client.去掉 再次尝试
2014-08-29
aix.niuy
发件人：gufei gufei...@163.com
发送时间：2014-08-29 11:29
主题：cloudstack主存使用ceph挂载失败。
收件人：users-cn@cloudstack.apache.orgusers-cn@cloudstack.apache.org
抄送：
使用ceph挂载主存储时失败 ，但可以在命令行使用rbd挂载。哪位有这方面的经验。
日志
2014-08-29 11:23:06,808{GMT} WARN [cloud.agent.Agent]
(agentRequest-Handler-5:) Caught:
com.cloud.utils.exception.CloudRuntimeException: Failed to create storage pool:
6e029116-7061-3eaa-a00d-5d9acdc7c413
at
com.cloud.hypervisor.kvm.storage.LibvirtStorageAdaptor.createStoragePool(LibvirtStorageAdaptor.java:524)
at
com.cloud.hypervisor.kvm.storage.KVMStoragePoolManager.createStoragePool(KVMStoragePoolManager.java:277)
at
com.cloud.hypervisor.kvm.storage.KVMStoragePoolManager.createStoragePool(KVMStoragePoolManager.java:271)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:2813)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1325)
at com.cloud.agent.Agent.processRequest(Agent.java:501)
at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808)
at com.cloud.utils.nio.Task.run(Task.java:84)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
Re:回复: Re:回复: cloudstack主存使用ceph挂载失败。
谢谢。
日志里报错信息太少 。
在2014年08月29 14时45分, aix.niuyaix.n...@gmail.com写道:
没有做过不验证的测试，再等等其他人吧
2014-08-29
aix.niuy
发件人：gufei gufei...@163.com
发送时间：2014-08-29 14:38
主题：Re:回复: cloudstack主存使用ceph挂载失败。
收件人：users-cn@cloudstack.apache.orgusers-cn@cloudstack.apache.org
抄送：
我是这样填的 。
RADOS Monitor:172.16.100.5
RADOS POOL: pool
RADOS User: admin
RADOS Secret: AQDRJf9TgAdxBxAAVLF0d2RsefehcLT9WaYReg==
另外 ceph配置文件里 验证都是none
auth cluster required = none
auth service required = none
auth client required = none
auth supported = none
在2014年08月29 12时56分, aix.niuyaix.n...@gmail.com写道:
RADOS User: 怎么填的？
把创建主存储的信息加一下 RADOS User: 是否用了client.x 如果是请把client.去掉 再次尝试
2014-08-29
aix.niuy
发件人：gufei gufei...@163.com
发送时间：2014-08-29 11:29
主题：cloudstack主存使用ceph挂载失败。
收件人：users-cn@cloudstack.apache.orgusers-cn@cloudstack.apache.org
抄送：
使用ceph挂载主存储时失败 ，但可以在命令行使用rbd挂载。哪位有这方面的经验。
日志
2014-08-29 11:23:06,808{GMT} WARN [cloud.agent.Agent]
(agentRequest-Handler-5:) Caught:
com.cloud.utils.exception.CloudRuntimeException: Failed to create storage pool:
6e029116-7061-3eaa-a00d-5d9acdc7c413
at
com.cloud.hypervisor.kvm.storage.LibvirtStorageAdaptor.createStoragePool(LibvirtStorageAdaptor.java:524)
at
com.cloud.hypervisor.kvm.storage.KVMStoragePoolManager.createStoragePool(KVMStoragePoolManager.java:277)
at
com.cloud.hypervisor.kvm.storage.KVMStoragePoolManager.createStoragePool(KVMStoragePoolManager.java:271)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:2813)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1325)
at com.cloud.agent.Agent.processRequest(Agent.java:501)
at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808)
at com.cloud.utils.nio.Task.run(Task.java:84)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
AW: Stale datastores in database?
Hi!
Sorry, it is Cloudstack 4.4.0.
Here's a piece of the log file:
2014-08-29 09:06:15,853 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl]
(RouterStatusMonitor-1:ctx-d40f3eb8) Found 0 routers to update status.
2014-08-29 09:06:15,855 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl]
(RouterStatusMonitor-1:ctx-d40f3eb8) Found 0 networks to update RvR status.
2014-08-29 09:06:20,894 DEBUG [o.a.c.f.j.d.VmWorkJobDaoImpl]
(Vm-Operations-Cleanup-1:ctx-53d42538) Expunge completed work job-4952
2014-08-29 09:06:20,897 DEBUG [o.a.c.f.j.d.VmWorkJobDaoImpl]
(Vm-Operations-Cleanup-1:ctx-53d42538) Expunge completed work job-4953
2014-08-29 09:06:25,120 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
Timer:ctx-cc3c8ca6) Resetting hosts suitable for reconnect
2014-08-29 09:06:25,121 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
Timer:ctx-cc3c8ca6) Completed resetting hosts suitable for reconnect
2014-08-29 09:06:25,121 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
Timer:ctx-cc3c8ca6) Acquiring hosts for clusters already owned by this
management server
2014-08-29 09:06:25,123 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
Timer:ctx-cc3c8ca6) Completed acquiring hosts for clusters already owned by
this management server
2014-08-29 09:06:25,123 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
Timer:ctx-cc3c8ca6) Acquiring hosts for clusters not owned by any management
server
2014-08-29 09:06:25,124 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
Timer:ctx-cc3c8ca6) Completed acquiring hosts for clusters not owned by any
management server
2014-08-29 09:06:31,644 DEBUG [c.c.s.StatsCollector]
(StatsCollector-3:ctx-c9fb6895) StorageCollector is running...
2014-08-29 09:06:31,703 DEBUG [c.c.a.t.Request] (StatsCollector-3:ctx-c9fb6895)
Seq 11-6232137459350635412: Received: { Ans: , MgmtId: 220037193816942, via:
11, Ver: v1, Flags: 10, { GetStorageStatsAnswer } }
2014-08-29 09:06:31,707 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-210:ctx-6e881c4a) Seq 10-5576019288638097197: Executing request
2014-08-29 09:06:31,893 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-210:ctx-6e881c4a) Seq 10-5576019288638097197: Response Received:
2014-08-29 09:06:31,893 DEBUG [c.c.a.t.Request] (StatsCollector-3:ctx-c9fb6895)
Seq 10-5576019288638097197: Received: { Ans: , MgmtId: 220037193816942, via:
10, Ver: v1, Flags: 10, { GetStorageStatsAnswer } }
2014-08-29 09:06:32,444 DEBUG [c.c.s.StatsCollector]
(StatsCollector-4:ctx-1099b9be) AutoScaling Monitor is running...
2014-08-29 09:06:32,750 DEBUG [c.c.a.m.AgentManagerImpl]
(AgentManager-Handler-1:null) Ping from 11
2014-08-29 09:06:33,603 DEBUG [c.c.c.ConsoleProxyManagerImpl]
(consoleproxy-1:ctx-fc6cda67) Zone 1 is ready to launch console proxy
2014-08-29 09:06:33,604 DEBUG [c.c.c.ConsoleProxyManagerImpl]
(consoleproxy-1:ctx-fc6cda67) Expand console proxy standby capacity for zone
ESC-KL
2014-08-29 09:06:33,607 INFO [c.c.c.ConsoleProxyManagerImpl]
(consoleproxy-1:ctx-fc6cda67) Found a stopped console proxy, bring it up to
running pool. proxy vm id : 36
2014-08-29 09:06:33,615 DEBUG [o.a.c.s.SecondaryStorageManagerImpl]
(secstorage-1:ctx-6d3000ae) Zone 1 is ready to launch secondary storage VM
2014-08-29 09:06:33,619 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(consoleproxy-1:ctx-fc6cda67) Sync job-4954 execution on object
VmWorkJobQueue.36
2014-08-29 09:06:33,622 WARN [c.c.u.d.Merovingian2]
(consoleproxy-1:ctx-fc6cda67) Was unable to find lock for the key vm_instance36
and thread id 974875322
2014-08-29 09:06:33,852 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(AsyncJobMgr-Heartbeat-1:ctx-35c0dfca) Execute sync-queue item: SyncQueueItemVO
{id:4837, queueId: 2963, contentType: AsyncJob, contentId: 4954,
lastProcessMsid: null, lastprocessNumber: null, lastProcessTime: null, created:
Fri Aug 29 09:06:33 CEST 2014}
2014-08-29 09:06:33,854 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(AsyncJobMgr-Heartbeat-1:ctx-35c0dfca) Schedule queued job-4954
2014-08-29 09:06:33,857 INFO [o.a.c.f.j.i.AsyncJobMonitor]
(Work-Job-Executor-48:ctx-ffc7a4fc job-3068/job-4954) Add job-4954 into job
monitoring
2014-08-29 09:06:33,857 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Work-Job-Executor-48:ctx-ffc7a4fc job-3068/job-4954) Executing AsyncJobVO
{id:4954, userId: 1, accountId: 1, instanceType: null, instanceId: null, cmd:
com.cloud.vm.VmWorkStart, cmdInfo:
AW: Downloading new templates blocked?
Yes, it's an internal server Thanks for the hint! Ciao Martin -Ursprüngliche Nachricht- Von: Kirk Kosinski [mailto:kirkkosin...@gmail.com] Gesendet: Donnerstag, 28. August 2014 22:28 An: users@cloudstack.apache.org Betreff: Re: Downloading new templates blocked? Hi, Martin. Is your web server on an internal (RFC 1918) network? If so you need to add the CIDR to secstorage.allowed.internal.sites in Global Settings. Best regards, Kirk
Vm can not get IP address in Advanced Zone under some situation
Hi, I configured the zone as Advanced Zone. Guest Vm can not get IP address when it's Virtual Router is not? on the same host with the Vm. Could you help answer this question? Best Regard ro...@cywee.com
AW: Vm can not get IP address in Advanced Zone under some situation
Your VLAN range for Guest network must be trunked in all switchports on which your hosts Guest networks connected... -Ursprüngliche Nachricht- Von: ro...@cywee.com [mailto:ro...@cywee.com] Gesendet: Freitag, 29. August 2014 09:53 An: cloudusersusers Betreff: Vm can not get IP address in Advanced Zone under some situation Hi, I configured the zone as Advanced Zone. Guest Vm can not get IP address when it's Virtual Router is not? on the same host with the Vm. Could you help answer this question? Best Regard ro...@cywee.com
RE: Failed Site-to-Site VPN 4.4.0 - Error due semicolon
Thanks Erik for your response. My colleagues have resolved this issue in CS 4.4.0 modifying one script in XenServer, at least we have VPN Site-to-Site tunnels with this version. I hope this issue is resolved with CS 4.4.1 Best -Mensaje original- De: Erik Weber [mailto:terbol...@gmail.com] Enviado el: jueves, 28 de agosto de 2014 22:05 Para: users@cloudstack.apache.org Asunto: Re: Failed Site-to-Site VPN 4.4.0 - Error due semicolon On Thu, Aug 28, 2014 at 8:53 PM, David Amorín david.amo...@adderglobal.com wrote: Hi, We are having issues to establish VPN Site-to-Site with our VPC based in CS 4.4.0 We see this issue already identified https://issues.apache.org/jira/browse/CLOUDSTACK-7124 but it says that only affects the version 4.5.0. Can somebody confirm if this issue affects also the version 4.4.0? My experience is that 'Affected version(s)' is entered with the version someone first experience it in. That doesn't mean it doesn't exist in any other release. If you have the same error message and have excluded typos etc. it is very likely that you experience the same bug. -- Erik
http://cloudstack.org/dl/cloud-set-guest-password not working
We are still at 4.1.1 CS. Using the documentation for 4.1.1. gives the link for password set script to: http://cloudstack.org/dl/cloud-set-guest-password This is no longer valid. Where could i get the password script nowdays from? Tnx. F.
Re: http://cloudstack.org/dl/cloud-set-guest-password not working
Hi France, One of the shapeblue guys has them uploaded to github: https://github.com/shankerbalan/cloudstack-scripts Hope this helps, ian On 29 August 2014 10:11, France mailingli...@isg.si wrote: We are still at 4.1.1 CS. Using the documentation for 4.1.1. gives the link for password set script to: http://cloudstack.org/dl/cloud-set-guest-password This is no longer valid. Where could i get the password script nowdays from? Tnx. F.
RE: Re: About sharepoint mode in CloudStack
Yes, Cloudstack uses an MS SQL server for data, we've created our own message bus with MS Exchange and the interface is going to be accessed through a MS Word add-in going forwards :-) Kind Regards Giles D: +44 20 3603 0541 | M: +44 796 111 2055 giles.sir...@shapeblue.com -Original Message- From: Dave Dunaway [mailto:dave.duna...@gmail.com] Sent: 28 August 2014 10:29 To: users@cloudstack.apache.org Subject: Re: Re: About sharepoint mode in CloudStack OMG...it has to be since it's too early where I am, but I almost puked thinking somehow Cloudplatform was using MS Sharepoint to store docs in some sick twisted disgusting joke. Thankfully it's just auto-correct being a dick :) /me runs away arms flailing about anyways! On Thu, Aug 28, 2014 at 5:12 AM, ro...@cywee.com ro...@cywee.com wrote: Kirks, thanks a lot. By the wa y, I use OCFS2/iSCSI as the clumster filesystem under Shared Mountpoint mode. I have a problem right now. There are two hosts running ocfs2 and connecting to a signle storage server with iSCSI. After I run about one day, one hosts hung up and all the VM on this host stopped. I suspected ocfs2 filesystem locked the host. I want to see the lock status of ocfs2. How to do? ro...@cywee.com From: Kirk Kosinski Date: 2014-08-28 16:54 To: users Subject: Re: About sharepoint mode in CloudStack Hi, Robin. The NFS option should be used for NFS shares that are not already mounted on the hosts. CloudStack will tell the hosts to mount the NFS share you specify. The Shared Mount Point option would be for a primary storage that is already mounted on the hosts by the system administrator. Here is what the docs [1] say about it: KVM supports Shared Mountpoint storage. A shared mountpoint is a file system path local to each server in a given cluster. The path must be the same across all Hosts in the cluster, for example /mnt/primary1. This shared mountpoint is assumed to be a clustered filesystem such as OCFS2. In this case the CloudStack does not attempt to mount or unmount the storage as is done with NFS. The CloudStack requires that the administrator insure that the storage is available. Best regards, Kirk [1] http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.2.0/html/A dmin_Guide/primary-storage.html#hypervisor-support-for-primarystorage On 08/27/2014 11:33 PM, ro...@cywee.com wrote: Hi, Can anyone help explain the difference of primary storage modes-- sharepoint and NFS? thanks, ro...@cywee.com 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 SA Pty Ltd is a company registered by The Republic of South Africa and is traded under license from Shape Blue Ltd. ShapeBlue is a registered trademark.
Re: http://cloudstack.org/dl/cloud-set-guest-password not working
Tnx what about windows password change app? On 29 Aug 2014, at 13:08, Ian Duffy i...@ianduffy.ie wrote: Hi France, One of the shapeblue guys has them uploaded to github: https://github.com/shankerbalan/cloudstack-scripts Hope this helps, ian On 29 August 2014 10:11, France mailingli...@isg.si wrote: We are still at 4.1.1 CS. Using the documentation for 4.1.1. gives the link for password set script to: http://cloudstack.org/dl/cloud-set-guest-password This is no longer valid. Where could i get the password script nowdays from? Tnx. F.
Re: Management Server won't connect after cluster shutdown and restart
Hi carlos, Did you ever find a fix for this? I'm seeing a same issue on 4.1.1 with Vmware ESXi. On 29 October 2013 04:54, Carlos Reategui create...@gmail.com wrote: Update. I cleared out the async_job table and also reset the system vms it thought where in starting mode from my previous attempts by setting them to Stopped from starting. I also re-set the XS pool master to be the one XS thinks it is. Now when I start the CS MS here are the logs leading up to the first exception about the Unable to reach the pool: 2013-10-28 21:27:11,040 DEBUG [cloud.alert.ClusterAlertAdapter] (Cluster-Notification-1:null) Management server node 172.30.45.2 is up, send alert 2013-10-28 21:27:11,045 WARN [cloud.cluster.ClusterManagerImpl] (Cluster-Notification-1:null) Notifying management server join event took 9 ms 2013-10-28 21:27:23,236 DEBUG [cloud.server.StatsCollector] (StatsCollector-2:null) HostStatsCollector is running... 2013-10-28 21:27:23,243 DEBUG [cloud.server.StatsCollector] (StatsCollector-3:null) VmStatsCollector is running... 2013-10-28 21:27:23,247 DEBUG [cloud.server.StatsCollector] (StatsCollector-1:null) StorageCollector is running... 2013-10-28 21:27:23,255 DEBUG [cloud.server.StatsCollector] (StatsCollector-1:null) There is no secondary storage VM for secondary storage host nfs://172.30.45.2/store/secondary 2013-10-28 21:27:23,273 DEBUG [agent.manager.ClusteredAgentAttache] (StatsCollector-2:null) Seq 1-201916421: Forwarding null to 233845174730255 2013-10-28 21:27:23,274 DEBUG [agent.manager.ClusteredAgentAttache] (AgentManager-Handler-9:null) Seq 1-201916421: Routing from 233845174730253 2013-10-28 21:27:23,275 DEBUG [agent.manager.ClusteredAgentAttache] (AgentManager-Handler-9:null) Seq 1-201916421: Link is closed 2013-10-28 21:27:23,275 DEBUG [agent.manager.ClusteredAgentManagerImpl] (AgentManager-Handler-9:null) Seq 1-201916421: MgmtId 233845174730253: Req: Resource [Host:1] is unreachable: Host 1: Link is c losed 2013-10-28 21:27:23,275 DEBUG [agent.manager.ClusteredAgentManagerImpl] (AgentManager-Handler-9:null) Seq 1--1: MgmtId 233845174730253: Req: Routing to peer 2013-10-28 21:27:23,277 DEBUG [agent.manager.ClusteredAgentManagerImpl] (AgentManager-Handler-11:null) Seq 1--1: MgmtId 233845174730253: Req: Cancel request received 2013-10-28 21:27:23,277 DEBUG [agent.manager.AgentAttache] (AgentManager-Handler-11:null) Seq 1-201916421: Cancelling. 2013-10-28 21:27:23,277 DEBUG [agent.manager.AgentAttache] (StatsCollector-2:null) Seq 1-201916421: Waiting some more time because this is the current command 2013-10-28 21:27:23,277 DEBUG [agent.manager.AgentAttache] (StatsCollector-2:null) Seq 1-201916421: Waiting some more time because this is the current command 2013-10-28 21:27:23,277 INFO [utils.exception.CSExceptionErrorCode] (StatsCollector-2:null) Could not find exception: com.cloud.exception.OperationTimedoutException in error code list for exceptions 2013-10-28 21:27:23,277 WARN [agent.manager.AgentAttache] (StatsCollector-2:null) Seq 1-201916421: Timed out on null 2013-10-28 21:27:23,278 DEBUG [agent.manager.AgentAttache] (StatsCollector-2:null) Seq 1-201916421: Cancelling. 2013-10-28 21:27:23,278 WARN [agent.manager.AgentManagerImpl] (StatsCollector-2:null) Operation timed out: Commands 201916421 to Host 1 timed out after 3600 2013-10-28 21:27:23,278 WARN [cloud.resource.ResourceManagerImpl] (StatsCollector-2:null) Unable to obtain host 1 statistics. 2013-10-28 21:27:23,278 WARN [cloud.server.StatsCollector] (StatsCollector-2:null) Received invalid host stats for host: 1 2013-10-28 21:27:23,281 DEBUG [agent.manager.ClusteredAgentAttache] (StatsCollector-1:null) Seq 1-201916422: Forwarding null to 233845174730255 2013-10-28 21:27:23,283 DEBUG [agent.manager.ClusteredAgentAttache] (AgentManager-Handler-12:null) Seq 1-201916422: Routing from 233845174730253 2013-10-28 21:27:23,283 DEBUG [agent.manager.ClusteredAgentAttache] (AgentManager-Handler-12:null) Seq 1-201916422: Link is closed 2013-10-28 21:27:23,283 DEBUG [agent.manager.ClusteredAgentManagerImpl] (AgentManager-Handler-12:null) Seq 1-201916422: MgmtId 233845174730253: Req: Resource [Host:1] is unreachable: Host 1: Link is closed 2013-10-28 21:27:23,284 DEBUG [agent.manager.ClusteredAgentManagerImpl] (AgentManager-Handler-12:null) Seq 1--1: MgmtId 233845174730253: Req: Routing to peer 2013-10-28 21:27:23,286 DEBUG [agent.manager.ClusteredAgentManagerImpl] (AgentManager-Handler-13:null) Seq 1--1: MgmtId 233845174730253: Req: Cancel request received 2013-10-28 21:27:23,286 DEBUG [agent.manager.AgentAttache] (AgentManager-Handler-13:null) Seq 1-201916422: Cancelling. 2013-10-28 21:27:23,286 DEBUG [agent.manager.AgentAttache] (StatsCollector-1:null) Seq 1-201916422: Waiting some more time because this is the current command 2013-10-28 21:27:23,286 DEBUG [agent.manager.AgentAttache] (StatsCollector-1:null) Seq
Re: http://cloudstack.org/dl/cloud-set-guest-password not working
Haven't used this before this might be of interest: http://www.cloudbase.it/cloud-init-for-windows-instances/ On 29 August 2014 14:09, France mailingli...@isg.si wrote: Tnx what about windows password change app? On 29 Aug 2014, at 13:08, Ian Duffy i...@ianduffy.ie wrote: Hi France, One of the shapeblue guys has them uploaded to github: https://github.com/shankerbalan/cloudstack-scripts Hope this helps, ian On 29 August 2014 10:11, France mailingli...@isg.si wrote: We are still at 4.1.1 CS. Using the documentation for 4.1.1. gives the link for password set script to: http://cloudstack.org/dl/cloud-set-guest-password This is no longer valid. Where could i get the password script nowdays from? Tnx. F.
Re: Management Server won't connect after cluster shutdown and restart
Hi Ian, So the root of the problem was that the machines where not started up in the correct order. My plan had been to stop all VMs from CS, then stop CS, then shutdown the VM hosts. On the other end the hosts needed to be brought up first and once they are ok then bring up the CS machine and make sure everything was in the same state it thought things were when it was shutdown. Unfortunately CS came up before everything else was the way it expected it to be and I did not realize that at the time. To resolve I went back to my CS db backup from right after I shut it down the MS, made sure the VM hosts were all as expected and then started the MS. On Fri, Aug 29, 2014 at 8:02 AM, Ian Duffy i...@ianduffy.ie wrote: Hi carlos, Did you ever find a fix for this? I'm seeing a same issue on 4.1.1 with Vmware ESXi. On 29 October 2013 04:54, Carlos Reategui create...@gmail.com wrote: Update. I cleared out the async_job table and also reset the system vms it thought where in starting mode from my previous attempts by setting them to Stopped from starting. I also re-set the XS pool master to be the one XS thinks it is. Now when I start the CS MS here are the logs leading up to the first exception about the Unable to reach the pool: 2013-10-28 21:27:11,040 DEBUG [cloud.alert.ClusterAlertAdapter] (Cluster-Notification-1:null) Management server node 172.30.45.2 is up, send alert 2013-10-28 21:27:11,045 WARN [cloud.cluster.ClusterManagerImpl] (Cluster-Notification-1:null) Notifying management server join event took 9 ms 2013-10-28 21:27:23,236 DEBUG [cloud.server.StatsCollector] (StatsCollector-2:null) HostStatsCollector is running... 2013-10-28 21:27:23,243 DEBUG [cloud.server.StatsCollector] (StatsCollector-3:null) VmStatsCollector is running... 2013-10-28 21:27:23,247 DEBUG [cloud.server.StatsCollector] (StatsCollector-1:null) StorageCollector is running... 2013-10-28 21:27:23,255 DEBUG [cloud.server.StatsCollector] (StatsCollector-1:null) There is no secondary storage VM for secondary storage host nfs://172.30.45.2/store/secondary 2013-10-28 21:27:23,273 DEBUG [agent.manager.ClusteredAgentAttache] (StatsCollector-2:null) Seq 1-201916421: Forwarding null to 233845174730255 2013-10-28 21:27:23,274 DEBUG [agent.manager.ClusteredAgentAttache] (AgentManager-Handler-9:null) Seq 1-201916421: Routing from 233845174730253 2013-10-28 21:27:23,275 DEBUG [agent.manager.ClusteredAgentAttache] (AgentManager-Handler-9:null) Seq 1-201916421: Link is closed 2013-10-28 21:27:23,275 DEBUG [agent.manager.ClusteredAgentManagerImpl] (AgentManager-Handler-9:null) Seq 1-201916421: MgmtId 233845174730253: Req: Resource [Host:1] is unreachable: Host 1: Link is c losed 2013-10-28 21:27:23,275 DEBUG [agent.manager.ClusteredAgentManagerImpl] (AgentManager-Handler-9:null) Seq 1--1: MgmtId 233845174730253: Req: Routing to peer 2013-10-28 21:27:23,277 DEBUG [agent.manager.ClusteredAgentManagerImpl] (AgentManager-Handler-11:null) Seq 1--1: MgmtId 233845174730253: Req: Cancel request received 2013-10-28 21:27:23,277 DEBUG [agent.manager.AgentAttache] (AgentManager-Handler-11:null) Seq 1-201916421: Cancelling. 2013-10-28 21:27:23,277 DEBUG [agent.manager.AgentAttache] (StatsCollector-2:null) Seq 1-201916421: Waiting some more time because this is the current command 2013-10-28 21:27:23,277 DEBUG [agent.manager.AgentAttache] (StatsCollector-2:null) Seq 1-201916421: Waiting some more time because this is the current command 2013-10-28 21:27:23,277 INFO [utils.exception.CSExceptionErrorCode] (StatsCollector-2:null) Could not find exception: com.cloud.exception.OperationTimedoutException in error code list for exceptions 2013-10-28 21:27:23,277 WARN [agent.manager.AgentAttache] (StatsCollector-2:null) Seq 1-201916421: Timed out on null 2013-10-28 21:27:23,278 DEBUG [agent.manager.AgentAttache] (StatsCollector-2:null) Seq 1-201916421: Cancelling. 2013-10-28 21:27:23,278 WARN [agent.manager.AgentManagerImpl] (StatsCollector-2:null) Operation timed out: Commands 201916421 to Host 1 timed out after 3600 2013-10-28 21:27:23,278 WARN [cloud.resource.ResourceManagerImpl] (StatsCollector-2:null) Unable to obtain host 1 statistics. 2013-10-28 21:27:23,278 WARN [cloud.server.StatsCollector] (StatsCollector-2:null) Received invalid host stats for host: 1 2013-10-28 21:27:23,281 DEBUG [agent.manager.ClusteredAgentAttache] (StatsCollector-1:null) Seq 1-201916422: Forwarding null to 233845174730255 2013-10-28 21:27:23,283 DEBUG [agent.manager.ClusteredAgentAttache] (AgentManager-Handler-12:null) Seq 1-201916422: Routing from 233845174730253 2013-10-28 21:27:23,283 DEBUG [agent.manager.ClusteredAgentAttache] (AgentManager-Handler-12:null) Seq 1-201916422: Link is closed 2013-10-28 21:27:23,283 DEBUG [agent.manager.ClusteredAgentManagerImpl]
RE: Management Server won't connect after cluster shutdown and restart
I posted an email yesterday stating how I shutdown\restart my CS instances. Works 100% Date: Fri, 29 Aug 2014 12:54:38 -0700 Subject: Re: Management Server won't connect after cluster shutdown and restart From: car...@reategui.com To: users@cloudstack.apache.org Hi Ian, So the root of the problem was that the machines where not started up in the correct order. My plan had been to stop all VMs from CS, then stop CS, then shutdown the VM hosts. On the other end the hosts needed to be brought up first and once they are ok then bring up the CS machine and make sure everything was in the same state it thought things were when it was shutdown. Unfortunately CS came up before everything else was the way it expected it to be and I did not realize that at the time. To resolve I went back to my CS db backup from right after I shut it down the MS, made sure the VM hosts were all as expected and then started the MS. On Fri, Aug 29, 2014 at 8:02 AM, Ian Duffy i...@ianduffy.ie wrote: Hi carlos, Did you ever find a fix for this? I'm seeing a same issue on 4.1.1 with Vmware ESXi. On 29 October 2013 04:54, Carlos Reategui create...@gmail.com wrote: Update. I cleared out the async_job table and also reset the system vms it thought where in starting mode from my previous attempts by setting them to Stopped from starting. I also re-set the XS pool master to be the one XS thinks it is. Now when I start the CS MS here are the logs leading up to the first exception about the Unable to reach the pool: 2013-10-28 21:27:11,040 DEBUG [cloud.alert.ClusterAlertAdapter] (Cluster-Notification-1:null) Management server node 172.30.45.2 is up, send alert 2013-10-28 21:27:11,045 WARN [cloud.cluster.ClusterManagerImpl] (Cluster-Notification-1:null) Notifying management server join event took 9 ms 2013-10-28 21:27:23,236 DEBUG [cloud.server.StatsCollector] (StatsCollector-2:null) HostStatsCollector is running... 2013-10-28 21:27:23,243 DEBUG [cloud.server.StatsCollector] (StatsCollector-3:null) VmStatsCollector is running... 2013-10-28 21:27:23,247 DEBUG [cloud.server.StatsCollector] (StatsCollector-1:null) StorageCollector is running... 2013-10-28 21:27:23,255 DEBUG [cloud.server.StatsCollector] (StatsCollector-1:null) There is no secondary storage VM for secondary storage host nfs://172.30.45.2/store/secondary 2013-10-28 21:27:23,273 DEBUG [agent.manager.ClusteredAgentAttache] (StatsCollector-2:null) Seq 1-201916421: Forwarding null to 233845174730255 2013-10-28 21:27:23,274 DEBUG [agent.manager.ClusteredAgentAttache] (AgentManager-Handler-9:null) Seq 1-201916421: Routing from 233845174730253 2013-10-28 21:27:23,275 DEBUG [agent.manager.ClusteredAgentAttache] (AgentManager-Handler-9:null) Seq 1-201916421: Link is closed 2013-10-28 21:27:23,275 DEBUG [agent.manager.ClusteredAgentManagerImpl] (AgentManager-Handler-9:null) Seq 1-201916421: MgmtId 233845174730253: Req: Resource [Host:1] is unreachable: Host 1: Link is c losed 2013-10-28 21:27:23,275 DEBUG [agent.manager.ClusteredAgentManagerImpl] (AgentManager-Handler-9:null) Seq 1--1: MgmtId 233845174730253: Req: Routing to peer 2013-10-28 21:27:23,277 DEBUG [agent.manager.ClusteredAgentManagerImpl] (AgentManager-Handler-11:null) Seq 1--1: MgmtId 233845174730253: Req: Cancel request received 2013-10-28 21:27:23,277 DEBUG [agent.manager.AgentAttache] (AgentManager-Handler-11:null) Seq 1-201916421: Cancelling. 2013-10-28 21:27:23,277 DEBUG [agent.manager.AgentAttache] (StatsCollector-2:null) Seq 1-201916421: Waiting some more time because this is the current command 2013-10-28 21:27:23,277 DEBUG [agent.manager.AgentAttache] (StatsCollector-2:null) Seq 1-201916421: Waiting some more time because this is the current command 2013-10-28 21:27:23,277 INFO [utils.exception.CSExceptionErrorCode] (StatsCollector-2:null) Could not find exception: com.cloud.exception.OperationTimedoutException in error code list for exceptions 2013-10-28 21:27:23,277 WARN [agent.manager.AgentAttache] (StatsCollector-2:null) Seq 1-201916421: Timed out on null 2013-10-28 21:27:23,278 DEBUG [agent.manager.AgentAttache] (StatsCollector-2:null) Seq 1-201916421: Cancelling. 2013-10-28 21:27:23,278 WARN [agent.manager.AgentManagerImpl] (StatsCollector-2:null) Operation timed out: Commands 201916421 to Host 1 timed out after 3600 2013-10-28 21:27:23,278 WARN [cloud.resource.ResourceManagerImpl] (StatsCollector-2:null) Unable to obtain host 1 statistics. 2013-10-28 21:27:23,278 WARN [cloud.server.StatsCollector] (StatsCollector-2:null) Received invalid host stats for host: 1 2013-10-28 21:27:23,281 DEBUG [agent.manager.ClusteredAgentAttache] (StatsCollector-1:null) Seq 1-201916422: Forwarding
RE: Management Server won't connect after cluster shutdown and restart
Hi Ian, I've seen this kind of behaviour before with KVM hosts reconnecting. There’s a select …. WITH UPDATE; query on the op_ha_work table which locks the table, stopping other hosts updating their status. If there are a lot of entries in there they all lock each other out. Deleting the entries fixed the problem, but you have to deal with hosts and vms being up/down yourself. So check the op_ha_work table for lots of entries which can lock up the database. If you can check the database for the queries that it's handling - that would be best. Also check that the management server and MySQL DB is tuned for the load that being thrown at it. (http://support.citrix.com/article/CTX132020) Remember if you have other services such as Nagios or puppet/chef directly reading the DB, that adds to the number of connections into the mysql db - I have seen the management server starved of mysql connections when a lot of hosts are brought back online. Regards Paul Angus Cloud Architect S: +44 20 3603 0540 | M: +447711418784 | T: CloudyAngus paul.an...@shapeblue.com -Original Message- From: create...@gmail.com [mailto:create...@gmail.com] On Behalf Of Carlos Reategui Sent: 29 August 2014 20:55 To: users@cloudstack.apache.org Subject: Re: Management Server won't connect after cluster shutdown and restart Hi Ian, So the root of the problem was that the machines where not started up in the correct order. My plan had been to stop all VMs from CS, then stop CS, then shutdown the VM hosts. On the other end the hosts needed to be brought up first and once they are ok then bring up the CS machine and make sure everything was in the same state it thought things were when it was shutdown. Unfortunately CS came up before everything else was the way it expected it to be and I did not realize that at the time. To resolve I went back to my CS db backup from right after I shut it down the MS, made sure the VM hosts were all as expected and then started the MS. On Fri, Aug 29, 2014 at 8:02 AM, Ian Duffy i...@ianduffy.ie wrote: Hi carlos, Did you ever find a fix for this? I'm seeing a same issue on 4.1.1 with Vmware ESXi. On 29 October 2013 04:54, Carlos Reategui create...@gmail.com wrote: Update. I cleared out the async_job table and also reset the system vms it thought where in starting mode from my previous attempts by setting them to Stopped from starting. I also re-set the XS pool master to be the one XS thinks it is. Now when I start the CS MS here are the logs leading up to the first exception about the Unable to reach the pool: 2013-10-28 21:27:11,040 DEBUG [cloud.alert.ClusterAlertAdapter] (Cluster-Notification-1:null) Management server node 172.30.45.2 is up, send alert 2013-10-28 21:27:11,045 WARN [cloud.cluster.ClusterManagerImpl] (Cluster-Notification-1:null) Notifying management server join event took 9 ms 2013-10-28 21:27:23,236 DEBUG [cloud.server.StatsCollector] (StatsCollector-2:null) HostStatsCollector is running... 2013-10-28 21:27:23,243 DEBUG [cloud.server.StatsCollector] (StatsCollector-3:null) VmStatsCollector is running... 2013-10-28 21:27:23,247 DEBUG [cloud.server.StatsCollector] (StatsCollector-1:null) StorageCollector is running... 2013-10-28 21:27:23,255 DEBUG [cloud.server.StatsCollector] (StatsCollector-1:null) There is no secondary storage VM for secondary storage host nfs://172.30.45.2/store/secondary 2013-10-28 21:27:23,273 DEBUG [agent.manager.ClusteredAgentAttache] (StatsCollector-2:null) Seq 1-201916421: Forwarding null to 233845174730255 2013-10-28 21:27:23,274 DEBUG [agent.manager.ClusteredAgentAttache] (AgentManager-Handler-9:null) Seq 1-201916421: Routing from 233845174730253 2013-10-28 21:27:23,275 DEBUG [agent.manager.ClusteredAgentAttache] (AgentManager-Handler-9:null) Seq 1-201916421: Link is closed 2013-10-28 21:27:23,275 DEBUG [agent.manager.ClusteredAgentManagerImpl] (AgentManager-Handler-9:null) Seq 1-201916421: MgmtId 233845174730253: Req: Resource [Host:1] is unreachable: Host 1: Link is c losed 2013-10-28 21:27:23,275 DEBUG [agent.manager.ClusteredAgentManagerImpl] (AgentManager-Handler-9:null) Seq 1--1: MgmtId 233845174730253: Req: Routing to peer 2013-10-28 21:27:23,277 DEBUG [agent.manager.ClusteredAgentManagerImpl] (AgentManager-Handler-11:null) Seq 1--1: MgmtId 233845174730253: Req: Cancel request received 2013-10-28 21:27:23,277 DEBUG [agent.manager.AgentAttache] (AgentManager-Handler-11:null) Seq 1-201916421: Cancelling. 2013-10-28 21:27:23,277 DEBUG [agent.manager.AgentAttache] (StatsCollector-2:null) Seq 1-201916421: Waiting some more time because this is the current command 2013-10-28 21:27:23,277 DEBUG [agent.manager.AgentAttache] (StatsCollector-2:null) Seq 1-201916421: Waiting some more time because this is the current command 2013-10-28 21:27:23,277 INFO
