v4.2.1 启动报错

2014-03-22 Thread 风南
各位好。
 安装的4.2.1一直都没有启动成功过,请各位高手帮忙,非常感谢。
环境如下:

management-server:
   运行在vmware workstation的虚拟中,网络桥接模式。
   配置:
   CPU::Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz  两个
   内存:2GB

-- 
Best Regards


[求助] v4.2.1 启动报错

2014-03-22 Thread 风南
各位好。

不好意思,刚才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 启动报错

2014-03-22 Thread 风南
补充一些信息:
[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 启动报错

2014-03-22 Thread ganglin_lan
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 启动报错

2014-03-22 Thread ganglin_lan
先把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 启动报错

2014-03-22 Thread ganglin_lan
根据你提供的日志信息,你的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 

Re: Management IP addresses pool exhausted

2014-03-22 Thread abhisek basu
Before making changes in DB, try to decrease the expung interval and delay 
interval to very low value, restart management service. This way the VM expung 
process will be faster and eventually address the issue.

Sent from my iPhone

 On 22 Mar 2014, at 8:58 am, Umair Azam ua...@i2cinc.com wrote:
 
 SELECT * FROM cloud.vm_instance where (name like s-% or name like v-%);
 
 shows me all VM's is expunging state and expunge delay/interval values are 
 set to 86400
 
 Umair Azam
 
 On 3/22/2014 6:58 AM, Umair Azam wrote:
 Hi,
 
 How to free exhausted IP addresses pool from cloudstack, Cloudstack was 
 unable to launch systems vms at first and especially ssvm due to strange nfs 
 time out issues so all IP's were used during this issue and now is there any 
 precise way of releasing these IP's and starting system VM's again?.
 


Re: Virtual Router doesn't start

2014-03-22 Thread Kambiz Darabi
Hi Alena,

thank you for your help.

The query returns no rows, i.e. nics.removed was not null, but I removed
the row though to see what happens: a new virtual router was created
which also couldn't be started due to the same NPE. I reverted the
change by restoring from the dump.

I have to mention that prior to the restart, r-7-VM was the router which
was used by my instances. I deleted the router using the UI after the first
occurrence of the NPE, because a post with a similar problem suggested
that the deleted router would be recreated again (and this procedure
solved the problem).

Below I have attached the state of the two tables.

Anything else I can try?

Thank you


Kambiz

mysql select n.id, n.removed, n.ip4_address, n.netmask, n.gateway, n.ip_type, 
n.reserver_name, n.network_id, i.id as instance_id, i.name, i.state, i.type 
from vm_instance i join nics n on n.instance_id = i.id where i.type = 
'DomainRouter';
++-+---+---+-+-+--++-+-+---+--+
| id | removed | ip4_address   | netmask   | gateway | 
ip_type | reserver_name| network_id | instance_id | name| state 
| type |
++-+---+---+-+-+--++-+-+---+--+
|  9 | 2014-03-17 11:27:58 | 10.124.99.1   | 255.255.255.0 | NULL| NULL 
   | ExternalGuestNetworkGuru |204 |   4 | r-4-VM  | Expunging 
| DomainRouter |
| 10 | 2014-03-17 11:27:58 | NULL  | NULL  | NULL| NULL 
   | ControlNetworkGuru   |202 |   4 | r-4-VM  | Expunging 
| DomainRouter |
| 11 | 2014-03-17 11:27:58 | 10.193.17.139 | 255.255.255.0 | 10.193.17.1 | NULL 
   | PublicNetworkGuru|200 |   4 | r-4-VM  | Expunging 
| DomainRouter |
| 14 | 2014-03-17 11:27:52 | 10.124.99.1   | 255.255.255.0 | NULL| NULL 
   | ExternalGuestNetworkGuru |205 |   7 | r-7-VM  | Expunging 
| DomainRouter |
| 15 | 2014-03-17 11:27:52 | NULL  | NULL  | NULL| NULL 
   | ControlNetworkGuru   |202 |   7 | r-7-VM  | Expunging 
| DomainRouter |
| 16 | 2014-03-17 11:27:52 | 10.193.17.190 | 255.255.255.0 | 10.193.17.1 | NULL 
   | PublicNetworkGuru|200 |   7 | r-7-VM  | Expunging 
| DomainRouter |
| 26 | 2014-03-18 08:11:16 | 10.124.99.1   | 255.255.255.0 | NULL| NULL 
   | ExternalGuestNetworkGuru |205 |  18 | r-18-VM | Expunging 
| DomainRouter |
| 27 | 2014-03-18 08:11:16 | NULL  | NULL  | NULL| NULL 
   | ControlNetworkGuru   |202 |  18 | r-18-VM | Expunging 
| DomainRouter |
| 28 | 2014-03-18 08:11:16 | 10.193.17.190 | 255.255.255.0 | 10.193.17.1 | NULL 
   | PublicNetworkGuru|200 |  18 | r-18-VM | Expunging 
| DomainRouter |
| 29 | NULL| 10.124.99.1   | 255.255.255.0 | NULL| NULL 
   | ExternalGuestNetworkGuru |205 |  19 | r-19-VM | Stopped   
| DomainRouter |
| 30 | NULL| NULL  | NULL  | NULL| NULL 
   | ControlNetworkGuru   |202 |  19 | r-19-VM | Stopped   
| DomainRouter |
| 31 | NULL| 10.193.17.190 | 255.255.255.0 | 10.193.17.1 | NULL 
   | PublicNetworkGuru|200 |  19 | r-19-VM | Stopped   
| DomainRouter |
++-+---+---+-+-+--++-+-+---+--+

mysql select * from router_network_ref;
++---+++
| id | router_id | network_id | guest_type |
++---+++
|  1 | 4 |204 | Isolated   |
|  2 | 7 |205 | Isolated   |
|  3 |18 |205 | Isolated   |
|  4 |19 |205 | Isolated   |
++---+++



Alena Prokharchyk alena.prokharc...@citrix.com wrote:
 
 The error happens not because Ip is null, but because the nic in a certain
 network can¹t be found. Looks like there is some bug in VPC nic
 plug/unplug for Guest networks process.

 Kambiz, please do the following to fix it:

 1) Stop the MS
 2) Take the DB dump of cloud db in case  you have to revert back.
 3) Run the query:

 select * from router_network_ref where router_id=id of your VR) and
 network_id not in (select network_id from nics where instance_id=ID of
 your VR and removed is null);

 It will give you the list of networks refs that somehow weren¹t cleaned
 during the nic detach. Remove the entry returned from router_network_ref
 table.

 Let me know how it works.

 -Alena.


 On 3/21/14, 3:36 PM, Kambiz Darabi dar...@m-creations.com 

