Re: Waiting for SSH to Come Up on All Nodes...
Did you follow this?
starcluster start -o -s 1 -i <INSTANCE-TYPE> -n <BASE-AMI-ID> imagehost
http://star.mit.edu/cluster/docs/0.93.3/manual/create_new_ami.html
On Mon, Apr 27, 2015 at 11:27 AM, Jason Gallant <jgallant_at_msu.edu> wrote:
> Hi All,
>
> I’ve been working so far with StarCluster to great success.
>
> I recently created a AMI based on the ami-3393a45a public image. I
> installed a few executables and then saved the machine as a new AMI. Now
> when I try to start this as a 10-node cluster, the stacluster program
> “hangs” at “Waiting for SSH to come up on all nodes…”.
>
> I can verify that I can ssh into each of the nodes using the “ubuntu”
> login name, however permission is denied for “root”. Looking over previous
> messages, it was suggested to change /etc/cloud/cloud.cfg 'disable_root:
> true'. to ‘false’ and recreating the AMI. I did this, but am still having
> the same issue of “Wating for SSH to come up on all nodes…"
>
> Testing this, it seems that my other AMIs used in other applications seem
> to operate fine. Any ideas on diagnosing this problem?
>
> Best,
> Jason Gallant
>
> —
> Dr. Jason R. Gallant
> Assistant Professor
> Room 38 Natural Sciences
> Department of Zoology
> Michigan State University
> East Lansing, MI 48824
> jgallant_at_msu.edu
> office: 517-884-7756
>
> _______________________________________________
> StarCluster mailing list
> StarCluster_at_mit.edu
> http://mailman.mit.edu/mailman/listinfo/starcluster
>
>
--
Nick Stong, PhD
Bioinformatics Scientist
Celmatix Inc.
54 W. 40th
New York, NY 10018
262-994-4152
www.celmatix.com
This email message and any attachments being sent by Celmatix Inc., are
confidential, and may be privileged. If you are not the intended recipient,
please notify us immediately—by replying to this message—and destroy all
copies of this message and any attachments. Thank you.
Received on Mon Apr 27 2015 - 13:16:23 EDT
This archive was generated by
hypermail 2.3.0.