Last night I used the Amazon console to stop my working instance. Today started
up the instance using amazon console. Waited appropriate time, using new
assigned public ip address and no response. Also did a reboot and no response.
I can ssh to the instance but do not know what to check for
Galaxy Cloudman does not support Stop/Start through the AWS interface, this is
known to cause problems and should be avoided. The persistence design allows
for complete termination and restart -- the issue with your startup zone can be
worked around currently by launching through the AWS
Dannon
Thanks for the update. I was able to power through getting the EC2
instance to start using the cloud man interface in the same zone as the
volume. Will let it run until next week. Amazon was not cooperating and
kept launching instances in the opposite zone that I had the yaml file
pointing
