Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escaping: Escape characters +-&|!(){}[]^"~*?:\ with \, e.g. \+
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
Answered
Hey Folks, When Trying To Use The Git User & Password For My Clearml-Agent, I Received An Error Message Saying That Support For Cloning Using The User Password Is No Longer Supported. So, When I Changed The Clearml.Conf At ~/Clearml.Conf, I See That The A

Hey folks, when trying to use the git user & password for my clearml-agent, I received an error message saying that support for cloning using the user password is no longer supported. So, when I changed the clearml.conf at ~/clearml.conf, I see that the agents already registered were not pulling the configuration from here even after the task was enqueued after the change in conf. How do I reset the configuration of the agents?

Weirdly, the clearml-agent config command gives me the new configuration, but the logs from the clearml-agent are still using the old config. A little help needed here. 🙂

  
  
Posted one year ago
Votes Newest

Answers 5


@<1523701087100473344:profile|SuccessfulKoala55> What would be the recommended command to delete/unregister an agent? None of the CLI commands seemed relevant to this operation other than the clearml-agent daemon --stop command that seems to only be stopping running instances of the agent and not unregistering it.

  
  
Posted one year ago

@<1523701087100473344:profile|SuccessfulKoala55> I have also tried using the API reference listed None to unregister a worker. However, it goes unregistered for a few seconds and comes back up on the UI. The Post request returns with a 200 response and says that the job is done.
image

  
  
Posted one year ago

For the people who are going to visit this thread later, what I found works is basically providing all the defining parameters of the clearml worker and then passing the arg --stop in the command.
Ex: sudo clearml-agent daemon --detached --queue gpu_default gpu_priority --gpus 0 --docker --stop
What didn't work for me: sudo clearml-agent daemon --stop <worker-id>

  
  
Posted one year ago

Hey @<1523701087100473344:profile|SuccessfulKoala55> that was actually my first approach. I used the command clearml-agent daemon --stop <worker-id>
However, this is what I saw:
image

  
  
Posted one year ago

SlimyElephant79 when you change the clearml.conf file used by an agent, you'll need to stop the agent and run it again

  
  
Posted one year ago