Hi Greg,

On Wednesday, December 21, 2011, mailing list wrote:

Ok I got past that part. I hadn't applied my rules :-(.

Glad to hear it's working now though.

Now when I go to the public DNS it prompts me for a username and
password but it's not accepting the password I entered in the user
data. Any idea what went wrong?

The username is not necessary, just the password. Did you download the ssh private key when you created it in the AWS console? You can use it to connect to the instance terminal and make confirm the password to use within the browser. If you connect to the instance (via ssh -i <key file> ubuntu@<instance public DNS>) you can execute following command and check you password:

cat /mnt/cm/userData.yaml

The value under the 'password' field is your password.

Note that the password cannot contain any spaces and is case sensitive.

Enis

Thanks again,

Greg

On Mon, Dec 19, 2011 at 2:24 PM, mailing list <margeemail@gmail.com> wrote:
> Hi guys,
>
> It looks like my security group rules didn't get saved. I'm going to
> try again and report back.
>
> I actually asked this question on Biostar too. I thought my email
> didn't make it to the user group.
>
> It probably makes sense to consolidate in one place so I'm continuing
> the updates over there:
> http://biostar.stackexchange.com/questions/15554/galaxy-cloudman-cant-get-an-instance-started-the-connection-has-timed-out
>
> -Greg
>
>
>
> On Sat, Dec 17, 2011 at 3:36 AM, Enis Afgan <eafgan@emory.edu> wrote:
>> Hi Greg,
>> Sorry to hear you're having trouble.
>> Can you please confirm that you followed the step for creating a security
>> group on the wiki and opened all the specified ports?
>>
>> Enis
>>
>> On Fri, Dec 16, 2011 at 7:58 PM, mailing list <margeemail@gmail.com> wrote:
>>>
>>> Hi Everyone,
>>>
>>> I'm trying to set up Cloud man.
>>>
>>> I believe I followed the instructions listed here to a T:
>>> http://wiki.g2.bx.psu.edu/Admin/Cloud
>>>
>>> After launching the instance I even waited 20 minutes before trying to
>>> access the public DNS
>>> ec2-xxx-xx-xx-xx.compute-1.amazonaws.com/cloud, but my browser just says:
>>>
>>> The connection has timed out
>>>
>>> The server at ec2-xxx-xx-xx-xx.compute-1.amazonaws.com is taking too
>>> long to respond.
>>>
>>> Any ideas what I should check? I'm stuck. What information would be
>>> useful?
>>>
>>> Info:
>>>
>>> Zone is us-east-1a
>>> Type is m1.large
>>> root devide is ebs
>>> AMI Name: galaxy-cloudman-2011-03-22
>>> Region is US East (Virginia)
>>>
>>> I used this format for user data:
>>>
>>> cluster_name: <DESIRED CLUSTER NAME>
>>> password: <DESIRED Galaxy CloudMan WEB UI PASSWORD>
>>> access_key: <YOUR AWS ACCESS KEY>
>>> secret_key: <YOUR AWS SECRET KEY>
>>>
>>> However this screenshot shows a pipe delimited deal? Maybe I should try
>>> that?
>>>
>>> http://userwww.service.emory.edu/~eafgan/content/galaxy_cloud/AWSconsole-4.jpg
>>>
>>>
>>> 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/
>>
>>