SmarmySeaurchin8 what's the trains-agent
version? What command did you use to start it (also did you use a custom worker ID)?
I've ran this 8 times:trains-agent --config-file /opt/trains/trains.conf daemon --detached --cpu-only --queue important_cpu_queue cpu_queue
The version is 0.16.2rc0 (a version Mushik gave me that supports local conda env)
And what's the TRAINS_WORKER_ID
you're using? It seems this issue is caused by the agent failing to locate a suitable .trainsagent*
file in the temp folder (these files store the currently running agent PIDs)
Also - what is the temp folder path in your case?
Nope, I've run them with the command I've written here
How can I tell what's the temp folder path?
And how can I tell which TRAINS_WORKER_ID
I'm using?
It's important to say that this happens when I have more than like 4 workers but when I run thetrains-agent daemon --stop
With less than 4 workers it works well
The trains-agent prints out the temp folder as part of the configuration dump to the log, when it starts
SuccessfulKoala55 I found the temp files, they contain the supposedly worker id, which seems just fine
By the way, what about enabling closing workers from the UI? 🙂
By the way, what about enabling closing workers from the UI?
As always, we'll appreciate a GitHub issue for feature requests 🙂 - I'll write it down
I found the temp files
What's the path they're located in?
in /tmp/.trainsagent_5031_f4iwisna.tmp
For example
Does the file contain the agent's PID?
SmarmySeaurchin8 when calling with --stop
, you need to use the exact same command-line used to start the agent, with the --stop
flag added. In your case:trains-agent --config-file /opt/trains/trains.conf daemon --detached --cpu-only --queue important_cpu_queue cpu_queue --stop
The file content by the way contained only the worker's name
I'll add the fix to the startswith
error you've reported to the next version in any case