This morning I was unable to start new instances.  I discovered that I
could SSH into the SSVM and the console proxy but not the virtual router.
Something strange was happening so I thought it might be a good time to
gracefully stop all the instances and reboot the hypervisor to see if the
VR would start working again.  I also rebooted the management server (a
separate machine) to have a clean slate.  Now that they've both been
rebooted, the following symptoms exist:

* On the management server, there is no services listening on 9090 or 8250.
* When I run the SSVM health check script, it says NFS is not currently
mounted.
* The management server log is reporting that Zone 1 is not ready to launch
SSVM/CP yet, even though both of those are running.

The NFS server is running just fine.  I can mount it in the management
server with no problems.  I've restarted cloudstack-management and
cloudstack-agent but the problems persist.  The "not ready to launch
SSVM/CP yet" messages sounds like the management server and the hypervisor
are not communicating or some information about the system state is out of
sync.  How can I confirm this?

Reply via email to