Hi Martin, Could you please confirm that you selected galaxyweb and default security groups because the only time we saw this error was in absence of correct group selection and/or configuration?

We'll look at it again. Thanks for the understanding.

On May 18, 2010, at 6:00 PM, Martin Paradesi <p.martin.samuel.rao@gmail.com

wrote:

Hello Galaxy team,

I tried to setup Galaxy on the cloud with my Amazon Web Services  

account but I'm getting the following message:

"The Galaxy Cloud Console is not running. It may take a few moments to start after your EC2 instance has become available, or you may not have provided the correct user data when configuring and launching the instance from the AWS Management Console. Please refer to the documentation for more information. If you did enter the correct user data, you may be able to reboot this EC2 instance to solve the problem." even after running the instance for an hour.

I'm using AMI ID: ami-ed03ed84 and have set appropriate security groups, key pair and user data. I have also rebooted the instance few times. I have attached a snapshot of the server log for your perusal.

init: console-setup main process (79) terminated with status 1 %Ginit: plymouth main process (61) killed by SEGV signal init: plymouth-splash main process (238) terminated with status 2 Generating locales... en_US.UTF-8... up-to-date Generation complete. mountall: Disconnected from Plymouth mountall: Skipping mounting /mnt since Plymouth is not available init: plymouth-log main process (392) terminated with status 1 Generating public/private rsa key pair. Your identification has been saved in /etc/ssh/ssh_host_rsa_key. Your public key has been saved in /etc/ssh/ssh_host_rsa_key.pub. The key fingerprint is: <snip></snip> The key's randomart image is: Generating public/private dsa key pair. Your identification has been saved in /etc/ssh/ssh_host_dsa_key. Your public key has been saved in /etc/ssh/ssh_host_dsa_key.pub. The key fingerprint is: <snip></snip> The key's randomart image is: ec2: ec2: ############################################################# ec2: -----BEGIN SSH HOST KEY FINGERPRINTS----- ec2: -----END SSH HOST KEY FINGERPRINTS----- ec2: #############################################################

