Hi,
I see this in the logs.
{"com.cloud.agent.api.check.CheckSshAnswer":{"result":false,"details":"Can not
ping System vm r-9-VMdue to:Unable to
connect","wait":0}},{"com.cloud.agent.api.Answer":{"result":false,"details":"Stopped
by previous
failure","wait":0}},{"com.cloud.agent.api.Answer":{"result":false,"details":"Stopped
by previous
failure","wait":0}},{"com.cloud.agent.api.Answer":{"result":false,"details":"Stopped
by previous failure","wait":0}}] }
2013-12-20 15:30:59,455 WARN
[network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-2:job-39 = [
069c2587-3000-45ae-979f-887dc1e99b23 ]) Unable to ssh to the VM: Can not ping
System vm r-9-VMdue to:Unable to connect
This means that the management server is not able to ssh to the router vm. This
can happen if there is a mismatch in the ssh keys used my the management
server and the routerVM. try to destroy the router VMs can recreate them.
If this dose not work try copying the systemvm.iso to the KVM host and
recreate router VM again.
Thanks,
Bharat.
On 21-Dec-2013, at 5:34 am, James Towner
<james.tow...@yahoo.com<mailto:james.tow...@yahoo.com>> wrote:
{"com.cloud.agent.api.check.CheckSshAnswer":{"result":false,"details":"Can not
ping System vm r-9-VMdue to:Unable to
connect","wait":0}},{"com.cloud.agent.api.Answer":{"result":false,"details":"Stopped
by previous
failure","wait":0}},{"com.cloud.agent.api.Answer":{"result":false,"details":"Stopped
by previous
failure","wait":0}},{"com.cloud.agent.api.Answer":{"result":false,"details":"Stopped
by previous failure","wait":0}}] }
