Re: Re: Re: [求助] v4.2.1 启动报错
实际上你的问题是你的系统虚拟机起不来，所以还是只能回到最早你给的log来看。从这段可以看出来，创建不了系统虚拟机是因为没找到合适的存储，你要先看看nfs配置是否正确。 2014-03-22 22:47:28,915 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl](consoleproxy-1:null) We need to allocate new storagepool for this volume 2014-03-22 22:47:28,915 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl](consoleproxy-1:null) Calling StoragePoolAllocators to find suitable pools 2014-03-22 22:47:28,915 DEBUG [storage.allocator.LocalStoragePoolAllocator](consoleproxy-1:null) LocalStoragePoolAllocator trying to find storage pool to fit the vm 2014-03-22 22:47:28,917 DEBUG [storage.allocator.LocalStoragePoolAllocator](consoleproxy-1:null) LocalStoragePoolAllocator returning 0 suitable storage pools 2014-03-22 22:47:28,917 DEBUG [storage.allocator.ClusterScopeStoragePoolAllocator] (consoleproxy-1:null)ClusterScopeStoragePoolAllocator looking for storage pool 2014-03-22 22:47:28,917 DEBUG [storage.allocator.ZoneWideStoragePoolAllocator] (consoleproxy-1:null)ZoneWideStoragePoolAllocator to find storage pool 2014-03-22 22:47:28,917 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (consoleproxy-1:null) No suitable pools found for volume: Vol[1|vm=1|ROOT]under cluster: 1 刘宇超 发件人： ganglin_lan 发送时间： 2014-03-23 13:45:19 收件人： 风南; users-cn 抄送： 主题： Re: Re: [求助] v4.2.1 启动报错 其实没你想的那么难，可能一个人装有的时候会陷进去，等发现问题后感叹原来是这么简单的问题难倒了你这么久，我觉得你再从安装步骤上检查一下，有没有遗漏或不正确的配置。进入ssvm嘛，xencenter连到xenserver上查看 ganglin_lan 发件人： 风南 发送时间： 2014-03-23 11:24 收件人： ganglin_lan 主题： Re: Re: [求助] v4.2.1 启动报错 唉，不行！还是老样子。 装个cs这么难！两周了都还没搞定 :( 你知道怎么进入ssvm吗？ 2014-03-22 23:56 GMT+08:00 ganglin_lan ganglin_...@tcloudcomputing.com: 跟二级存储应该没关系，我的测试环境也就100G，恭候佳音 ganglin_lan 发件人： 风南 发送时间： 2014-03-22 23:53 收件人： ganglin_lan 主题： Re: Re: [求助] v4.2.1 启动报错 确实重装过，不过db我都drop了，也重新初始化了。我按照你说的再做一次。 刚才我又看了一下官方，怀疑可能是我的二级存储空间太小了，我的才80G，文档中说最小250G，明天我再添加一块500G的硬盘试试。 多谢你的回复，有结果我会告诉各位。 2014-03-22 23:29 GMT+08:00 ganglin_lan ganglin_...@tcloudcomputing.com: 根据你提供的日志信息，你的DB里面已经存在了host = 192.168.11.61 的management server配置，你是不是重装cloudstack没有初始化DB呢，如果是新装环境，建议你做以下步奏： 1、停止cloudstack-management 服务 2、初始化mysql数据库，使用 cloudstack-setup-databases cloud:set cloud user passwd@localhost --deploy-as=root:mysql root user password 3、 cloudstack-setup-management 然后再配置试试 ganglin_lan 发件人： 风南 发送时间： 2014-03-22 23:17 收件人： ganglin_lan 主题： Re: Re: [求助] v4.2.1 启动报错 iptables关了貌似还是一样的问题，截了一段异常日志： 2014-03-23 07:14:52,069 DEBUG [allocator.impl.FirstFitAllocator] (secstorage-1:FirstFitRoutingAllocator) Looking for hosts in dc: 1 pod:1 cluster:1 2014-03-23 07:14:52,071 DEBUG [allocator.impl.FirstFitAllocator] (secstorage-1:FirstFitRoutingAllocator) FirstFitAllocator has 1 hosts to check for allocation: [Host[-1-Routing]] 2014-03-23 07:14:52,073 DEBUG [allocator.impl.FirstFitAllocator] (secstorage-1:FirstFitRoutingAllocator) Found 1 hosts for allocation after prioritization: [Host[-1-Routing]] 2014-03-23 07:14:52,073 DEBUG [allocator.impl.FirstFitAllocator] (secstorage-1:FirstFitRoutingAllocator) Looking for speed=500Mhz, Ram=256 2014-03-23 07:14:52,076 DEBUG [cloud.capacity.CapacityManagerImpl] (secstorage-1:FirstFitRoutingAllocator) Checking if host: 1 has enough capacity for requested CPU: 500 and requested RAM: 268435456 , cpuOverprovisioningFactor: 1.0 2014-03-23 07:14:52,078 DEBUG [cloud.capacity.CapacityManagerImpl] (secstorage-1:FirstFitRoutingAllocator) Hosts's actual total CPU: 27744 and CPU after applying overprovisioning: 27744 2014-03-23 07:14:52,078 DEBUG [cloud.capacity.CapacityManagerImpl] (secstorage-1:FirstFitRoutingAllocator) Free CPU: 27744 , Requested CPU: 500 2014-03-23 07:14:52,078 DEBUG [cloud.capacity.CapacityManagerImpl] (secstorage-1:FirstFitRoutingAllocator) Free RAM: 3773286656 , Requested RAM: 268435456 2014-03-23 07:14:52,078 DEBUG [cloud.capacity.CapacityManagerImpl] (secstorage-1:FirstFitRoutingAllocator) Host has enough CPU and RAM available 2014-03-23 07:14:52,078 DEBUG [cloud.capacity.CapacityManagerImpl] (secstorage-1:FirstFitRoutingAllocator) STATS: Can alloc CPU from host: 1, used: 0, reserved: 0, actual total: 27744, total with overprovisioning: 27744; requested cpu:500,alloc_from_last_host?:false ,considerReservedCapacity?: true 2014-03-23 07:14:52,078 DEBUG [cloud.capacity.CapacityManagerImpl] (secstorage-1:FirstFitRoutingAllocator) STATS: Can alloc MEM from host: 1, used: 0, reserved: 0, total: 3773286656; requested mem: 268435456,alloc_from_last_host?:false ,considerReservedCapacity?: true 2014-03-23 07:14:52,078 DEBUG [allocator.impl.FirstFitAllocator] (secstorage-1:FirstFitRoutingAllocator) Found a suitable host, adding to list: 1 2014-03-23 07:14:52,078 DEBUG [allocator.impl.FirstFitAllocator] (secstorage-1:FirstFitRoutingAllocator) Host Allocator returning 1 suitable hosts 2014-03-23 07:14:52,079 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (secstorage-1:null) Checking suitable pools for volume (Id, Type): (296,ROOT) 2014-03-23 07:14:52,079 DEBUG
[求助] 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
Re: Re: [求助] v4.2.1 启动报错
cloudstack 全局设置中的host 参数设置成management-server IP，management.network.cidr 设置成相应的值了吗 ganglin_lan 发件人： 风南 发送时间： 2014-03-22 15:30 收件人： users-cn 主题： 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
Re: Re: [求助] v4.2.1 启动报错
先把iptables stop 了试试呢？ ganglin_lan 发件人： 风南 发送时间： 2014-03-22 20:05 收件人： users-cn; ganglin_lan 主题： Re: Re: [求助] v4.2.1 启动报错 设置过了，值如下： host = 192.168.11.61 management.network.cidr = 192.168.11.0/24 2014-03-22 19:13 GMT+08:00 ganglin_lan ganglin_...@tcloudcomputing.com: cloudstack 全局设置中的host 参数设置成management-server IP，management.network.cidr 设置成相应的值了吗 ganglin_lan 发件人： 风南 发送时间： 2014-03-22 15:30 收件人： users-cn 主题： 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
Re: Re: [求助] v4.2.1 启动报错
根据你提供的日志信息，你的DB里面已经存在了host = 192.168.11.61 的management server配置，你是不是重装cloudstack没有初始化DB呢，如果是新装环境，建议你做以下步奏： 1、停止cloudstack-management 服务 2、初始化mysql数据库，使用 cloudstack-setup-databases cloud:set cloud user passwd@localhost --deploy-as=root:mysql root user password 3、 cloudstack-setup-management 然后再配置试试 ganglin_lan 发件人： 风南 发送时间： 2014-03-22 23:17 收件人： ganglin_lan 主题： Re: Re: [求助] v4.2.1 启动报错 iptables关了貌似还是一样的问题，截了一段异常日志： 2014-03-23 07:14:52,069 DEBUG [allocator.impl.FirstFitAllocator] (secstorage-1:FirstFitRoutingAllocator) Looking for hosts in dc: 1 pod:1 cluster:1 2014-03-23 07:14:52,071 DEBUG [allocator.impl.FirstFitAllocator] (secstorage-1:FirstFitRoutingAllocator) FirstFitAllocator has 1 hosts to check for allocation: [Host[-1-Routing]] 2014-03-23 07:14:52,073 DEBUG [allocator.impl.FirstFitAllocator] (secstorage-1:FirstFitRoutingAllocator) Found 1 hosts for allocation after prioritization: [Host[-1-Routing]] 2014-03-23 07:14:52,073 DEBUG [allocator.impl.FirstFitAllocator] (secstorage-1:FirstFitRoutingAllocator) Looking for speed=500Mhz, Ram=256 2014-03-23 07:14:52,076 DEBUG [cloud.capacity.CapacityManagerImpl] (secstorage-1:FirstFitRoutingAllocator) Checking if host: 1 has enough capacity for requested CPU: 500 and requested RAM: 268435456 , cpuOverprovisioningFactor: 1.0 2014-03-23 07:14:52,078 DEBUG [cloud.capacity.CapacityManagerImpl] (secstorage-1:FirstFitRoutingAllocator) Hosts's actual total CPU: 27744 and CPU after applying overprovisioning: 27744 2014-03-23 07:14:52,078 DEBUG [cloud.capacity.CapacityManagerImpl] (secstorage-1:FirstFitRoutingAllocator) Free CPU: 27744 , Requested CPU: 500 2014-03-23 07:14:52,078 DEBUG [cloud.capacity.CapacityManagerImpl] (secstorage-1:FirstFitRoutingAllocator) Free RAM: 3773286656 , Requested RAM: 268435456 2014-03-23 07:14:52,078 DEBUG [cloud.capacity.CapacityManagerImpl] (secstorage-1:FirstFitRoutingAllocator) Host has enough CPU and RAM available 2014-03-23 07:14:52,078 DEBUG [cloud.capacity.CapacityManagerImpl] (secstorage-1:FirstFitRoutingAllocator) STATS: Can alloc CPU from host: 1, used: 0, reserved: 0, actual total: 27744, total with overprovisioning: 27744; requested cpu:500,alloc_from_last_host?:false ,considerReservedCapacity?: true 2014-03-23 07:14:52,078 DEBUG [cloud.capacity.CapacityManagerImpl] (secstorage-1:FirstFitRoutingAllocator) STATS: Can alloc MEM from host: 1, used: 0, reserved: 0, total: 3773286656; requested mem: 268435456,alloc_from_last_host?:false ,considerReservedCapacity?: true 2014-03-23 07:14:52,078 DEBUG [allocator.impl.FirstFitAllocator] (secstorage-1:FirstFitRoutingAllocator) Found a suitable host, adding to list: 1 2014-03-23 07:14:52,078 DEBUG [allocator.impl.FirstFitAllocator] (secstorage-1:FirstFitRoutingAllocator) Host Allocator returning 1 suitable hosts 2014-03-23 07:14:52,079 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (secstorage-1:null) Checking suitable pools for volume (Id, Type): (296,ROOT) 2014-03-23 07:14:52,079 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (secstorage-1:null) We need to allocate new storagepool for this volume 2014-03-23 07:14:52,079 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (secstorage-1:null) Calling StoragePoolAllocators to find suitable pools 2014-03-23 07:14:52,080 DEBUG [storage.allocator.LocalStoragePoolAllocator] (secstorage-1:null) LocalStoragePoolAllocator trying to find storage pool to fit the vm 2014-03-23 07:14:52,081 DEBUG [storage.allocator.LocalStoragePoolAllocator] (secstorage-1:null) LocalStoragePoolAllocator returning 0 suitable storage pools 2014-03-23 07:14:52,082 DEBUG [storage.allocator.ClusterScopeStoragePoolAllocator] (secstorage-1:null) ClusterScopeStoragePoolAllocator looking for storage pool 2014-03-23 07:14:52,082 DEBUG [storage.allocator.ZoneWideStoragePoolAllocator] (secstorage-1:null) ZoneWideStoragePoolAllocator to find storage pool 2014-03-23 07:14:52,082 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (secstorage-1:null) No suitable pools found for volume: Vol[296|vm=295|ROOT] under cluster: 1 2014-03-23 07:14:52,082 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (secstorage-1:null) No suitable pools found 2014-03-23 07:14:52,082 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (secstorage-1:null) No suitable storagePools found under this Cluster: 1 2014-03-23 07:14:52,083 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (secstorage-1:null) Could not find suitable Deployment Destination for this VM under any clusters, returning. 2014-03-23 07:14:52,083 DEBUG [cloud.deploy.FirstFitPlanner] (secstorage-1:null) Searching all possible resources under this Zone: 1 2014-03-23 07:14:52,084 DEBUG [cloud.deploy.FirstFitPlanner] (secstorage-1:null) Listing clusters in order of aggregate capacity, that have (atleast one host with) enough CPU and RAM capacity under this Zone: 1 2014-03-23 07:14:52,086 DEBUG [cloud.deploy.FirstFitPlanner] (secstorage-1:null) Removing from the clusterId list
