Mostly  its the problem with ssk keys(if it not matched with MS  keys then it 
failed with ssh connection errors) ,remove the systemvm iso file from systemvm 
folder  exits in your secondary storage  path and restart the management 
server.It will copy the new systemvm iso file  into systemvm folder. 




Regards
Sadhu









-----Original Message-----
From: Rajesh Battala [mailto:rajesh.batt...@citrix.com] 
Sent: Monday, February 15, 2016 11:12 AM
To: users@cloudstack.apache.org
Subject: RE: CheckSshCommand) Trying to connect to VR

Hi, 
Were you able to login to ssvm/cpvm via cloud secret key?
Looks like the pub/private key using by mgmt. server is invalid. 
If the first step is not success then, its keys issues as CS uses private key 
to login to VR to configure the interfaces and other operations. 
Check whether the pub key in the VR is matching with the pub key in mgmt 
server. 

Thanks
Rajesh Battala

-----Original Message-----
From: Cristian Ciobanu [mailto:cristian.c@istream.today] 
Sent: Thursday, February 11, 2016 1:51 AM
To: users@cloudstack.apache.org
Subject: cmd: CheckSshCommand) Trying to connect to VR

Hello,

     I reinstalled again, again and so on, but each time i get new issue.  
right now i have this issue for virtual router :
2016-02-10 15:05:41,254 INFO  [c.c.h.v.r.VmwareResource] 
(DirectAgent-197:ctx-45356303 nsxxxxx.ip-19x-9x-xxx.net, job-64/job-66, cmd: 
CheckSshCommand) Could not connect to 1xx.xx.1x.2xx due to 
java.net.ConnectException: Connection timed out

looks like is not able to connect via SSH, but i'm not sure why because i'm 
able to ping the virtual router IP from management console.

SSVM is UP, and running ( storage mounted, and default templates was downloaded 
successfully ) CPVM IS UP, and running  ( also i tested console and works )

I have installed CloudStack 4.6 with basic network using VMware 5.5 for 
hypervisor 


Can someone confirm if exist an stable version for VMware ? ( because on any 
version of CS i found some issue, also different issue )  CS 4.52 with VMware 
5.5 was ok for 3 days, after some errors occurred 

Thank you!

Regards,
Cristian

Reply via email to