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
Hello! I Have An Issue On A Last-Week Self-Hosted Clearml Installation (Server: 1.16.0-494): After Starting Containers With Docker Compose Everything Goes Well Except For

Hello! I have an issue on a last-week self-hosted ClearML installation (Server: 1.16.0-494): after starting containers with docker compose everything goes well except for clearml-fileserver container is constantly restaring (every minute).

The "docker logs clearml-fileserver" command gives the line "clearml_agent.backend_api.session.session.LoginError: Failed getting token (error 401 from None ): Unauthorized (invalid credentials) (failed to locate provided credentials)"

All installation instructions are done according to the official docs: None

  
  
Posted 5 months ago
Votes Newest

Answers 2


Hi @<1722061354531033088:profile|TroubledCamel37> , what do you see in the apiserver logs?

  
  
Posted 5 months ago

Hi @<1523701070390366208:profile|CostlyOstrich36> ! Thanks for responding!
In the apiserver.log there are periodic (~1 min) messages like this:
[9] [WARNING] [clearml.service_repo] Returned 401 for auth.login in 2ms, msg=Unauthorized (invalid credentials) (failed to locate provided credentials)
In the fileserver.log there are no fresh messages - probably because the container could not start normally.

  
  
Posted 5 months ago
498 Views
2 Answers
5 months ago
5 months ago
Tags