Thanks for reporting! <https://flyte-org.slack.com...
# flyte-deployments
Shivay Lamba
09/05/2022, 6:21 AMThanks for reporting! https://flyte-org.slack.com/archives/CNMKCU6FR/p1661980868829449
There was an error which was causing the connection error, but with the latest version, this should be fixed. Can you let us know the version of flyte-ctl you are running?
k
KS Tarun
09/05/2022, 7:56 AMI'm using 1.2.0b0
KS Tarun
09/06/2022, 5:55 AMHi All, I'm still getting this error even when trying to setup flyte on an EC2 instance :
Error: Get "https://127.0.0.1:30086/api/v1/nodes": dial tcp 127.0.0.130086 connect: connection refused
{"json":{},"level":"error","msg":"Get \"https://127.0.0.1:30086/api/v1/nodes\": dial tcp 127.0.0.130086 connect: connection refused","ts":"2022-09-06T054822Z"}
And I've tried it with both the 1.1.0 & 1.2.0b0 versions.
s
Shivay Lamba
09/06/2022, 5:57 AM@Samhita Alla could there any other specific reason related to configuration of cluster information?
s
Samhita Alla
09/06/2022, 6:31 AM
flytectl demo start --version=v1.1.0Samhita Alla
09/06/2022, 7:07 AM
Oh, but it should work the first time as well.
k
KS Tarun
09/06/2022, 7:08 AMYes, you're right. I'm not sure why it isn't working the first time.
s
Samhita Alla
09/06/2022, 7:09 AM
You’ll need to install the requirements locally first. Can you run
pip install -r requirements.txtp
Prafulla Mahindrakar
09/06/2022, 9:11 AM@KS Tarun next time it happen can you check the o/p of docker ps and check the exit status of flyte container . Also you can do an inspect on the container on why it failed.
k
KS Tarun
09/07/2022, 4:18 AM@Prafulla Mahindrakar Sure, I'll check it. Thanks
161 Views