https://flyte.org logo
Join Slack
Powered by
Dear community, I get the following error on debia...
# flyte-support
r
Dear community, I get the following error on debian 12, what could I do? >>flytectl demo start 🧑‍🏭 Bootstrapping a brand new Flyte cluster... 🔨 🔧 Error: Malformed version: flytectl/v0.8.20 {"json":{},"level":"error","msg":"Malformed version: flytectl/v0.8.20","ts":"2024-05-16T161316+02:00"} MY STEPS, ONE BY ONE: pip install -U flytekit pip install flytekitplugins-envd curl -sL https://ctl.flyte.org/install | sudo bash -s -- -b /usr/local/bin export FLYTECTL_CONFIG=~/.flyte/config-sandbox.yaml sudo systemctl start docker flytectl demo start I have tried to uninstall and go over again. I get the same error. Many thanks.
a
could you try upgrading your 
flytectl
version? I just had and fixed the same issue
r
Thanks for reading my post. However, it seems there are not coming changes. Execution below: (flyte_env) root@gdg-test-influx:/home/dg/flyte_tests# flytectl upgrade You already have the latest version of Flytectl
a
looks like you're on Linux what about
Copy code
curl -sL <https://ctl.flyte.org/install> | sudo bash -s -- -b /usr/local/bin v0.8.20
r
Copy code
(flyte_env) root@gdg-test-influx:/home/dg/flyte_tests# curl -sL <https://ctl.flyte.org/install> | sudo bash -s -- -b /usr/local/bin v0.8.20
flyteorg/flytectl info checking GitHub for tag 'v0.8.20'
flyteorg/flytectl crit unable to find 'v0.8.20' - use 'latest' or see <https://github.com/flyteorg/flytectl/releases> for details
(flyte_env) root@gdg-test-influx:/home/dg/flyte_tests# curl -sL <https://ctl.flyte.org/install> | sudo bash -s -- -b /usr/local/bin latest
flyteorg/flytectl info checking GitHub for tag 'latest'
flyteorg/flytectl info found version: 0.8.18 for v0.8.18/Linux/x86_64
flyteorg/flytectl info installed /usr/local/bin/flytectl
(flyte_env) root@gdg-test-influx:/home/dg/flyte_tests# flytectl upgrade
You already have the latest version of Flytectl
(flyte_env) root@gdg-test-influx:/home/dg/flyte_tests# flytectl demo start
:factory_worker: Bootstrapping a brand new Flyte cluster... :hammer: :wrench:
Error: Malformed version: flytectl/v0.8.20
{"json":{},"level":"error","msg":"Malformed version: flytectl/v0.8.20","ts":"2024-05-16T17:27:42+02:00"}
(flyte_env) root@gdg-test-influx:/home/dg/flyte_tests#
thanks @average-finland-92144, but it seems to stay on the same tag
a
flytectl demo start --version v1.12.0
can you try that one pls?
🔧 1
r
@average-finland-92144, thanks for your quick replies, Let me explain, I have run this execution 4 times: 1st, I get the error: Error: Get "https://127.0.0.1:6443/api/v1/nodes": dial tcp 127.0.0.16443 connect: connection refused {"json":{},"level":"error","msg":"Get \"https://127.0.0.1:6443/api/v1/nodes\": dial tcp 127.0.0.16443 connect: connection refused","ts":"2024-05-16T173449+02:00"} 2nd, OK, but I cannot accéss on the terminal: http://localhost:30080/console 3th, same error as 1st 4th, same case as 2nd. I am not sure if it is 'my problem' or not. Probably it is my issue. However, yesterday in another environment, in the same virtual machine, I could get access to http://IP:30080/console
a
Ok, but were you able to create the demo cluster?
🎉 1
r
yes!
a
cool, ok what changed from 1st to 2nd error?
r
I have just reexecuted the line that you suggested.
a
can you check the status of the cluster? the `create`command needs to be run only once 
flytectl demo status
👍 1
r
Copy code
(flyte_env) root@gdg-test-influx:/home/dg/flyte_tests# flytectl demo status
Flyte local sandbox container image [<http://cr.flyte.org/flyteorg/flyte-sandbox-bundled:sha-bd3ed0d2684bddbc8fad1c26d4bc39a86e91077f|cr.flyte.org/flyteorg/flyte-sandbox-bundled:sha-bd3ed0d2684bddbc8fad1c26d4bc39a86e91077f>] with status [Exited (137) 15 minutes ago] is in state [exited]
@average-finland-92144, ahora me funciona como esperaría. No soy consciente de haber cambiado nada. Simplemente he vuelto a ejecutar por Nvez la ejecución que tu has propuesto: 
flytectl demo start --version v1.12.0
Muchas gracias!
a
me alegra Clara! Si tienes otro inconveniente, haznos saber!
r
@average-finland-92144, I am not sure if it is my fault, or not, but my cluster exits from time to time. I am just writting it down here in case it is a general behaviour. Thanks in any case. 
(flyte_env) root@gdg-test-influx:/home/dg/flyte_tests_v2/test7# flytectl demo status
Flyte local sandbox container image [cr.flyte.org/flyteorg/flyte-sandbox-bundled:sha-bd3ed0d2684bddbc8fad1c26d4bc39a86e91077f] with status [Exited (137) About a minute ago] is in state [exited]
a
can you check if there is maybe some resource contention in your Docker daemon? Is this Docker desktop or?
r
Copy code
(flyte_env) root@gdg-test-influx:/home/dg/flyte_tests_v2/test7# docker stats
CONTAINER ID   NAME            CPU %     MEM USAGE / LIMIT    MEM %     NET I/O          BLOCK I/O         PIDS
8961b4cd69c5   flyte-sandbox   3.82%     1.01GiB / 3.823GiB   26.43%    738MB / 1.88MB   4.52GB / 5.69GB   229
CONTAINER ID   NAME            CPU %     MEM USAGE / LIMIT     MEM %     NET I/O          BLOCK I/O         PIDS
8961b4cd69c5   flyte-sandbox   13.61%    1.004GiB / 3.823GiB   26.26%    738MB / 1.88MB   4.52GB / 5.69GB   229
CONTAINER ID   NAME            CPU %     MEM USAGE / LIMIT     MEM %     NET I/O          BLOCK I/O         PIDS
8961b4cd69c5   flyte-sandbox   13.61%    1.004GiB / 3.823GiB   26.26%    738MB / 1.88MB   4.52GB / 5.69GB   229
CONTAINER ID   NAME            CPU %     MEM USAGE / LIMIT     MEM %     NET I/O          BLOCK I/O         PIDS
8961b4cd69c5   flyte-sandbox   9.87%     1.004GiB / 3.823GiB   26.26%    738MB / 1.88MB   4.52GB / 5.69GB   229
uff, same container, running along? too many 'demo starts' maybe....
a
yep
flytectl demo teardown
usually deletes the container
run it once and wait a bit to see
r
@average-finland-92144, thanks for the continuous help. Dinner-time here, tomorrow I will let you know how it proceeds. Many thanks again!
🍽️ 1
👍🏽 1
Good morning @average-finland-92144, what happens is that I cannot make more than 1 execution without tearing appart the demo cluster and building it up again. After one execution I get:
> 
flytectl demo status
INFO[0000] [0] Couldn't find a config file []. Relying on env vars and pflags. Flyte local sandbox container image [cr.flyte.org/flyteorg/flyte-sandbox-bundled:sha-bd3ed0d2684bddbc8fad1c26d4bc39a86e91077f] with status [Exited (137) About a minute ago] is in state [exited] My debian 12 has 4 CPU, 8 GB RAM, 50GB disk. Before any flyte testing I had: 27 GB of disk, 6.5GM ram, <10% of CPU usage. After my last test'`flytectl demo start --version v1.12.0`' I had: 19GB of disk, no RAM changes, 14% CPU Do you think it could be due to the characteristics of my VM? Thanks!
a
do you have any other container in that VM? or is it solely dedicated to running Flyte?
r
I do not have other containers, but I do have other tests running (not containerized). I have asked for a new testing VM to repeat the tests. Thanks!
👍🏽 1
37 Views
Open in Slack
PreviousNext
Powered by