RE: CloudStack 4.2.1 XenServer version support

2014-03-22 Thread Amin Samir
Hi Paul,

Thanks for the tip.

 
Kind Regards

Amin 

 
 
From: Paul Angus [mailto:paul.an...@shapeblue.com] 
Sent: Friday, 21 March 2014 6:29 PM
To: users@cloudstack.apache.org
Subject: RE: CloudStack 4.2.1 XenServer version support

 
Hi Amir,

 
Will 4.3.x support XenServer 6.2 in 'upgraded' management server installations?

 
Regards,

Paul Angus

Cloud Architect
S: +44 20 3603 0540 | M: +447711418784 | T: @CloudyAngus

paul.an...@shapeblue.com mailto:paul.an...@shapeblue.com 

 
From: Amin Samir [mailto:a...@opencloud.net.au mailto:a...@opencloud.net.au ] 
Sent: 21 March 2014 01:29
To: users@cloudstack.apache.org mailto:users@cloudstack.apache.org 
Subject: RE: CloudStack 4.2.1 XenServer version support

 
Yes it is supported in new management server installation only, meaning if you 
upgrade from an earlier cloudstack version you will have only upgrade path to 
xen server 6.1, if you have a new cloud stack management installation then you 
can have xen server 6.2 for the compatibility matrix check out the below table.

 

 
 
Kind Regards

Amin   

 
 
 
-Original Message-
From: Peter Sadowski [mailto:peter.m.sadow...@gmail.com 
mailto:peter.m.sadow...@gmail.com ] 
Sent: Friday, 21 March 2014 1:04 AM
To: users@cloudstack.apache.org mailto:users@cloudstack.apache.org 
Subject: CloudStack 4.2.1 XenServer version support

 
Hi, 

 
 
 
Since the release of CS 4.2.1 is XenServer 6.2 supported?

 
In the install docs all I see is support up to version 6.0.2.

 
 
 
Thx in advance, 

 
 
 
Peter 

 
 
 
 
 
Need Enterprise Grade Support for Apache CloudStack?
Our CloudStack Infrastructure Support 
http://shapeblue.com/cloudstack-infrastructure-support/ offers the best 24/7 
SLA for CloudStack Environments.

Apache CloudStack Bootcamp training courses

**NEW!** CloudStack 4.2.1 training http://shapeblue.com/cloudstack-training/ 
18th-19th February 2014, Brazil. Classroom 
http://shapeblue.com/cloudstack-training/ 
17th-23rd March 2014, Region A. Instructor led, On-line 
http://shapeblue.com/cloudstack-training/ 
24th-28th March 2014, Region B. Instructor led, On-line 
http://shapeblue.com/cloudstack-training/ 
16th-20th June 2014, Region A. Instructor led, On-line 
http://shapeblue.com/cloudstack-training/ 
23rd-27th June 2014, Region B. Instructor led, On-line 
http://shapeblue.com/cloudstack-training/ 

 
This email and any attachments to it may be confidential and are intended 
solely for the use of the individual to whom it is addressed. Any views or 
opinions expressed are solely those of the author and do not necessarily 
represent those of Shape Blue Ltd or related companies. If you are not the 
intended recipient of this email, you must neither take any action based upon 
its contents, nor copy or show it to anyone. Please contact the sender if you 
believe you have received this email in error. Shape Blue Ltd is a company 
incorporated in England  Wales. ShapeBlue Services India LLP is a company 
incorporated in India and is operated under license from Shape Blue Ltd. Shape 
Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is 
operated under license from Shape Blue Ltd. ShapeBlue is a registered 
trademark. 



