Re: newbie problems

From: Justin Riley <no email>
Date: Sun, 20 May 2012 12:58:39 -0400

You can also use StarCluster to list your volumes:

$ starcluster listvolumes

If you only want details on a single volume:

$ starcluster listvolumes -v vol-999999

You can also filter volumes by status, size, zone, snapshot id, etc.
Pass --help to the listvolumes command for more details.

HTH,

~Justin

On Sun, May 20, 2012 at 11:34:54AM -0400, Rayson Ho wrote:
> You are attaching an external EBS volume that is in us-east-1c, so you
> can't have your instances in us-east-1a.
>
> If you are not sure which zone your EBS vol is in, log onto the AWS
> Management Console, and go to Elastic Block Store -> Volumes. Then
> click on the volume you want to attach to the cluster, and zone will
> be displayed together with other information related to the volume.
>
>
> Also, see: http://aws.amazon.com/ebs/
>
> "Amazon EBS volumes are placed in a specific Availability Zone, and
> can then be attached to instances also in that same Availability
> Zone."
>
> Rayson
>
> ================================
> Open Grid Scheduler / Grid Engine
> http://gridscheduler.sourceforge.net/
>
> Scalable Grid Engine Support Program
> http://www.scalablelogic.com/
>
>
> On Sun, May 20, 2012 at 4:21 AM, Manal Helal <manal.helal_at_gmail.com> wrote:
> > to be comprehensive:
> >
> > when I change the aws info configuration:
> >
> > AWS_REGION_NAME = us-east-1a
> > #AWS_REGION_HOST = ec2.us-east-1.amazonaws.com (tried changing this and had
> > errors)
> >
> > and then in the cluster configuration:
> >
> > AVAILABILITY_ZONE = us-east-1a
> >
> > I get these errors
> >
> > !!! ERROR - Cluster settings are not valid:
> > !!! ERROR - availability_zone setting 'us-east-1a' does not match the
> > !!! ERROR - common volume zone 'us-east-1c'
> >
> >
> > I practically tried all possible variations between these three arguments,
> > and I get the above error and the other error without anyone connecting
> > since three days now. While the same configuration file and using the
> > default region, or us-east-1 only, and I think us-east-1c also was
> > successful in connecting before,
> >
> > thanks again for your support,
> >
> > Manal
> >
> > On 20 May 2012 16:28, Manal Helal <manal.helal_at_gmail.com> wrote:
> >>
> >> Hi Rayson,
> >>
> >> Thanks again. Now even away from bidding, and using the same configuration
> >> file that connected successfully 3 days ago,
> >>
> >> I am consistently now getting this error:
> >>
> >> !!! ERROR - Unsupported: Your requested instance type (cg1.4xlarge) is not
> >> supported in your requested Availability Zone (us-east-1c). Please retry
> >> your request by not specifying an Availability Zone or choosing us-east-1a.
> >>
> >>
> >> I do as it says, and remove any region specifications, or specify the
> >> "us-east-1a" region at says, and it still keep coming back with the same
> >> error,  3 days now without successful connection with bidding and without. I
> >> am not sure how to solve that
> >>
> >> I appreciate your support very much.
> >>
> >
>
>
>
> --
> ==================================================
> Open Grid Scheduler - The Official Open Source Grid Engine
> http://gridscheduler.sourceforge.net/
>
> _______________________________________________
> StarCluster mailing list
> StarCluster_at_mit.edu
> http://mailman.mit.edu/mailman/listinfo/starcluster



Received on Sun May 20 2012 - 12:58:41 EDT