Do I maybe need to do something more that I wasn’t aware to start the trigger schedule on the service queue? Or is it better at this point to just manually run a script on the machine and do “start()” instead of “start_remotely()”?
The container is still running and doesn’t show any log entry when I start the trigger scheduler remotely
The log of the “clearml-agent-services” only contained this:
Assuming you're running it in docker-compose, you should be able to get he docker logs for the apps-agent container
@<1792727007507779584:profile|HollowKangaroo53> , is it a self hosted server?
And the services agent? Can you get its log?
Exactly, I guess that is exactly the problem probably caused by start_remotely() terminating the process accidentally. The server is 2.0.0-613
@<1792727007507779584:profile|HollowKangaroo53> what is the ClearML Server you're using? I don't see the task being run at all, just installing dependencies and exiting.
This is the log of the remote run (the local one is just a bunch of “Sleeping until the next pool instead 1.5 minutes” plus the logs of my schedule function as expected). The version of the sdk is 1.17.1
Hi @<1792727007507779584:profile|HollowKangaroo53> , can you please share the log of this run, as well as the clearml SDK version you're using?