Thanks for the reply. Yes, I'm using KVM.
If I try and do a yum update on the cloud-agent, on the host machine, yum returns that there is no update available for it. I've even tried uninstalling it and reinstalling the cloud-agent. Also the cloud-agent service is running on the host. I cannot telnet into port 8250 on the management server, even with the management server's firewall disabled. I guess my question is ... why is it trying to connect over SSL? Have the packages for the yum repository for Cloudstack 4.0.1 been set up to work with SSL (where as 4.0.0 was not)? Do I now have to configure SSL on my management server? That's not going to be a solution. Is my only option to now go get the source files and install it myself, or does anyone know if you can disable SSL in the options? Thanks again, Jeremy From: Sheng Yang <sh...@yasker.org> To: "<cloudstack-users@incubator.apache.org>" <cloudstack-users@incubator.apache.org>, Date: 03/05/2013 02:25 PM Subject: Re: Hosts not adding - SSL issue? Could you check the network connection? And if the agent is upgraded and running on the host? I suppose you're using KVM. Use "telnet 192.168.100.237 8250" to check connectivity. --Sheng On Tue, Mar 5, 2013 at 11:13 AM, <jsm...@h2l.com> wrote: > I decided to reinstall cloud stack and start over as I was having a some > issues. I've previously been able to get hosts into the cloud, but after > reinstalling (following the same instructions I did before - as I document > what I do), my hosts will not join. It seems to be complaining about SSL > in the agent.log on both hosts. I'm not looking to use SSL, I don't know > why it's asking for it. While creating the cloud I selected to use a > basic flat network as this is for a private cloud. > > I don't know if the SSL got introduced from 4.0 to 4.0.1 or what, but I > don't want it, and don't know how it got in there this time around. I > installed the management server via yum on a CentOS 6 server. Any > thoughts? > > 2013-03-05 12:03:14,221 INFO [cloud.agent.AgentShell] (main:null) > Implementation Version is 4.0.1.20130201075054 > 2013-03-05 12:03:14,221 INFO [cloud.agent.AgentShell] (main:null) > agent.properties found at /etc/cloud/agent/agent.properties > 2013-03-05 12:03:14,222 INFO [cloud.agent.AgentShell] (main:null) > Defaulting to using properties file for storage > 2013-03-05 12:03:14,224 INFO [cloud.agent.AgentShell] (main:null) > Defaulting to the constant time backoff algorithm > 2013-03-05 12:03:14,291 INFO [cloud.agent.Agent] (main:null) id is 4 > 2013-03-05 12:03:14,392 INFO > [resource.virtualnetwork.VirtualRoutingResource] (main:null) > VirtualRoutingResource _scriptDir to use: scripts/network/domr/k > vm > 2013-03-05 12:03:15,317 INFO [kvm.resource.LibvirtComputingResource] > (main:null) No libvirt.vif.driver specififed. Defaults to BridgeVifDriver. > 2013-03-05 12:03:15,332 INFO [cloud.agent.Agent] (main:null) Agent [id = > 4 : type = LibvirtComputingResource : zone = 1 : pod = 1 : workers = 5 : > host = 1 > 92.168.100.237 : port = 8250 > 2013-03-05 12:03:15,340 INFO [utils.nio.NioClient] (Agent-Selector:null) > Connecting to 192.168.100.237:8250 > 2013-03-05 12:03:15,424 ERROR [utils.nio.NioConnection] > (Agent-Selector:null) Unable to initialize the threads. > java.io.IOException: SSL: Fail to init SSL! java.io.IOException: > Connection closed with -1 on reading size. > at com.cloud.utils.nio.NioClient.init(NioClient.java:83) > at com.cloud.utils.nio.NioConnection.run(NioConnection.java:108) > at java.lang.Thread.run(Thread.java:679) > 2013-03-05 12:03:20,428 INFO [utils.nio.NioClient] (Agent-Selector:null) > Connecting to 192.168.100.237:8250 > 2013-03-05 12:03:20,430 ERROR [utils.nio.NioConnection] > (Agent-Selector:null) Unable to initialize the threads. > java.io.IOException: SSL: Fail to init SSL! java.io.IOException: > Connection closed with -1 on reading size. > at com.cloud.utils.nio.NioClient.init(NioClient.java:83)
