Are you using custom SSL certificates and domain for your system VMs? Have you deployed HTTPS on your management server? Which version of CloudStack is this?
I believe you can ignore heartbeat related errors. Only thing you need to maintain is time sync between the mgmt nodes. Also, I am not sure about mshost parameter of deploy-databases script. you can try giving other ip..see that works.. Thanks, Praveen On Thu, Feb 12, 2015 at 10:42 AM, Yiping Zhang <[email protected]> wrote: > Hi, Praveen: > > That worked, sort of. Now both CPVM and SSVM are trying to connect to the > correct IP address on my management server, but the connect failed due to > some sort of SSL error, even though I have not used SSL for this CS > instance at all. > > Following error is logged in /var/log/cloud.log file repeatedly: > > 2015-02-12 04:50:58,053 INFO [utils.nio.NioClient] (Agent-Selector:null) > Connecting to 10.0.100.11:8250 > 2015-02-12 04:50:58,060 ERROR [utils.nio.NioConnection] > (Agent-Selector:null) Unable to initialize the threads. > java.io.IOException: SSL: Fail to init SSL! java.io.IOException: > Connection reset by peer > at com.cloud.utils.nio.NioClient.init(NioClient.java:84) > at com.cloud.utils.nio.NioConnection.run(NioConnection.java:108) > at java.lang.Thread.run(Thread.java:701) > > > > Regarding ³host² global setting, if this variable determines which IP > address on mgr to use, then I wonder do I still need to use ³‹mshost <ip>² > option when running cloudstack-setup-databases script ? I am seeing some > errors in catalina.out about cluster heartbeat failures which I have not > seen before. > > Yiping > > > > On 2/11/15, 8:21 PM, "Praveen B" <[email protected]> wrote: > > >Hi Zhang, > > > >"host" parameter in the global settings will decide system VMs to > >communicate to MGMT ip address on port 8250. Since you have two IP > >addresses on management server, CloudStack has picked up your corporate > >network IP address. > > > >As a fix, change the "host" parameter to your lab network IP address and > >destroy system VMs. New system VMs will point to correct mgmt IP. Let me > >know how it goes. > > > >Thanks, > >Praveen > > > >On Thu, Feb 12, 2015 at 5:39 AM, Yiping Zhang <[email protected]> wrote: > > > >> Hi, all: > >> > >> My CS management server has two IP addresses: one IP address on our > >> corporate network (for general access) and one IP address on lab > >>network , > >> which is used at CloudStack¹s management network. > >> > >> When I run cloudstack-setup-database script, I have given ³‹mshost² > >>option > >> with its IP address on lab network. However, when CPVM comes up, the > >> cloud service is not running . Looking at /var/log/cloud.log file on > >>CPVM > >> indicates that it is trying to connect to port 8250 of management > >>server¹s > >> IP address on corporate network instead of the IP address on lab > >>network. > >> On SSVM, its cloud service also tries to connect to port 8250 of the > >>wrong > >> MS IP address > >> > >> How does systemVMs decide which IP address on the management server to > >>use > >> when starting cloud service ? How do I make systemVM¹s to use proper > >> interface on management server ? > >> > >> Thanks > >> > >> Yiping > >> > >
