Dear Sir/Madam, I just started to instantiate a Galaxy instance on the AWS. I have followed your instructions on the following page: http://wiki.g2.bx.psu.edu/CloudMan http://wiki.g2.bx.psu.edu/CloudMan/AWS/GettingStarted At the end of step 2, I faced a problem which resulted in the following error: 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. So, I rebooted the instance and then since the problem was not resolved I terminated the instance and created another instance. I did so a few times. However, it did not help. I have reviewed my AWS credentials and also the master instance (AMI: ami-da58aab3, Name: 861460482541/galaxy-cloudman-2011-03-22). Every thing looks fine. Would you please help me fix this? Regards, Kourosh
Kourosh, My first guess would be a misconfiguration of the security groups or the like -- are you launching the instance using the regular AWS console? If so, it might be worth it to try using Galaxy's Cloud Launch at https://main.g2.bx.psu.edu/cloudlaunch which will help you format any userData correctly and will automatically configure security groups and the like. -Dannon On Sep 25, 2012, at 11:06 AM, "Ravvaz, Kourosh" <ravvaz@gmail.com> wrote:
Dear Sir/Madam,
I just started to instantiate a Galaxy instance on the AWS. I have followed your instructions on the following page:
http://wiki.g2.bx.psu.edu/CloudMan http://wiki.g2.bx.psu.edu/CloudMan/AWS/GettingStarted
At the end of step 2, I faced a problem which resulted in the following error:
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.
So, I rebooted the instance and then since the problem was not resolved I terminated the instance and created another instance. I did so a few times. However, it did not help.
I have reviewed my AWS credentials and also the master instance (AMI: ami-da58aab3, Name: 861460482541/galaxy-cloudman-2011-03-22). Every thing looks fine.
Would you please help me fix this?
Regards,
Kourosh
___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at:
participants (2)
-
Dannon Baker
-
Ravvaz, Kourosh