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 Try To Update Trains-Server (0.16) To Clearml-Server In Another Linux Machine, Here Is My Steps:

Hello, I try to update trains-server (0.16) to clearml-server in another linux machine, here is my steps:
copy(scp) /opt/trains to target machine update /opt/trains/mongo to /opt/trains/mongo_4 in target machine mv /opt/trains /opt/clearml; get lastest docker-compose.yml and pull/upBut, i get SERVER UNAVAILABLE in web ui, what's wrong with my solution? (And i try to deploy a new clearml sever from scratch, it works fine)

  
  
Posted 2 years ago
Votes Newest

Answers 31


I know why, because i used the old apiserver.conf, i set fixed_users. After log in http://xxx:8080/login , it's ok now

  
  
Posted 2 years ago

OK, this indeed seems like v0.16 🙂

  
  
Posted 2 years ago

Do you mean i send the old one to you?

  
  
Posted 2 years ago

here is my old docker-compose

  
  
Posted 2 years ago

Oh... that's very strange

  
  
Posted 2 years ago

I tried as below, it can works fine:
copy(scp) /opt/trains to target machine upgrade mongo by this: https://clear.ml/docs/latest/docs/deploying_clearml/clearml_server_mongo44_migration/ mv /opt/trains /opt/clearml Increase vm.max_map_count ;Grant access to the Dockers; get lastest docker-compose.yml and pull/upBut the web ui dashboard is still weird, anyway it can work now

  
  
Posted 2 years ago

so the process to move to a new machine and upgrade should be:
Shut down the server Copy the data folder to a new machine Run the migration script from <=v1.1 to v1.2 - the script should automatically create the new mongo_4 folder Get the new docker-compose Start the new server

  
  
Posted 2 years ago

I know, I just want to understand the old one's status

  
  
Posted 2 years ago

I want to use clearml, the old one's mongo is 3.65...

  
  
Posted 2 years ago

I mean the old one, in the non-migrated server

  
  
Posted 2 years ago

Where's "view all" in that screenshot?

  
  
Posted 2 years ago

Cam you perhaps send the docker-compose in the current server? (已編輯)

Sorry I don't undestand what' your meaning...

  
  
Posted 2 years ago

Cam you perhaps send the docker-compose in the current server?

  
  
Posted 2 years ago

This only means the UI is loading but can't access the server

  
  
Posted 2 years ago

But when i click view_all, i can see all the experiments

  
  
Posted 2 years ago

OK i will try again, this time i won't upgrade ES, But do increase vm.max_map_count and open access of /opt/clearm. Why i do again is i found the web ui is fine in deployed machine, but it's weird in my local machine:

  
  
Posted 2 years ago

SuccessfulKoala55 I get all the trains server experiments record in new clearml server. Maybe it's due to vm.max_map_count or access of /opt/clearml, or the failed ES upgrade...

  
  
Posted 2 years ago

My docker-compose is lateset, download by this:
curl https://raw.githubusercontent.com/allegroai/clearml-server/master/docker/docker-compose.yml -o /opt/clearml/docker-compose.yml

  
  
Posted 2 years ago

If you only want to move the server to another machine and not upgrade the server version, you should just copy the folder and restart the server there, but change nothing

  
  
Posted 2 years ago

7.6 and 7.16 do not require data migration, 7.16 can simply be started after the migration to 7.6 was done

  
  
Posted 2 years ago

This is the migration step. once done, the latest docker compose should use the 7.16 image

  
  
Posted 2 years ago

Also, from the log, I see your ES version is 5.6:

at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:136) ~[elasticsearch-5.6.16.jar:5.6.16]

and I'm not sure why - in v0.16, the ES version is already 7.6, which makes me think your original version was v0.15, also in the new docker-compose the version is 7.16, so maybe you are not using the updated docker-compose file?

It confused me too, but ES dir in my 0.16 version is /opt/trains/data/elastic_7

  
  
Posted 2 years ago

Also, from the log, I see your ES version is 5.6:
at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:136) ~[elasticsearch-5.6.16.jar:5.6.16]and I'm not sure why - in v0.16, the ES version is already 7.6, which makes me think your original version was v0.15, also in the new docker-compose the version is 7.16, so maybe you are not using the updated docker-compose file?

  
  
Posted 2 years ago

Sorry , my poor english, it means upgrade by script.
Good news is it's fine now, I try to upgrade ES (although it fails), and i try to go through the necessary steps in this: https://clear.ml/docs/latest/docs/deploying_clearml/clearml_server_linux_mac

  
  
Posted 2 years ago

Hi SuccessfulKoala55 I find why the ES version is not upgraded to 7.16, because the script provided here is 7.6 https://clear.ml/docs/latest/docs/deploying_clearml/clearml_server_es7_migration

  
  
Posted 2 years ago

Hi SubstantialBaldeagle49 , in order to upgrade to v1.2, you will need to run a migration, see https://clear.ml/docs/latest/docs/deploying_clearml/clearml_server_mongo44_migration/

  
  
Posted 2 years ago

Correct me if I'm wrong, but you wrote:

  1. update /opt/trains/mongo to /opt/trains/mongo_4 in target machine

which does not mention running the upgrade script?

  
  
Posted 2 years ago

And i try to upgrade elastic by your script, but it cannot success, the log shows :

  
  
Posted 2 years ago

Hi SuccessfulKoala55 I have run this in step 2

  
  
Posted 2 years ago

image

  
  
Posted 2 years ago
589 Views
31 Answers
2 years ago
12 days ago
Tags