it happens consistently with this one task that really should be all cache.
I disabled cache in the final step and it seems to run now.
ugh. again. it launched all these tasks and then just died. logs go silent.
enqueuing. pipe.start("default") but I think it's picking up on my local clearml install instead of what I told it to use.
my tasks have this in them... what's the equivalent for pipeline controllers?
damn. I can't believe it. It disappeared again despite having 1.15.1 be the task's clearml version.
I'm going to try running the pipeline locally.
do you have any STATUS REASON under the INFO section of the controller task?
worker thinks its in venv mode but is containerized .
apiserver is docker compose stack
ill check logs next time i see it .
currently rushing to ship a model out, so I've just been running smaller experiments slowly hoping to avoid the situation . fingers crossed .
are you running this locally or are you enqueueing the task (controller)?
yeah, it just shows what I see in the Console, but then immediately goes back to polling for more work (so... instead of running backtest, it exits, no completion message)
let me downgrade my install of clearml and try again.
N/A (still shows as running despite Abort being sent)
its odd... I really dont see tasks except the controller one dying
that's the final screenshot. it just shows a bunch of normal "launching ..." steps, and then stops all the sudden.
I think i've narrowed this down to the ssh connection approach.
regarding the container that runs the pipeline:
- when I made it stop using autossh tunnels and instead put it on the same machine as the clearml server + used docker network host mode, suddenly the problematic pipeline started completing.
it's just so odd that the pipeline controller task is the only one with an issue. the modeling / data-creation tasks really all seem to complete consistently just fine.
so yeah, best guess now is that its unrelated to clearml verison but rather to the connectivity of the pipeline controller task to the api server.
when I run this pipeline controller locally (also using the same ssh tunnel approach for comms), the pipeline completes just fine. so it's something specific about how its working inside the container vs on my machine, it seems.
it's pretty reliably happening but the logs are just not informative. just stops midway
when i run the pipe locally, im using the same connect.sh script as the workers are in order to poll the apiserver via the ssh tunnel.
hoping this really is a 1.16.2 issue. fingers crossed. at this point more pipes are failing than not.
Hi @<1689446563463565312:profile|SmallTurkey79> , when this happens, do you see anything in the API server logs? How is the agent running, on top of K8s or bare metal? Docker mode or venv?
would it be on the pipeline task itself then, since that's what's disappearing? that likely the case
(the "magic" of the env detection is nice but man... it has its surprises)
Hi @<1689446563463565312:profile|SmallTurkey79> ! I will take a look at this and try to replicate the issue. In the meantime, I suggest you look into other dependencies you are using. Maybe some dependency got upgraded and the upgrade now triggers this behaviour in clearml.
trying to run the experiment that kept failing right now, watching logs (they go by fast)... will try to spot anything anamolous
but maybe here's a clue. after hanging like that for a while... it seems like the agent restarts (the container it runs in does not)
ah. a clue! it came right below that but i guess out of order...
that id is the pipeline that failed
would it be on the pipeline task itself then, since that's what's disappearing?
I will do some experiment comparisons and see if there are package diffs. thanks for the tip.
Hi @<1689446563463565312:profile|SmallTurkey79> !Prior runs of this pipeline worked just fine What SDK version were you using for the prior runs? Does this still happen if you revert to that version?
Can you provide a script that imitates what you are doing?
In the pipeline you are running, are you creating new tasks/pipelines/datasets?