cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Remi Bergsma (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-8920) KVM agent cannot communicate with server on port 8250
Date Tue, 29 Sep 2015 12:44:04 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-8920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14935103#comment-14935103
] 

Remi Bergsma commented on CLOUDSTACK-8920:
------------------------------------------

This works fine in my environment. Are you able to telnet to the management server over port
8250?

Set the pro to critical, as this is not a blocker for release.

> KVM agent cannot communicate with server on port 8250
> -----------------------------------------------------
>
>                 Key: CLOUDSTACK-8920
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8920
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Install and Setup
>    Affects Versions: 4.5.2
>         Environment: CentOS 6.7, OpenJDK 1.7.0
>            Reporter: Noel D. Kendall
>
> Attempting to add a KVM host, the management server is able to reach the target host
via SSH and successfully changes agent.properties, and restarts the agent process. All that
works fine. Zone, Pod and Cluster are configured successfully.
> Problem is occurring on the agent when attempting to contact the management server on
port 8250. Getting an ERROR logged, unable to initialize the threads, with an IOException
-1 connection closed with -1 on reading size.
> This sounds suspiciously like an SSL client is attempting to connect to a non-SSL server.
For the life of me, I cannot see how this is configured or misconfigured.
> I have created SSL certificates for the proxies, and successfully uploaded these, following
the documentation. Not sure this is related in any way or not.
> Have turned on full debugging log output in log4j, not seeing any elaboration on the
underlying cause of the problem.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message