PAT not connecting with AWS [closed]

asked 2018-07-09 22:49:33 -0500

pow_skier's avatar

updated 2018-07-18 11:28:04 -0500

After 5 attempts today (7/9) and I had no luck with my PAT connecting to an newly started cluster. On my AWS console I could see active server/workers, but they never connected or intitalized or whatever within my PAT, and I could never start a run.

PAT v2.5.1 and 2.5.1 AMIs with m3.xlarge instances and I tried both 4 and 8 worker configs too.

And although, I've experienced occasional "false starts" times before usually I can restart my PAT run or even my computer and proceed. But today I had no success making the connection. How do I trouble shoot this with PAT/OS when my AWS console shows (and bills) a live connection, but my PAT sits and waits never completing the connections?

Thank you.

edit retag flag offensive reopen merge delete

Closed for the following reason the question is answered, right answer was accepted by pow_skier
close date 2018-08-28 11:25:58.745781


Still no luck. Tried again today. I had luck with v2.5 PAT connecting with AWS. But this doesn't work because I need to use the Prototype Measure (therefore v2.5.1) within my cloud work flow. Please Help!

pow_skier's avatar pow_skier  ( 2018-07-11 09:31:01 -0500 )edit

Can you try the 2.6.0 builds? A number of issues were addressed regarding docker deployment both locally and on AWS.

BrianLBall's avatar BrianLBall  ( 2018-07-31 11:20:26 -0500 )edit

@BrianLBall I just had luck getting v2.5.1 to connect and I am running my workflow. Later today I will try a 2.6 build and get back to you. Thanks.

pow_skier's avatar pow_skier  ( 2018-08-01 11:51:06 -0500 )edit

anything below 2.6.0 will be intermittent as far as startup goes, especially on smaller instances.

BrianLBall's avatar BrianLBall  ( 2018-08-01 11:57:45 -0500 )edit

Maybe it does relate to my system firewall in someway too.

pow_skier's avatar pow_skier  ( 2018-08-30 10:17:44 -0500 )edit