Hi Julia, On Tue, Apr 24, 2012 at 7:54 PM, Hui Zhao <zh...@cbio.mskcc.org> wrote: > Hi, > I tried to recreate a security group and still have the same error. Attached > is the screen shot I have for the security group. I was able to launch the > galaxy instance last year without any problem. Not sure what had changed, Can > you tell if there is anything wrong in the security group configuration?
Did you click Apply Rule Changes when you finished adding rules? Other than that, I'm not sure what the problem is, but I have not used cloudman before. I followed the instructions and it works for me. Dan > Thanks, > Julia > > > > On Apr 24, 2012, at 9:01 PM, Dan Tenenbaum wrote: > >> On Tue, Apr 24, 2012 at 9:16 AM, Hui Zhao <zh...@cbio.mskcc.org> wrote: >>> Hi, >>> This is Julia from Memorial SLoan-Kettering Cancer Center. I've been using >>> the galaxy Cloudman instance last year and it worked fine. But today when I >>> tried to launch instance galaxy-cloudman-2011-03-22(ami-da58aab3). After the >>> instance was running, it gave me "tcp_error: A communication error occurred: >>> "Connection refused". Any ideas? >>> >> >> Sounds like maybe a security group problem. Did you set up your >> security group as described here: >> http://wiki.g2.bx.psu.edu/Admin/Cloud >> >> Search for "Add Inbound Rules". >> Dan >> >>> Thanks a lot, >>> Julia >>> >>> >>> >>> >>> ___________________________________________________________ >>> 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: >>> >>> http://lists.bx.psu.edu/ > > ___________________________________________________________ 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: http://lists.bx.psu.edu/
