Actually nevermind on that. I think I just wasn't waiting long enough.
On Tue, Jan 10, 2012 at 3:37 PM, mailing list wrote:
> Ok thanks. That makes sense.
>
> Maybe a separate issue but when I do the terminate option from within
> the CloudMan web interface it says it's terminating but nothing
Ok thanks. That makes sense.
Maybe a separate issue but when I do the terminate option from within
the CloudMan web interface it says it's terminating but nothing seems
to happen. I still see the S3 bucket, the volumes, and the instance
continues running.
Thanks again for all the answers today.
In your AWS management console delete the s3 bucket containing the cluster
information. In the s3 viewer, the .clusterName file reflects the name of the
cluster.
You'll probably also want to delete the EBS data volume associated with that
cluster, though electing to keep this won't prevent sta
Yes, I did use the same name. I thought once I terminated everything
would be gone.
So how do I make a "clean start"?
Thanks,
Greg
On Tue, Jan 10, 2012 at 3:08 PM, Dannon Baker wrote:
> It looks like you're trying to restart an existing cluster (same cluster
> name) that previously had galax
It looks like you're trying to restart an existing cluster (same cluster name)
that previously had galaxy included. Is this the case? If so, you'll need to
start it in the same availability zone as the existing volumes.
On Jan 10, 2012, at 3:03 PM, mailing list wrote:
> The page seems to be
The page seems to be loading now but I think I'm getting some weird
behavior on my started instance.
None of the services except SGE started up, and I see this under
cluster status log on the main page:
* 19:57:11 - Retrieved file 'persistent_data.yaml' from bucket
'cm-31bf91*22c1a276
6 matches
Mail list logo
