????????5G????????
5G??10Gui5G5G??removed??null??
2014-02-24 00:00:34,477 DEBUG [agent.transport.Request]
(AgentManager-Handler-8:null) Seq 21-445986440: Processing: { Ans: , MgmtId:
203178702697288, via: 21, Ver: v1, Flags: 10,
[{com.cloud.agent.api.storage.DownloadAnswer:{jobId:43780278-fc1d-4a48-8955-208dcb3d306c,downloadPct:0,errorString:
,downloadStatus:NOT_DOWNLOADED,downloadPath:/mnt/SecStorage/7424873f-e269-3fa8-9450-4f5b3879c218/template/tmpl/2/321/dnld2165836156843133954tmp_,installPath:template/tmpl/2/321,templateSize:0,templatePhySicalSize:0,result:true,details:
,wait:0}}] }
2014-02-24 00:00:35,060 DEBUG [agent.manager.AgentManagerImpl]
(AgentManager-Handler-9:null) SeqA 18-29060: Processing Seq 18-29060: { Cmd ,
MgmtId: -1, via: 18, Ver: v1, Flags: 11,
[{com.cloud.agent.api.ConsoleProxyLoadReportCommand:{_proxyVmId:222,_loadInfo:{\n
\connections\: []\n},wait:0}}] }
@
2014-02-24 10:18:35,076 DEBUG [agent.manager.AgentManagerImpl]
(AgentManager-Handler-5:null) SeqA 18-34074: Sending Seq 18-34074: { Ans: ,
MgmtId: 203178702697288, via: 18, Ver: v1, Flags: 100010,
[{com.cloud.agent.api.AgentControlAnswer:{result:true,wait:0}}] }
2014-02-24 10:18:39,934 DEBUG [storage.download.DownloadListener]
(Timer-10:null) timeout: transitioning to download error state,
currstate=DOWNLOAD_IN_PROGRESS, TEMPLATE: 328 at host 21
2014-02-24 10:18:39,934 DEBUG [storage.image.BaseImageStoreDriverImpl]
(Timer-10:null) Performing image store createTemplate async callback
2014-02-24 10:18:39,942 WARN [storage.download.DownloadListener]
(Timer-10:null) Entering download error state: timeout waiting for response
from storage host, TEMPLATE: 328 at host 21
2014-02-24 10:18:43,542 DEBUG [cloud.server.StatsCollector]
(StatsCollector-1:null) VmStatsCollector is running...
2014-02-24 10:22:35,895 DEBUG [cloudstack.storage.RemoteHostEndPoint]
(Timer-10:null) Sending command
org.apache.cloudstack.storage.command.DownloadProgressCommand to host: 21
2014-02-24 10:22:35,896 DEBUG [agent.transport.Request] (Timer-10:null) Seq
21-1681588331: Sending { Cmd , MgmtId: 203178702697288, via: 21, Ver: v1,
Flags: 100011,
[{org.apache.cloudstack.storage.command.DownloadProgressCommand:{jobId:729b418f-c826-490d-8bbb-c31c43eea900,request:PURGE,hvm:true,description:70.123,maxDownloadSizeInBytes:53687091200,id:328,resourceType:TEMPLATE,installPath:template/tmpl/2/328,_store:{com.cloud.agent.api.to.NfsTO:{_url:nfs://172.16.106.231/cloud-nfs-temp,_role:Image}},url:http://192.168.150.5/70.123.qcow2,format:QCOW2,accountId:2,name:328-2-5158d452-bf60-3161-9421-4f088e9d0391,secUrl:nfs://172.16.106.231/cloud-nfs-temp,wait:0}}]
}
2014-02-24 10:22:35,937 DEBUG [agent.transport.Request]
(AgentManager-Handler-14:null) Seq 21-1681588331: Processing: { Ans: , MgmtId:
203178702697288, via: 21, Ver: v1, Flags: 10,
[{com.cloud.agent.api.storage.DownloadAnswer:{jobId:729b418f-c826-490d-8bbb-c31c43eea900,downloadPct:100,errorString:Install
completed successfully at 2/24/14 2:22
AM,downloadStatus:DOWNLOADED,downloadPath:/mnt/SecStorage/7424873f-e269-3fa8-9450-4f5b3879c218/template/tmpl/2/328/dnld3971000183567759621tmp_,installPath:template/tmpl/2/328/07289b74-d443-3708-a95d-72832e0e1ad5.qcow2,templateSize:21474836480,templatePhySicalSize:11856510976,checkSum:837256903c623369055e47211e8de6a1,result:true,details:Install
completed successfully at 2/24/14 2:22 AM,wait:0}}] }
Segfault: Top Sampling Rates (kvm.resource.LibvirtComputingResource)
Hi, I have just noticed the occasional following error messages in kern.log. This is happening on all but 1 of my nodes. Is anyone else experiencing this issue? = Feb 23 06:53:24 aurora kernel: [10185338.400091] top[27631]: segfault at 0 ip 7f025eba3315 sp 7fff3f9ed308 error 4 in libc-2.15.so[7f025ea6f000+1b5000] = I happened to have one of the nodes in trace mode, showing cloudstack-agent is starting it: /var/log/cloudstack/agent/agent.log == 2014-02-23 06:53:23,654 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-1:null) Executing: /bin/bash -c idle=$(top -b -n 1|grep Cpu\(s\):|cut -d% -f4|cut -d, -f2);echo $idle 2014-02-23 06:53:23,661 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-2:null) Executing: /bin/bash -c idle=$(top -b -n 1|grep Cpu\(s\):|cut -d% -f4|cut -d, -f2);echo $idle == ## This lead me on to find the following (potential) bug: When running this manually I get the same result (2 secs before each command): == root@aurora:/var/log/cloudstack/agent# top -b -n1 | grep Cpu Cpu(s): 6.3%us, 1.0%sy, 0.0%ni, 92.4%id, 0.2%wa, 0.0%hi, 0.0%si, 0.0%st root@aurora:/var/log/cloudstack/agent# top -b -n1 | grep Cpu Cpu(s): 6.3%us, 1.0%sy, 0.0%ni, 92.4%id, 0.2%wa, 0.0%hi, 0.0%si, 0.0%st root@aurora:/var/log/cloudstack/agent# top -b -n1 | grep Cpu Cpu(s): 6.3%us, 1.0%sy, 0.0%ni, 92.4%id, 0.2%wa, 0.0%hi, 0.0%si, 0.0%st root@aurora:/var/log/cloudstack/agent# top -b -n2 | grep Cpu Cpu(s): 6.3%us, 1.0%sy, 0.0%ni, 92.4%id, 0.2%wa, 0.0%hi, 0.0%si, 0.0%st Cpu(s): 29.2%us, 1.1%sy, 0.0%ni, 69.1%id, 0.5%wa, 0.0%hi, 0.1%si, 0.0%st === Apparently this is because: This is because top, vmstat, iostat all in their first run collect data since the last reboot time of the system. And the successive iterations run on the sampling period that you specify. So, in the first run of top, you will see the %idle time because from the time of reboot to the time of running top, it was that much % idle. But in next iterations, since it is busy it doesn't show any %idle. Exclude the first iteration and try sampling over the interval you want. http://serverfault.com/questions/436446/top-showing-64-idle-on-first-screen-or-batch-run-while-there-is-no-idle-time-a Wouldn't this result in Cloudstack-Agent getting the wrong idle value for the system? If this hasn't been fixed in 4.3.0, I will create a patch along the following lines (if others agree): /bin/bash -c idle=$(top -d0.01 -b -n 2|grep Cpu\(s\):|tail -n1|cut -d% -f4|cut -d, -f2;echo $idle - Where top -d0.01, changes the refresh interval so the command is faster to complete. - tail -n1, get's the last line of the output (the latest idle value) Ubuntu 12.04 / KVM / CS 4.2.0 Linux aurora 3.5.0-34-generic #55~precise1-Ubuntu SMP Fri Jun 7 16:25:50 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Thanks, Marty
Network is not in the right state to be restarted. Correct states are: Implemented, Setup
Hi All, We experienced a storage failure a few days back and Cloudstack has since recovered (everything is up and running) but the Networks seem to be in a funny state. They're all in an Implementing state. And as such I cannot restart them. I only came across this because I was digging into possible reasons for a new Load Balancer not actually load balancing. Anyone seen this behaviour before in CS 4.2.1 ? Or have any thoughts on how to correct it? State: Implementing MGMT LOG SNIP: # 2014-02-23 21:03:06,407 ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-24:job-136 = [ 69637672-9ef5-4aba-9e8b-765b6451d5f4 ]) Unexpected exception while executing org.apache.cloudstack.api.command.user.network.RestartNetworkCmd com.cloud.exception.InvalidParameterValueException: Network is not in the right state to be restarted. Correct states are: Implemented, Setup at com.cloud.network.NetworkServiceImpl.restartNetwork(NetworkServiceImpl.java:1790) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at org.apache.cloudstack.api.command.user.network.RestartNetworkCmd.execute(RestartNetworkCmd.java:92) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531) 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.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:701) 2014-02-23 21:03:06,411 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-24:job-136 = [ 69637672-9ef5-4aba-9e8b-765b6451d5f4 ]) Complete async job-136 = [ 69637672-9ef5-4aba-9e8b-765b6451d5f4 ], jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text: Network is not in the right state to be restarted. Correct states are: Implemented, Setup # Regards Ronald
Re: Network is not in the right state to be restarted. Correct states are: Implemented, Setup
Ronald, I've seen this happening since version 3 of CS, so for me it is a know issue. Not sure what changes the state of Network, but it seems to change from time to time. The way I deal with it is by changing the database entry for the network to the right state and it seems to work. Andrei - Original Message - From: ronald higgins ronald.higg...@gmail.com To: users users@cloudstack.apache.org Sent: Sunday, 23 February, 2014 7:07:30 PM Subject: Network is not in the right state to be restarted. Correct states are: Implemented, Setup Hi All, We experienced a storage failure a few days back and Cloudstack has since recovered (everything is up and running) but the Networks seem to be in a funny state. They're all in an Implementing state. And as such I cannot restart them. I only came across this because I was digging into possible reasons for a new Load Balancer not actually load balancing. Anyone seen this behaviour before in CS 4.2.1 ? Or have any thoughts on how to correct it? State: Implementing MGMT LOG SNIP: # 2014-02-23 21:03:06,407 ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-24:job-136 = [ 69637672-9ef5-4aba-9e8b-765b6451d5f4 ]) Unexpected exception while executing org.apache.cloudstack.api.command.user.network.RestartNetworkCmd com.cloud.exception.InvalidParameterValueException: Network is not in the right state to be restarted. Correct states are: Implemented, Setup at com.cloud.network.NetworkServiceImpl.restartNetwork(NetworkServiceImpl.java:1790) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at org.apache.cloudstack.api.command.user.network.RestartNetworkCmd.execute(RestartNetworkCmd.java:92) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531) 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.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:701) 2014-02-23 21:03:06,411 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-24:job-136 = [ 69637672-9ef5-4aba-9e8b-765b6451d5f4 ]) Complete async job-136 = [ 69637672-9ef5-4aba-9e8b-765b6451d5f4 ], jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text: Network is not in the right state to be restarted. Correct states are: Implemented, Setup # Regards Ronald
Xen Server Setup
Hello, I am attempting to setup cloudstack on Xen Server, I have setup the traffic labels it seems all is well in that regard. The system VMs are running without issue and setup the way I would like them as follows: Public IP Addressx.x.x.x (omitted for obvious reasons)Private IP Address 10.4.234.151Link Local IP Address169.254.0.21 I would like to know what I am doing wrong, as you can see I have a Private IP address and a public facing IP address, but, no internet access is provided within. Thus resulting in the inability to download the CentOS Template (which is it possible to obtain a NEWER template when installing Cloudstack). Also, I am not seeing ingrees/regress rules to allow inbound/outbound connections; so I am a little at a loss on how to resolve this. If someone could assist me and/or direct me in the right way that would be great. - Maurice
Re: Network is not in the right state to be restarted. Correct states are: Implemented, Setup
Thanks Andrei, appreciate your feedback. I'll take a shufti in the DB to change the state and I'll open up a ticket. On Sun, Feb 23, 2014 at 9:18 PM, Andrei Mikhailovsky and...@arhont.comwrote: Ronald, I've seen this happening since version 3 of CS, so for me it is a know issue. Not sure what changes the state of Network, but it seems to change from time to time. The way I deal with it is by changing the database entry for the network to the right state and it seems to work. Andrei - Original Message - From: ronald higgins ronald.higg...@gmail.com To: users users@cloudstack.apache.org Sent: Sunday, 23 February, 2014 7:07:30 PM Subject: Network is not in the right state to be restarted. Correct states are: Implemented, Setup Hi All, We experienced a storage failure a few days back and Cloudstack has since recovered (everything is up and running) but the Networks seem to be in a funny state. They're all in an Implementing state. And as such I cannot restart them. I only came across this because I was digging into possible reasons for a new Load Balancer not actually load balancing. Anyone seen this behaviour before in CS 4.2.1 ? Or have any thoughts on how to correct it? State: Implementing MGMT LOG SNIP: # 2014-02-23 21:03:06,407 ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-24:job-136 = [ 69637672-9ef5-4aba-9e8b-765b6451d5f4 ]) Unexpected exception while executing org.apache.cloudstack.api.command.user.network.RestartNetworkCmd com.cloud.exception.InvalidParameterValueException: Network is not in the right state to be restarted. Correct states are: Implemented, Setup at com.cloud.network.NetworkServiceImpl.restartNetwork(NetworkServiceImpl.java:1790) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at org.apache.cloudstack.api.command.user.network.RestartNetworkCmd.execute(RestartNetworkCmd.java:92) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531) 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.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:701) 2014-02-23 21:03:06,411 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-24:job-136 = [ 69637672-9ef5-4aba-9e8b-765b6451d5f4 ]) Complete async job-136 = [ 69637672-9ef5-4aba-9e8b-765b6451d5f4 ], jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text: Network is not in the right state to be restarted. Correct states are: Implemented, Setup # Regards Ronald
Re: Dashboard (Xen Questions)
Could you re-attach your inline image and add me on jabber? mattisb...@authbase.com :) On Sun, Feb 23, 2014 at 2:47 PM, Mo m...@daoenix.com wrote: [image: Inline image 1] You can see it states I have 112 public IP address, that is not correct, I am only using 12 public IP addresses. Along with that, due to my previous e-mail (Xen Server Setup) it would seem as though my inability to configure it correctly. Again, if someone can assist me, I would be delighted! Thanks! Mo
SSVM Public IP not pinging
I have created basic zone, with no security group on CS 4.0.2 and hypervisor is xenserver. SSVM and CPVM is running state but I am not able to ping SSVM Public IP. it says Destination Host Unreachable . So I am not able to download CentOS template and and hence not able to create any guest vm. need help. Regards, Tejas
Re: SSVM Public IP not pinging
nope not able to ping link local of SSVM or CPVM. Regards, Tejas On Mon, Feb 24, 2014 at 11:14 AM, Ian Young iyo...@ratespecial.com wrote: What about the SSVM's link local address? Can you ping that? It should begin with 169.254. On Feb 23, 2014 9:41 PM, Tejas Gadaria refond.g...@gmail.com wrote: I have created basic zone, with no security group on CS 4.0.2 and hypervisor is xenserver. SSVM and CPVM is running state but I am not able to ping SSVM Public IP. it says Destination Host Unreachable . So I am not able to download CentOS template and and hence not able to create any guest vm. need help. Regards, Tejas
Re: SSVM Public IP not pinging
This should help you debug : https://cwiki.apache.org/confluence/display/CLOUDSTACK/SSVM,+templates,+Sec ondary+storage+troubleshooting On 2/23/14 9:44 PM, Ian Young iyo...@ratespecial.com wrote: What about the SSVM's link local address? Can you ping that? It should begin with 169.254. On Feb 23, 2014 9:41 PM, Tejas Gadaria refond.g...@gmail.com wrote: I have created basic zone, with no security group on CS 4.0.2 and hypervisor is xenserver. SSVM and CPVM is running state but I am not able to ping SSVM Public IP. it says Destination Host Unreachable . So I am not able to download CentOS template and and hence not able to create any guest vm. need help. Regards, Tejas
