This message was deleted.
# ask-the-community
s
This message was deleted.
k
i think you do not have the right endpoint configured
please configure the right endpoint in the ~/.flyte/config.yaml
šŸ‘ 1
a
i also get that error:
Copy code
<_InactiveRpcError of RPC that terminated with:\n\tstatus = StatusCode.UNAVAILABLE\n\tdetails = \"failed to connect to all addresses\"\n\tdebug_error_string = \"
etcā€¦. even when the script has [at least initially] connected to the right endpoint. Not sure exactly the source of flakiness. For @Taeef Najib, I agree ensuring config is correct is the good place to start.
šŸ‘ 1
n
can you
cat ~/.flyte/config.yaml
and copy-paste it here?
šŸ‘ 1
a
To hijack Taeefā€™s thread ā€¦ https://github.com/flyteorg/flyte/actions/runs/2678784708 ā€¦ see the artifact ā€˜config.yamlā€™ ā€¦ this one failed ( after a short bit ). When I ran fewer tests: https://github.com/flyteorg/flyte/runs/7363730667 ( it was successful ).
my current thinking is that it is also possible to get that error from resource constraints-or-maybe-misbehaving-workflows/executions [ havenā€™t isolated specific issue ], but doesnā€™t seem to be the
config.yaml
y
yeah the error is a generic connection error, can happen for a number of reasons
the most common reason i feel like weā€™ve seen is the wrong address, or not adding
dns:///
in front of the domain, or using/not using insecure
a
sure ā€¦ but wonder what cases we could put messaging in place to debug that ā€” ex: when first parsing the config file ex: ā€œERROR: the proper format of
endpoint
field is ā€™dns://<DNS_OF_SERVICE> ā€¦ ā€˜dns://ā€™ is missingā€ā€¦. [ but Iā€™m not sure if you could address with just IP, and in that case, dns:// might not be required ]. Or other things like thatā€¦.
I think tests will start in a couple minutesā€¦. Will see whether they fail [ I believe VERY likely to fail ]. https://github.com/flyteorg/flyte/runs/7365263197?check_suite_focus=true
t
Thank you all for all the suggestions. However, I might have made some mistake in installing flyte and getting it to work on my mac. I tried a Windows laptop to make sure that itā€™s not the hardware problem. On windows, I get the same error. Iā€™d like to mention that I didnā€™t install flytectl on my machines. I tried to install it on windows with the following command: First
bash
and then
curl -sL <https://ctl.flyte.org/install>
but no luck. I see a file called
flytectl
in the bin folder. But that is not editable or readable on vs code. I am very inexperienced into this, but how do I find
config.yaml
for flyte on my windows machine? or how do I correctly install it using cmd (on vs code)?
a
@Taeef Najib flytectl likely would be a binary, so I wouldnā€™t expect it to be editable/readable with VSCode.
šŸ‘ 1
unfortunately, I canā€™t help you with windows šŸ˜•, but maybe someone else can
šŸ‘ 1
k
It is a golang binary and should work on windows, but I don't have a windows machine
šŸ‘ 1
t
Under the bin folder, thereā€™s just one binary file called flytectl. Am I not supposed to have a folder where I can find config.yaml? @austin and @Ketan (kumare3)
k
You have to do flytectl config init - check the docs https://docs.flyte.org/projects/flytectl/en/latest/index.html
šŸ‘ 1
t
Thanks @Ketan (kumare3) šŸ™
a
@Taeef Najib ā€” those docs solved things for you? Anything else that could be better highlighted/documented?
šŸ‘ 1
t
@austin even after installing flytectl using my vs code terminal (cmd) I canā€™t upgrade or check the version of flytectl. Under the bin folder, I can see the flytectl file, but terminal returns this error:
Copy code
'flytectl' is not recognized as an internal or external command
Thatā€™s where Iā€™m stuck. Do you have any suggestions? šŸ˜ž When I use
Copy code
curl -sL <https://ctl.flyte.org/install> | bash
I get this:
Copy code
flyteorg/flytectl info checking GitHub for latest tag
flyteorg/flytectl info found version: 0.6.4 for v0.6.4/Linux/x86_64
flyteorg/flytectl info installed ./bin/flytectl
181 Views