I'd be curious to know if it works by re-adding the host. I remember running into situations like this in the past, where the mgmt server was either not fully up or rejecting agents for some reason.
On Wed, Oct 1, 2014 at 7:01 AM, Wido den Hollander <w...@widodh.nl> wrote: > > > On 09/30/2014 09:26 AM, Daan Hoogland wrote: > > H all, > > > > As you might remember, we agreed on a test day for the master branch on > > Wednesday the 1st October, during our last meeting in Schihol-Rijk with > > some folks. Please feel invited to test master so that we can report to > our > > RM for 4.5 for the current state and he can have a short and quick > journey > > to releasing. > > > > I didn't forget! Just tested by upgrading from 4.4.1 (RC) to 4.5.0 and > that worked, but my KVM agent couldn't connect anymore afterwards: > > 2014-10-01 14:59:08,789 INFO [utils.nio.NioClient] > (Agent-Selector:null) Connecting to cloudstack.XXXX:8250 > 2014-10-01 14:59:08,809 ERROR [utils.nio.NioConnection] > (Agent-Selector:null) Unable to initialize the threads. > java.io.IOException: Connection closed with -1 on reading size. > at com.cloud.utils.nio.Link.doHandshake(Link.java:509) > at com.cloud.utils.nio.NioClient.init(NioClient.java:78) > at com.cloud.utils.nio.NioConnection.run(NioConnection.java:111) > at java.lang.Thread.run(Thread.java:744) > > Any ideas? When I try to telnet to 8250 the connection is closed > immediately by the mgmt server. Nothing in the logs. > > So this is currently preventing me from testing the KVM agents. > > Wido > > > > optimistically yours, > > >