• Starting AppArmor profiles [80G [74G[ OK ]
• Exporting directories for NFS kernel daemon... [80G exportfs: Warning: /mnt/galaxyTools does not exist

exportfs: Warning: /mnt/galaxyIndices does not exist exportfs: Warning: /mnt/galaxyData does not exist

[74G[ OK ]

• Starting NFS kernel daemon [80G [74G[ OK ]

Starting PostgreSQL 8.4: waiting for server to start...sh: cannot create /mnt/galaxyData/ pgsql/data/pg_log/startup.log: Directory nonexistent ............................................................could not start server PostgreSQL 8.4 did not start in a timely fashion, please see /mnt/ galaxyData/pgsql/data/pg_log/startup.log for details Starting rabbitmq-server: SUCCESS rabbitmq-server. landscape-client is not configured, please run landscape-config. Unzipping file ec2autorun.zip

Ubuntu lucid (development branch) ip-10-245-189-171 tty1

ip-10-245-189-171 login:

Can you please let me know what could be going wrong?

Thanks, Martin _______________________________________________ galaxy-dev mailing list galaxy-dev@lists.bx.psu.edu http://lists.bx.psu.edu/listinfo/galaxy-dev

Hi Dannon,

I selected both the security groups - default and galaxyweb (ssh, http and port 42284).

Thanks, Martin

On Wed, May 19, 2010 at 12:33 AM, Dannon Baker dannonbaker@me.com wrote:

Hi Martin, Could you please confirm that you selected galaxyweb and default security groups because the only time we saw this error was in absence of correct group selection and/or configuration?

We'll look at it again. Thanks for the understanding.

On May 18, 2010, at 6:00 PM, Martin Paradesi < p.martin.samuel.rao@gmail.com> wrote:

Hello Galaxy team,

...

I tried to setup Galaxy on the cloud with my Amazon Web Services account but I'm getting the following message:

"The Galaxy Cloud Console is not running. It may take a few moments to start after your EC2 instance has become available, or you may not have provided the correct user data when configuring and launching the instance from the AWS Management Console. Please refer to the documentation for more information. If you did enter the correct user data, you may be able to reboot this EC2 instance to solve the problem." even after running the instance for an hour.

I'm using AMI ID: ami-ed03ed84 and have set appropriate security groups, key pair and user data. I have also rebooted the instance few times. I have attached a snapshot of the server log for your perusal.

init: console-setup main process (79) terminated with status 1 %Ginit: plymouth main process (61) killed by SEGV signal init: plymouth-splash main process (238) terminated with status 2 Generating locales... en_US.UTF-8... up-to-date Generation complete. mountall: Disconnected from Plymouth mountall: Skipping mounting /mnt since Plymouth is not available init: plymouth-log main process (392) terminated with status 1 Generating public/private rsa key pair. Your identification has been saved in /etc/ssh/ssh_host_rsa_key. Your public key has been saved in /etc/ssh/ssh_host_rsa_key.pub. The key fingerprint is: <snip></snip> The key's randomart image is: Generating public/private dsa key pair. Your identification has been saved in /etc/ssh/ssh_host_dsa_key. Your public key has been saved in /etc/ssh/ssh_host_dsa_key.pub. The key fingerprint is: <snip></snip> The key's randomart image is: ec2: ec2: ############################################################# ec2: -----BEGIN SSH HOST KEY FINGERPRINTS----- ec2: -----END SSH HOST KEY FINGERPRINTS----- ec2: #############################################################

• Starting AppArmor profiles [80G [74G[ OK ]
• Exporting directories for NFS kernel daemon... [80G exportfs: Warning: /mnt/galaxyTools does not exist

exportfs: Warning: /mnt/galaxyIndices does not exist exportfs: Warning: /mnt/galaxyData does not exist

[74G[ OK ]

• Starting NFS kernel daemon [80G [74G[ OK ]

Starting PostgreSQL 8.4: waiting for server to start...sh: cannot create /mnt/galaxyData/pgsql/data/pg_log/startup.log: Directory nonexistent ............................................................could not start server PostgreSQL 8.4 did not start in a timely fashion, please see /mnt/galaxyData/pgsql/data/pg_log/startup.log for details Starting rabbitmq-server: SUCCESS rabbitmq-server. landscape-client is not configured, please run landscape-config. Unzipping file ec2autorun.zip

Ubuntu lucid (development branch) ip-10-245-189-171 tty1

ip-10-245-189-171 login:

Can you please let me know what could be going wrong?

Thanks, Martin _______________________________________________ galaxy-dev mailing list galaxy-dev@lists.bx.psu.edu http://lists.bx.psu.edu/listinfo/galaxy-dev

Dannon,

It works now.

Thanks, Martin

On Wed, May 19, 2010 at 11:23 AM, Dannon Baker dannonbaker@me.com wrote:

Martin and Dennis,

Thanks for bringing this to our attention, and sorry for the inconvenience. The problem has been identified and fixed. Thanks for trying out Galaxy on the Cloud, it should work for you this time.

-Dannon

On May 19, 2010, at 8:33 AM, Martin Paradesi wrote:

...

Hi Dannon,

I selected both the security groups - default and galaxyweb (ssh,

http and port 42284).

...

Thanks, Martin

On Wed, May 19, 2010 at 12:33 AM, Dannon Baker dannonbaker@me.com

wrote:

...

Hi Martin, Could you please confirm that you selected galaxyweb and default security

groups because the only time we saw this error was in absence of correct group selection and/or configuration?

...

We'll look at it again. Thanks for the understanding.

On May 18, 2010, at 6:00 PM, Martin Paradesi <

p.martin.samuel.rao@gmail.com> wrote:

...

Hello Galaxy team,

I tried to setup Galaxy on the cloud with my Amazon Web Services

account but I'm getting the following message:

...

"The Galaxy Cloud Console is not running. It may take a few moments to

start after your EC2 instance has become available, or you may not have provided the correct user data when configuring and launching the instance from the AWS Management Console. Please refer to the documentation for more information. If you did enter the correct user data, you may be able to reboot this EC2 instance to solve the problem." even after running the instance for an hour.

...

I'm using AMI ID: ami-ed03ed84 and have set appropriate security

groups, key pair and user data. I have also rebooted the instance few times. I have attached a snapshot of the server log for your perusal.

...

init: console-setup main process (79) terminated with status 1 %Ginit: plymouth main process (61) killed by SEGV signal init: plymouth-splash main process (238) terminated with status 2 Generating locales... en_US.UTF-8... up-to-date Generation complete. mountall: Disconnected from Plymouth mountall: Skipping mounting /mnt since Plymouth is not available init: plymouth-log main process (392) terminated with status 1 Generating public/private rsa key pair. Your identification has been saved in /etc/ssh/ssh_host_rsa_key. Your public key has been saved in /etc/ssh/ssh_host_rsa_key.pub. The key fingerprint is: <snip></snip> The key's randomart image is: Generating public/private dsa key pair. Your identification has been saved in /etc/ssh/ssh_host_dsa_key. Your public key has been saved in /etc/ssh/ssh_host_dsa_key.pub. The key fingerprint is: <snip></snip> The key's randomart image is: ec2: ec2: ############################################################# ec2: -----BEGIN SSH HOST KEY FINGERPRINTS----- ec2: -----END SSH HOST KEY FINGERPRINTS----- ec2: #############################################################

• Starting AppArmor profiles [80G [74G[ OK ]
• Exporting directories for NFS kernel daemon... [80G exportfs: Warning: /mnt/galaxyTools does not exist

exportfs: Warning: /mnt/galaxyIndices does not exist exportfs: Warning: /mnt/galaxyData does not exist

[74G[ OK ]

• Starting NFS kernel daemon [80G [74G[ OK ]

Starting PostgreSQL 8.4: waiting for server to start...sh: cannot create

/mnt/galaxyData/pgsql/data/pg_log/startup.log: Directory nonexistent

...

............................................................could not

start server

...

PostgreSQL 8.4 did not start in a timely fashion, please see

/mnt/galaxyData/pgsql/data/pg_log/startup.log for details

...

Starting rabbitmq-server: SUCCESS rabbitmq-server. landscape-client is not configured, please run landscape-config. Unzipping file ec2autorun.zip

Ubuntu lucid (development branch) ip-10-245-189-171 tty1

ip-10-245-189-171 login:

Can you please let me know what could be going wrong?

Thanks, Martin _______________________________________________ galaxy-dev mailing list galaxy-dev@lists.bx.psu.edu http://lists.bx.psu.edu/listinfo/galaxy-dev