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 All, I Recently Updated My Self-Hosted Clearml-Server To 1.10 And It Seemed To Fail (See Attached Image). I Checked The Logs And Could Not Find Any Errors That Would Prevent The Server From Working. I Did Find These Errors In Clearml-Elastic By Runnin

Hi all,
I recently updated my self-hosted clearml-server to 1.10 and it seemed to fail (see attached image). I checked the logs and could not find any errors that would prevent the server from working.

I did find these errors in clearml-elastic by running docker logs clearml-elastic | less | grep -v INFO | less

 {"type": "deprecation.elasticsearch", "timestamp": "2023-04-02T07:29:06,804Z", "level": "CRITICAL", "component": "o.e.d.c.s.Settings", "cluster.name": "clearml", "node.name": "clearml", "message": "[node.ingest] setting was deprecated in Elasticsearch and will be removed in a future release! See the breaking changes documentation for the next major version.", "key": "node.ingest", "category": "settings" }
{"type": "deprecation.elasticsearch", "timestamp": "2023-04-02T07:29:06,868Z", "level": "CRITICAL", "component": "o.e.d.n.Node", "cluster.name": "clearml", "node.name": "clearml", "message": "legacy role settings [node.ingest] are deprecated, use [node.roles=[transform, data_frozen, master, remote_cluster_client, data, ml, data_content, data_hot, data_warm, data_cold, ingest]]", "key": "legacy role settings", "category": "settings" }
{"type": "deprecation.elasticsearch", "timestamp": "2023-04-02T07:29:08,487Z", "level": "CRITICAL", "component": "o.e.d.c.s.Settings", "cluster.name": "clearml", "node.name": "clearml", "message": "[xpack.monitoring.enabled] setting was deprecated in Elasticsearch and will be removed in a future release! See the breaking changes documentation for the next major version.", "key": "xpack.monitoring.enabled", "category": "settings" }
{"type": "deprecation.elasticsearch", "timestamp": "2023-04-02T07:29:08,489Z", "level": "CRITICAL", "component": "o.e.d.c.s.Settings", "cluster.name": "clearml", "node.name": "clearml", "message": "[discovery.zen.minimum_master_nodes] setting was deprecated in Elasticsearch and will be removed in a future release! See the breaking changes documentation for the next major version.", "key": "discovery.zen.minimum_master_nodes", "category": "settings" }
{"type": "deprecation.elasticsearch", "timestamp": "2023-04-02T07:29:41,069Z", "level": "WARN", "component": "o.e.d.r.RestController", "cluster.name": "clearml", "node.name": "clearml", "message": "Legacy index templates are deprecated in favor of composable templates.", "key": "deprecated_route_PUT_/_template/{name}", "category": "api", "cluster.uuid": "Qn-Lwrw8QqaW6rlMVGQ6Aw", "node.id": "AW_veqC2Q0O5KQJr5OtKPQ"  }

there is nothing on /opt/clearml/logs/ that indicates an issue or on the docker logs. Any idea what's going on?
image

  
  
Posted one year ago
Votes Newest

Answers 4


I put it there since I tried using clearml fileserver URLs as input to foxglove studio (playback of remote .bag files recorded in ROS). Foxglove required these CORS settings, but we since then pivoted to a different solution so it is no longer needed.

  
  
Posted one year ago

Got it 👍

  
  
Posted one year ago

@<1523701235335565312:profile|HugeArcticwolf77> do you know why was it there to begin with?

  
  
Posted one year ago

For future reference - I managed to solve the issue.
I found that I have an old CORS configuration that I no longer need in /opt/clearml/config/ (for both API and file servers). Once I removed the cors segment from the config and restarted the server it worked.

  
  
Posted one year ago
1K Views
4 Answers
one year ago
one year ago
Tags