Simple network configuration

2014-03-22 Thread Alex Hartner
I just completed a fresh installation of 4.2.1 on CentOS 6.5 with both the 
management and the agent running on a single host. The plan is to keep things 
simple as this setup will be used for development rather than hosting 
production level services. After the initial setup everything looked great 
until I rebooted the system.

From here on I am no longer able to access the network from the physical 
server. It doesn’t happen all the time, but often enough. Maybe 1 out of 5 
times does the network stack initially properly.

Here is my network configuration

Physical server:
Device: eth0
Assigned via DHCP. Fixed on the DHCP server to the MAC address of the server to 
192.168.0.6
DNS name / mapping configured for both name and IP (both directions) to allow 
for the system to find the hostname

ifcfg-eth0
==
DEVICE=eth0
TYPE=Ethernet
UUID= XX
ONBOOT=yes
NM_CONTROLLED=no
BOOTPROTO=dhcp
HWADDR=XX
DEFROUTE=yes
PEERDNS=NO
PEERROUTES=yes
IPV4_FAILURE_FATAL=yes
IPV6INIT=no
NAME=System eth0
BRIDGE=cloudbr0

ifcfg-cloudbr0
=
DEVICE=cloudbr0
TYPE=Bridge
UUID= XX
ONBOOT=yes
NM_CONTROLLED=no
BOOTPROTO=dhcp
HWADDR=XX
DEFROUTE=yes
PEERDNS=no
PEERROUTES=yes
IPV4_FAILURE_FATAL=yes
IPV6INIT=no
NAME=System eth0

One of the issues is that when the problem occurs the system it not able to 
access any other system on the local network and hence not able to resolve its 
own hostname, causing the cloudstack-agent/management server also to fail.

Here is the resolve.conf file
==
# Generated by NetworkManager
search mydomain.com
# No nameservers found; try putting DNS servers into your
# ifcfg files in /etc/sysconfig/network-scripts like so:
#
# DNS1=xxx.xxx.xxx.xxx
# DNS2=xxx.xxx.xxx.xxx
# DOMAIN=lab.foo.com bar.foo.com

Here is the routing table
===
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse Iface
192.168.0.0 0.0.0.0 255.255.255.0   U 0  00 eth0
192.168.122.0   0.0.0.0 255.255.255.0   U 0  00 virbr0
169.254.0.0 0.0.0.0 255.255.0.0 U 0  00 cloud0
0.0.0.0 192.168.0.1 0.0.0.0 UG0  00 eth0

And the output from ifconfig
==
cloudbr0  Link encap:Ethernet  HWaddr XX
  inet6 addr: fe80::e44c:e4ff:fe1e:dde7/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:20 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:0 (0.0 b)  TX bytes:3852 (3.7 KiB)
eth0  Link encap:Ethernet  HWaddr XX
  inet addr:192.168.0.6  Bcast:192.168.0.255  Mask:255.255.255.0
  inet6 addr: fe80::52e5:49ff:fee1:7d12/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:306 errors:0 dropped:0 overruns:0 frame:0
  TX packets:212 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:37028 (36.1 KiB)  TX bytes:32638 (31.8 KiB)
  Interrupt:20 Memory:fbf0-fbf2
loLink encap:Local Loopback
  inet addr:127.0.0.1  Mask:255.0.0.0
  inet6 addr: ::1/128 Scope:Host
  UP LOOPBACK RUNNING  MTU:16436  Metric:1
  RX packets:119 errors:0 dropped:0 overruns:0 frame:0
  TX packets:119 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:10712 (10.4 KiB)  TX bytes:10712 (10.4 KiB)
virbr0Link encap:Ethernet  HWaddr XX
  inet addr:192.168.122.1  Bcast:192.168.122.255  Mask:255.255.255.0
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

Any pointers what I can do to get my network configuration working correctly.


Alex Hartner
Enterprise Architect
T +44 20 8238 7423
F
M
ahart...@thunderhead.commailto:ahart...@thunderhead.com

[http://thunderhead.com/email_signature/images/thf2.gif]Thunderhead 
Limited
www.thunderhead.comhttp://www.thunderhead.com WE'RE 
HIRING[http://thunderhead.com/email_signature/images/ar.gif]http://www.thunderhead.com/company/careers/available-roles/
 THE 
BLOG[http://thunderhead.com/email_signature/images/ar.gif]http://www.thunderhead.com/blog
[http://thunderhead.com/email_signature/images/lki.jpg]http://www.linkedin.com/company/25033
  [http://thunderhead.com/email_signature/images/tw.jpg] 
http://twitter.com/Thunderheadon   
[http://thunderhead.com/email_signature/images/rss.jpg] 
http://www.thunderhead.com/rss-feeds  
[http://thunderhead.com/email_signature/images/yt.jpg]