This sounds like the availability zone issue. I am assuming you are restarting the same cluster (i.e., using the same name) and the instance that gets created may be created in a zone different from the one that the volume from the previous instantiation of the cluster was in. biocloudcentral does not know which zone your cluster was created in previously so it cannot request an instance in that zone. Obviously, this is a limitation of service and, thus far, we are mostly recommending it be used to start a cluster only the very first time. After the cluster creation, we recommend using the AWS console (which is easier to get going now because all the security group/key pair issues have been resolved).

On Tue, Jan 24, 2012 at 2:39 PM, mailing list <margeemail@gmail.com> wrote:

Hi guys,

For the past two days when I try to launch my CloudMan instance using
http://biocloudcentral.herokuapp.com the first time I see an instance
get up and running, but it doesn't mount my galaxyData volume and I
can't get to the webpage <public DNS>/cloud. The webpage just says
"Unable to connect. Firefox can't establish a connection to the server
at ...".

If I terminate the instance and relaunch through BioCloudCentral it
seems to then start up fine.

Any ideas? Is there any more information I can provide to help?

Thanks,

Greg
___________________________________________________________
The Galaxy User list should be used for the discussion of
Galaxy analysis and other features on the public server
at usegalaxy.org. Please keep all replies on the list by
using "reply all" in your mail client. For discussion of
local Galaxy instances and the Galaxy source code, please
use the Galaxy Development list:

http://lists.bx.psu.edu/listinfo/galaxy-dev

To manage your subscriptions to this and other Galaxy lists,
please use the interface at:

http://lists.bx.psu.edu/