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
Hi, How Can I Check If My Clearml-Agent Is Running Probably? I Setup A Local Server To Test, But Seems It Does Not Pick Up Any Job. In The Ui, I Saw The New Agent Was Registered (It Shown Up In The "Workers" Page) The Terminal Looks A Bit Weird, After S

Hi, how can I check if my clearml-agent is running probably? I setup a local server to test, but seems it does not pick up any job.

In the UI, I saw the new agent was registered (It shown up in the "workers" page)

The terminal looks a bit weird, After seeing this message, no new log is pop up and it looks stuck.

Running in Docker mode (v19.03 and above) - using default docker image: nvidia/cuda:10.1-cudnn7-runtime-ubuntu18.04

  
  
Posted 2 years ago
Votes Newest

Answers 16


First thing to make sure is that this is indeed your default queue's ID - perhaps the agent configuration is incorrect and the agent is connecting to a different server?

  
  
Posted 2 years ago

Do you see this message now as well?

  
  
Posted 2 years ago

This is the only log I see.

  
  
Posted 2 years ago

How do I confirm this?

  
  
Posted 2 years ago

Digest: sha256:407714e5459e82157f7c64e95bf2d6ececa751cca983fdc94cb797d9adccbb2f Status: Downloaded newer image for nvidia/cuda:10.1-cudnn7-runtime-ubuntu18.04 docker: Error response from daemon: OCI runtime create failed: container_linux.go:370: starting container process caused: process_linux.go:459: container init caused: Running hook #0:: error running hook: exit status 1, stdout: , stderr: nvidia-container-cli: initialization error: driver error: failed to process request: unknown.

  
  
Posted 2 years ago

Sorry, let me get back to you tomorrow. Maybe I did something wrong now the entire UI crash

  
  
Posted 2 years ago

I'm not sure, but I suspect it might be an issue... perhaps AgitatedDove14 knows?

  
  
Posted 2 years ago

Now my problem is clearml-agent pick up the job but fail to run the docker.

  
  
Posted 2 years ago

Do you see any change in the URL if you click on you "test" queue?

  
  
Posted 2 years ago

I am running on Window 10 Machine, is this not compatible?

  
  
Posted 2 years ago

Well, go to the Workers and Queues section in the WebApp, click on Queues, than click on your default queue - the queue ID should appear in the URL

  
  
Posted 2 years ago

Not sure why my elasticsearch & mongodb crashed. I have to remove and recreate all the dockers. Then clearml-agent works fine too

  
  
Posted 2 years ago

Yes, i did use foreground.

I tested in a older "trains" server, it will show up log like this if no job is pick up. While my new "clearml-agent" shows nothing

No tasks in queue bb1bb1673f224fc98bbc8f86779be802
No tasks in Queues, sleeping for 5.0 seconds

  
  
Posted 2 years ago

Hi EnviousStarfish54
docker on windows , with nvidia runtime support is only with WSL (I think)
https://docs.nvidia.com/cuda/wsl-user-guide/index.html#installing-wip
https://medium.com/@dalgibbard/docker-with-gpu-support-in-wsl2-ebbc94251cf5

  
  
Posted 2 years ago

hmmmm, maybe I missed some UI Element, I can't locate any ID

  
  
Posted 2 years ago

Hi EnviousStarfish54 , did you use --foreground ? By default, the agent will output it's log to a log file, unless explicitly requested to do otherwise

  
  
Posted 2 years ago
385 Views
16 Answers
2 years ago
10 months ago
Tags