I've investigated it some more, It isn't path related as far as I can tell, as these same paths worked 2 weeks ago and a normal path doesn't work now

you could do something like 'tags':{'AND':['pipe','training']}
And the user could decide if he wants AND or OR logic

That should do the trick, thanks 🙂

By the way, what about enabling closing workers from the UI? 🙂

Actually the 5031 is the PID.

How can I tell what's the temp folder path?

AgitatedDove14 Quite hard for me to try this right now. but I've validated that the relevant code segments are untouched between the versions. (at least current master branch at the ClearML repo)

Oh

in /tmp/.trainsagent_5031_f4iwisna.tmp
For example

The file content by the way contained only the worker's name

Since my servers have a shared file system, the init process tells me that the configuration file already exists. Can I tell it to place it in another location? GrumpyPenguin23

in the file's name

Hmm, I've changed my trains-server config location to use a config in a different location, and successfully set up in the second server the trains-agent. But I don't see any new worker created, why is that?

great, will try this

I've ran this 8 times:
trains-agent --config-file /opt/trains/trains.conf daemon --detached --cpu-only --queue important_cpu_queue cpu_queueThe version is 0.16.2rc0 (a version Mushik gave me that supports local conda env)

I see, will keep that in mind. Thanks Martin!

how could I configure this in the docker compose?
Edit: the trains-agent points to a different trains.conf config as I wis., I want the dev environment to point to a different location trains.conf as well

trains ( 0.16.1-320 )

I bet it has something to do with the server or DB, any clue?

Nope, I've run them with the command I've written here

3.6.6

I understand how this is problematic. This might require more thinking if you guys wish to support this.

Nope, only its name

Yep. Works as you said.

Thanks

Great! Thanks.

So what can I do?

If I'd be exact that's a trains agent task that creates in a new subprocess another trains agent task

For me

It's important to say that this happens when I have more than like 4 workers but when I run the
trains-agent daemon --stopWith less than 4 workers it works well