[StarCluster] !!! ERROR - placement group does not exist (Butson, Christopher)

[Butson, Christopher]

Check the debug log (~/.starcluster/logs/debug.log).
I suspect the requested machine never started -- cc2.8xlarge are in short supply.

This is the text from the debug log around that time. It hadn't occurred to me that this instance might not be available. Is there another way I can check availability before launching starcluster? Thanks.

2013-02-28 19:15:08,934 PID: 17806 config.py:551 - DEBUG - Loading config
2013-02-28 19:15:08,935 PID: 17806 config.py:118 - DEBUG - Loading file: /Users/local/.starcluster/config
2013-02-28 19:15:08,937 PID: 17806 awsutils.py:54 - DEBUG - creating self._conn w/ connection_authenticator kwargs = {'proxy_user': None, 'proxy_pass': None, 'proxy_port': None, 'proxy': None, 'is_secure': True, 'path': '/', 'region': None, 'port': None}
2013-02-28 19:15:09,747 PID: 17806 start.py:176 - INFO - Using default cluster template: smallcluster
2013-02-28 19:15:09,747 PID: 17806 cluster.py:1539 - INFO - Validating cluster template settings...
2013-02-28 19:15:14,924 PID: 17806 cluster.py:1555 - INFO - Cluster template settings are valid
2013-02-28 19:15:14,924 PID: 17806 cluster.py:1427 - INFO - Starting cluster...
2013-02-28 19:15:14,924 PID: 17806 cluster.py:952 - INFO - Launching a 1-node cluster...
2013-02-28 19:15:14,924 PID: 17806 cluster.py:979 - DEBUG - Launching master (ami: ami-4583572c, type: cc2.8xlarge)
2013-02-28 19:15:15,041 PID: 17806 awsutils.py:165 - INFO - Creating security group @sc-butson_cluster...
2013-02-28 19:15:17,257 PID: 17806 awsutils.py:275 - INFO - Creating placement group @sc-butson_cluster...
2013-02-28 19:15:18,631 PID: 17806 cli.py:279 - ERROR - placement group @sc-butson_cluster does not exist





Regards,
Steve

Fri, 1 Mar 2013 01:31:45 +0000
From: "Butson, Christopher" <cbutson at mcw.edu<mailto:cbutson at mcw.edu>>
If I choose the instance "HVM StarCluster ami-4583572c" with cluster size 1
and NODE_INSTANCE_TYPE = cc2.8xlarge then I get the following error message.
Any idea what could be causing this? I don't have this problem if I switch
to the 64 bit AMI with instance type c1.xlarge. Thanks, Chris

_______________________________________________
StarCluster mailing list
StarCluster at mit.edu<mailto:StarCluster at mit.edu>
http://mailman.mit.edu/mailman/listinfo/starcluster