Re: 服务启动不成功
系统里是不是有keytool这个命令没有安装吧？你装一下试试。 2014-03-26 17:14 GMT+08:00 史丽丽 shi...@neusoft.com: 您好，我这边做一个cloudstack的部署，目前是在一台虚拟机上装cloudstack，数据库安装成功，操作系统是rhel cs版本为4.2，到初始化cloudstack管理程序步骤，执行如下命令cloudstack-setup-management 参看日志为：/var/log/cloudstack/management/catalina.out cs启动报错如下：服务启动不成功，望您给予解答，谢谢。 maxElementsOnDisk = 0 memoryStoreEvictionPolicy = LRU timeToLiveSeconds = 600 timeToIdleSeconds = 300 diskPersistent = false diskExpiryThreadIntervalSeconds = 120 cacheEventListeners: hitCount = 0 memoryStoreHitCount = 0 diskStoreHitCount = 0 missCountNotFound = 0 missCountExpired = 0 ] INFO [utils.component.ComponentContext] (Timer-2:) Configuring com.cloud.upgrade.DatabaseIntegrityChecker_EnhancerByCloudStack_ead01e13 INFO [utils.component.ComponentContext] (Timer-2:) Configuring com.cloud.server.ConfigurationServerImpl_EnhancerByCloudStack_a685eed4 INFO [cloud.server.ConfigurationServerImpl] (Timer-2:) Processing updateSSLKeyStore INFO [cloud.server.ConfigurationServerImpl] (Timer-2:) SSL keystore located at /etc/cloudstack/management/cloud.keystore WARN [cloud.server.ConfigurationServerImpl] (Timer-2:) Would use fail-safe keystore to continue. java.io.IOException: Fail to generate certificate!: sudo: keytool: command not found at com.cloud.server.ConfigurationServerImpl.generateDefaultKeystore(ConfigurationServerImpl.java:496) at com.cloud.server.ConfigurationServerImpl.updateSSLKeystore(ConfigurationServerImpl.java:517) at com.cloud.server.ConfigurationServerImpl.persistDefaultValues(ConfigurationServerImpl.java:289) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at com.cloud.server.ConfigurationServerImpl.configure(ConfigurationServerImpl.java:157) at com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:111) at com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:54) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) INFO [cloud.server.ConfigurationServerImpl] (Timer-2:) Processing updateKeyPairs INFO [cloud.server.ConfigurationServerImpl] (Timer-2:) Keypairs already in database, updating local copy INFO [cloud.server.ConfigurationServerImpl] (Timer-2:) Going to update systemvm iso with generated keypairs if needed 2014-3-26 13:57:40 org.springframework.web.context.ContextLoader initWebApplicationContext 信息: Root WebApplicationContext: initialization completed in 3871 ms 2014-3-26 13:57:40 org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor init 信息: JSR-330 'javax.inject.Inject' annotation found and supported for autowiring INFO [utils.component.ComponentContext] (Timer-2:) Configuring com.cloud.utils.crypt.EncryptionSecretKeyChecker_EnhancerByCloudStack_375384cc INFO [utils.component.ComponentContext] (Timer-2:) Configuring com.cloud.cluster.ManagementServerNode_EnhancerByCloudStack_ab03d7d2 INFO [utils.component.ComponentContext] (Timer-2:) Configuring com.cloud.cluster.ClusterManagerImpl_EnhancerByCloudStack_5702e15 INFO [cloud.cluster.ClusterManagerImpl] (Timer-2:) Start configuring cluster manager : ClusterManagerImpl_EnhancerByCloudStack_5702e15 INFO [cloud.cluster.ClusterManagerImpl] (Timer-2:) Cluster node IP : 192.168.131.141 INFO [utils.db.Merovingian2] (Timer-2:) Cleaning up locks for 86530476470110 INFO [utils.db.Merovingian2] (Timer-2:) Released 0 locks for 86530476470110 INFO [cloud.cluster.ClusterManagerImpl] (Timer-2:) register cluster listener class com.cloud.cluster.LockMasterListener INFO [cloud.cluster.ClusterManagerImpl] (Timer-2:) Trying to connect to 192.168.131.141 ERROR [cloud.cluster.ClusterManagerImpl] (Timer-2:) Unable to ping management server at 192.168.131.141:9090 due to ConnectException java.net.ConnectException: Connection refused at sun.nio.ch.Net.connect(Native Method) at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:500) at com.cloud.cluster.ClusterManagerImpl.pingManagementNode(ClusterManagerImpl.java:1405) at com.cloud.cluster.ClusterManagerImpl.pingManagementNode(ClusterManagerImpl.java:1384) at com.cloud.cluster.ClusterManagerImpl.checkConflicts(ClusterManagerImpl.java:1461) at com.cloud.cluster.ClusterManagerImpl.configure(ClusterManagerImpl.java:1347) at com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:111) at com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:54) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) INFO [cloud.cluster.ClusterManagerImpl] (Timer-2:) Detected that another management node with the same IP 192.168.131.141 is considered as running in DB, however it is not pingable, we will continue cluster initialization with this management server node INFO [cloud.cluster.ClusterManagerImpl] (Timer-2:) Cluster
v4.2.1 启动报错
各位好。 安装的4.2.1一直都没有启动成功过，请各位高手帮忙，非常感谢。 环境如下： management-server: 运行在vmware workstation的虚拟中，网络桥接模式。 配置： CPU:：Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz 两个 内存：2GB -- Best Regards
[求助] v4.2.1 启动报错
各位好。 不好意思，刚才Gmail的快捷键误发了和一个没有写完的邮件，请管理员删除。 安装的4.2.1一直都没有启动成功过，请各位高手帮忙，非常感谢。 环境如下： management-server: 运行在vmware workstation的虚拟机中，网络桥接模式。 物理宿主机为windows7，IP：192.168.11.30 配置： CPU:：Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz 两个 内存：2GB 磁盘：80GB IP： 192.168.11.61 GW: 192.168.11.1 Host： 运行在另一台物理主机，XenServer6.1.0 配置： CPU:：Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz 内存：8GB 磁盘：2TB IP： 192.168.11.40 GW: 192.168.11.1 一级存储和二级存储使用NFS模式，NFS服务端：management-server（192.168.11.61） 中： primary: /export/primary secondary: /export/secondary 在Host中挂载NFS读写都没有问题 management-server iptables: [root@cs-manager management]# cat /etc/sysconfig/iptables # Generated by iptables-save v1.4.7 on Mon Mar 17 06:02:02 2014 *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [999012:2307279867] -A INPUT -p tcp -m tcp --dport 9090 -j ACCEPT -A INPUT -p tcp -m tcp --dport 8250 -j ACCEPT -A INPUT -p tcp -m tcp --dport 7080 -j ACCEPT -A INPUT -p tcp -m tcp --dport 8080 -j ACCEPT -A INPUT -p tcp -m tcp --dport 111 -j ACCEPT -A INPUT -p udp -m udp --dport 111 -j ACCEPT -A INPUT -p tcp -m tcp --dport 2049 -j ACCEPT -A INPUT -p tcp -m tcp --dport 32803 -j ACCEPT -A INPUT -p udp -m udp --dport 32769 -j ACCEPT -A INPUT -p tcp -m tcp --dport 892 -j ACCEPT -A INPUT -p udp -m udp --dport 892 -j ACCEPT -A INPUT -p tcp -m tcp --dport 875 -j ACCEPT -A INPUT -p udp -m udp --dport 875 -j ACCEPT -A INPUT -p tcp -m tcp --dport 662 -j ACCEPT -A INPUT -p udp -m udp --dport 662 -j ACCEPT -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT -A INPUT -p icmp -j ACCEPT -A INPUT -i lo -j ACCEPT -A INPUT -p tcp -m state --state NEW -m tcp --dport 22 -j ACCEPT -A INPUT -j REJECT --reject-with icmp-host-prohibited -A FORWARD -j REJECT --reject-with icmp-host-prohibited COMMIT # Completed on Mon Mar 17 06:02:02 2014 完整日志文件请见：http://hctysoft.com/management-server.log 从日志中分析来看在启动Console Proxy VM的报错，下面是我截取的一些关键的management-server日志片段： catalina.out: INFO [cloud.cluster.ClusterManagerImpl] (Timer-2:) register cluster listener class com.cloud.cluster.LockMasterListener INFO [cloud.cluster.ClusterManagerImpl] (Timer-2:) Trying to connect to 192.168.11.61 ERROR [cloud.cluster.ClusterManagerImpl] (Timer-2:) Unable to ping management server at 192.168.11.61:9090 due to ConnectException java.net.ConnectException: Connection refused at sun.nio.ch.Net.connect0(Native Method) at sun.nio.ch.Net.connect(Net.java:465) at sun.nio.ch.Net.connect(Net.java:457) at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:670) at com.cloud.cluster.ClusterManagerImpl.pingManagementNode(ClusterManagerImpl.java:1405) at com.cloud.cluster.ClusterManagerImpl.pingManagementNode(ClusterManagerImpl.java:1384) at com.cloud.cluster.ClusterManagerImpl.checkConflicts(ClusterManagerImpl.java:1461) at com.cloud.cluster.ClusterManagerImpl.configure(ClusterManagerImpl.java:1347) at com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:111) at com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:54) at java.util.TimerThread.mainLoop(Timer.java:555) at java.util.TimerThread.run(Timer.java:505) management-server.log 2014-03-22 22:45:57,912 INFO [cloud.cluster.ClusterManagerImpl] (Timer-2:null) Cluster node IP : 192.168.11.61 2014-03-22 22:45:57,959 DEBUG [utils.db.ConnectionConcierge] (Timer-2:null) Registering a database connection for LockMaster1 2014-03-22 22:45:57,959 INFO [utils.db.Merovingian2] (Timer-2:null) Cleaning up locks for 52243566829 2014-03-22 22:45:57,960 INFO [utils.db.Merovingian2] (Timer-2:null) Released 0 locks for 52243566829 2014-03-22 22:45:57,960 INFO [cloud.cluster.ClusterManagerImpl] (Timer-2:null) register cluster listener class com.cloud.cluster.LockMasterListener 2014-03-22 22:45:57,988 INFO [cloud.cluster.ClusterManagerImpl] (Timer-2:null) Trying to connect to 192.168.11.61 2014-03-22 22:45:57,993 ERROR [cloud.cluster.ClusterManagerImpl] (Timer-2:null) Unable to ping management server at 192.168.11.61:9090 due to ConnectException java.net.ConnectException: Connection refused at sun.nio.ch.Net.connect0(Native Method) at sun.nio.ch.Net.connect(Net.java:465) at sun.nio.ch.Net.connect(Net.java:457) at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:670) at com.cloud.cluster.ClusterManagerImpl.pingManagementNode(ClusterManagerImpl.java:1405) at com.cloud.cluster.ClusterManagerImpl.pingManagementNode(ClusterManagerImpl.java:1384) at com.cloud.cluster.ClusterManagerImpl.checkConflicts(ClusterManagerImpl.java:1461) at com.cloud.cluster.ClusterManagerImpl.configure(ClusterManagerImpl.java:1347) at com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:111) at com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:54) at java.util.TimerThread.mainLoop(Timer.java:555) at java.util.TimerThread.run(Timer.java:505) 2014-03-22 22:45:57,994 INFO
Re: [求助] v4.2.1 启动报错
补充一些信息： [root@cs-manager ~]# netstat -antp| grep 9090 tcp0 0 :::9090 :::* LISTEN 4282/java [root@cs-manager ~]# ps -ef | grep java| grep 4282 cloud 4282 1 4 22:45 ?00:01:52 /usr/lib/jvm/java/bin/java -Djava.awt.headless=true -Dcom.sun.management.jmxremote.port=45219 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Xmx2g -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/var/log/cloudstack/management/ -XX:PermSize=512M -XX:MaxPermSize=800m -classpath :::/etc/cloudstack/management:/usr/share/cloudstack-management/setup:/usr/share/cloudstack-management/bin/bootstrap.jar:/usr/share/cloudstack-management/bin/tomcat-juli.jar:/usr/share/java/commons-daemon.jar -Dcatalina.base=/usr/share/cloudstack-management -Dcatalina.home=/usr/share/cloudstack-management -Djava.endorsed.dirs= -Djava.io.tmpdir=/usr/share/cloudstack-management/temp -Djava.util.logging.config.file=/usr/share/cloudstack-management/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager org.apache.catalina.startup.Bootstrap start 2014-03-22 15:23 GMT+08:00 风南 winnery...@gmail.com: 各位好。 不好意思，刚才Gmail的快捷键误发了和一个没有写完的邮件，请管理员删除。 安装的4.2.1一直都没有启动成功过，请各位高手帮忙，非常感谢。 环境如下： management-server: 运行在vmware workstation的虚拟机中，网络桥接模式。 物理宿主机为windows7，IP：192.168.11.30 配置： CPU:：Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz 两个 内存：2GB 磁盘：80GB IP： 192.168.11.61 GW: 192.168.11.1 Host： 运行在另一台物理主机，XenServer6.1.0 配置： CPU:：Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz 内存：8GB 磁盘：2TB IP： 192.168.11.40 GW: 192.168.11.1 一级存储和二级存储使用NFS模式，NFS服务端：management-server（192.168.11.61） 中： primary: /export/primary secondary: /export/secondary 在Host中挂载NFS读写都没有问题 management-server iptables: [root@cs-manager management]# cat /etc/sysconfig/iptables # Generated by iptables-save v1.4.7 on Mon Mar 17 06:02:02 2014 *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [999012:2307279867] -A INPUT -p tcp -m tcp --dport 9090 -j ACCEPT -A INPUT -p tcp -m tcp --dport 8250 -j ACCEPT -A INPUT -p tcp -m tcp --dport 7080 -j ACCEPT -A INPUT -p tcp -m tcp --dport 8080 -j ACCEPT -A INPUT -p tcp -m tcp --dport 111 -j ACCEPT -A INPUT -p udp -m udp --dport 111 -j ACCEPT -A INPUT -p tcp -m tcp --dport 2049 -j ACCEPT -A INPUT -p tcp -m tcp --dport 32803 -j ACCEPT -A INPUT -p udp -m udp --dport 32769 -j ACCEPT -A INPUT -p tcp -m tcp --dport 892 -j ACCEPT -A INPUT -p udp -m udp --dport 892 -j ACCEPT -A INPUT -p tcp -m tcp --dport 875 -j ACCEPT -A INPUT -p udp -m udp --dport 875 -j ACCEPT -A INPUT -p tcp -m tcp --dport 662 -j ACCEPT -A INPUT -p udp -m udp --dport 662 -j ACCEPT -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT -A INPUT -p icmp -j ACCEPT -A INPUT -i lo -j ACCEPT -A INPUT -p tcp -m state --state NEW -m tcp --dport 22 -j ACCEPT -A INPUT -j REJECT --reject-with icmp-host-prohibited -A FORWARD -j REJECT --reject-with icmp-host-prohibited COMMIT # Completed on Mon Mar 17 06:02:02 2014 完整日志文件请见：http://hctysoft.com/management-server.log 从日志中分析来看在启动Console Proxy VM的报错，下面是我截取的一些关键的management-server日志片段： catalina.out: INFO [cloud.cluster.ClusterManagerImpl] (Timer-2:) register cluster listener class com.cloud.cluster.LockMasterListener INFO [cloud.cluster.ClusterManagerImpl] (Timer-2:) Trying to connect to 192.168.11.61 ERROR [cloud.cluster.ClusterManagerImpl] (Timer-2:) Unable to ping management server at 192.168.11.61:9090 due to ConnectException java.net.ConnectException: Connection refused at sun.nio.ch.Net.connect0(Native Method) at sun.nio.ch.Net.connect(Net.java:465) at sun.nio.ch.Net.connect(Net.java:457) at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:670) at com.cloud.cluster.ClusterManagerImpl.pingManagementNode(ClusterManagerImpl.java:1405) at com.cloud.cluster.ClusterManagerImpl.pingManagementNode(ClusterManagerImpl.java:1384) at com.cloud.cluster.ClusterManagerImpl.checkConflicts(ClusterManagerImpl.java:1461) at com.cloud.cluster.ClusterManagerImpl.configure(ClusterManagerImpl.java:1347) at com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:111) at com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:54) at java.util.TimerThread.mainLoop(Timer.java:555) at java.util.TimerThread.run(Timer.java:505) management-server.log 2014-03-22 22:45:57,912 INFO [cloud.cluster.ClusterManagerImpl] (Timer-2:null) Cluster node IP : 192.168.11.61 2014-03-22 22:45:57,959 DEBUG [utils.db.ConnectionConcierge] (Timer-2:null) Registering a database connection for LockMaster1 2014-03-22 22:45:57,959 INFO [utils.db.Merovingian2] (Timer-2:null) Cleaning up locks for 52243566829 2014-03-22 22:45:57,960 INFO [utils.db.Merovingian2] (Timer-2:null) Released 0 locks for 52243566829 2014-03-22 22:45:57,960 INFO
XenServer 问题 AgentUnavailableException: Resource [Host:1] is unreachable: Host 1: Unable to start instance due to null
Hi，各位： 今天弄过了一天一直有一个问题搞不定，前来请教各位，环境如下： 2台机器： 管理端v4.2.1：cloudstack-manager 装在vmware里，桥接网络方式 192.168.11.60， 1,2级存储也在这个机器上NFS Host：XenServer 6.1 192.168.11.40 问题出现在使用向导配置执行 Creating system VMs (this may take a while) 这一步的时候。 XenSever中挂载的nfs没有问题，可以正常读写。 管理端日志异常信息： 2014-03-16 03:54:38,779 DEBUG [cloud.capacity.CapacityManagerImpl] (consoleproxy-1:null) release mem from host: 1, old used: 1342177280,reserved: 0, total: 7224936960; new used: 268435456,reserved:0; movedfromreserved: false,moveToReserveredfalse 2014-03-16 03:54:38,789 WARN [cloud.consoleproxy.ConsoleProxyManagerImpl] (consoleproxy-1:null) Exception while trying to start console proxy com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[ConsoleProxy|v-2-VM]Scope=interface com.cloud.dc.DataCenter; id=1 at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:841) at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:577) at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:570) at com.cloud.consoleproxy.ConsoleProxyManagerImpl.startProxy(ConsoleProxyManagerImpl.java:556) at com.cloud.consoleproxy.ConsoleProxyManagerImpl.allocCapacity(ConsoleProxyManagerImpl.java:928) at com.cloud.consoleproxy.ConsoleProxyManagerImpl.expandPool(ConsoleProxyManagerImpl.java:1672) at com.cloud.consoleproxy.ConsoleProxyManagerImpl.expandPool(ConsoleProxyManagerImpl.java:157) at com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:111) at com.cloud.vm.SystemVmLoadScanner.access$100(SystemVmLoadScanner.java:33) at com.cloud.vm.SystemVmLoadScanner$1.reallyRun(SystemVmLoadScanner.java:81) at com.cloud.vm.SystemVmLoadScanner$1.run(SystemVmLoadScanner.java:72) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) 2014-03-16 03:54:41,326 INFO [storage.volume.VolumeServiceImpl] (secstorage-1:null) Unable to acquire lock on VMTemplateStoragePool 1 2014-03-16 03:54:41,330 ERROR [cloud.vm.VirtualMachineManagerImpl] (secstorage-1:null) Failed to start instance VM[SecondaryStorageVm|s-1-VM] java.lang.NullPointerException at org.apache.cloudstack.storage.volume.VolumeServiceImpl.createBaseImageAsync(VolumeServiceImpl.java:428) at org.apache.cloudstack.storage.volume.VolumeServiceImpl.createVolumeFromTemplateAsync(VolumeServiceImpl.java:575) at com.cloud.storage.VolumeManagerImpl.recreateVolume(VolumeManagerImpl.java:2577) at com.cloud.storage.VolumeManagerImpl.prepare(VolumeManagerImpl.java:2641) at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:888) at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:577) at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:570) at com.cloud.storage.secondary.SecondaryStorageManagerImpl.startSecStorageVm(SecondaryStorageManagerImpl.java:267) at com.cloud.storage.secondary.SecondaryStorageManagerImpl.allocCapacity(SecondaryStorageManagerImpl.java:696) at com.cloud.storage.secondary.SecondaryStorageManagerImpl.expandPool(SecondaryStorageManagerImpl.java:1300) at com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:123) at com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:50) at com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:104) at com.cloud.vm.SystemVmLoadScanner.access$100(SystemVmLoadScanner.java:33) at com.cloud.vm.SystemVmLoadScanner$1.reallyRun(SystemVmLoadScanner.java:81) at com.cloud.vm.SystemVmLoadScanner$1.run(SystemVmLoadScanner.java:72) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) 2014-03-16 03:54:41,343 DEBUG [cloud.vm.VirtualMachineManagerImpl] (secstorage-1:null) Cleaning up resources for the vm VM[SecondaryStorageVm|s-1-VM] in Starting state 2014-03-16 03:54:41,350 DEBUG [agent.transport.Request] (secstorage-1:null) Seq 1-1640628238:
