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 Channel, I Am Trying To Upgrade My Ec2 With The Community Ami From Trains 0.16 Server To Latest Clearml Server. I Followed The Instructions

Hi channel, I am trying to upgrade my EC2 with the community AMI from trains 0.16 server to latest ClearML server. I followed the instructions https://allegro.ai/clearml/docs/docs/deploying_clearml/clearml_server_aws_ec2_ami.html#upgrading-on-the-same-aws-instance but get an error when executing step 6
docker-compose -f /opt/clearml/docker-compose.yml pull docker-compose -f docker-compose.yml up -dwith the following message:
` WARNING: The CLEARML_HOST_IP variable is not set. Defaulting to a blank string.
WARNING: The CLEARML_AGENT_GIT_USER variable is not set. Defaulting to a blank string.
WARNING: The CLEARML_AGENT_GIT_PASS variable is not set. Defaulting to a blank string.
Creating network "clearml_backend" with driver "bridge"
Creating network "clearml_frontend" with driver "bridge"
Creating clearml-redis ...
Creating clearml-elastic ...
Creating clearml-fileserver ...
Creating clearml-fileserver ... error
Creating clearml-redis ... done
Creating clearml-elastic ... done
ERROR: for clearml-fileserver Cannot start service fileserver: driver failed programming external connectivity on endpoint clearml-fileserver (4a1d2aCreating clearml-mongo ... done

ERROR: for fileserver Cannot start service fileserver: driver failed programming external connectivity on endpoint clearml-fileserver (4a1d2a7f0cfe2d5fec3b11cf49c244a3dcf60d38f7b696b738cccd0d2ef80cfb): Bind for 0.0.0.0:8081 failed: port is already allocated
ERROR: Encountered errors while bringing up the project. Also, after executing sudo docker-compose down ` I still can access the web UI

  
  
Posted 2 years ago
Votes Newest

Answers 24


after running docker ps I saw that all the ports are still listed. I then changed the name of /opt/clearml back to /opt/trains and ran the command sudo docker-compose -f /opt/trains/docker-compose.yml down and it did the trick

  
  
Posted 2 years ago

when running the docker ps command the output is empty

  
  
Posted 2 years ago

I think you have the page cached - can you try reloading using

Ctrl-F5

?

using Ctrl-F5 it redirects to the ClearML new login

  
  
Posted 2 years ago

but if I just enter the URL with ending :8080 it takes me to the old login

  
  
Posted 2 years ago

SuccessfulKoala55 in step 1. it isn't written

  
  
Posted 2 years ago

it turns out that my docker-compose.yml wasn't in the environment path, so when I first ran the down command, it had no effect

  
  
Posted 2 years ago

Before starting this upgrade, did you shut down the old Trains Server using sudo docker-compose -f /opt/trains/docker-compose.yml down ?

  
  
Posted 2 years ago

and then if you do Ctrl-F5?

  
  
Posted 2 years ago

In the browser

  
  
Posted 2 years ago

So it means the old WebApp is still in cache...

  
  
Posted 2 years ago

I see

  
  
Posted 2 years ago

(and I didn't use the -f switch since it wasn't in the instructions, and I'm not familiar with dockers all that much)

  
  
Posted 2 years ago

if I add :8080/login I get the new "clearML" welcome page

  
  
Posted 2 years ago

I see, I'll try to clear the cache

  
  
Posted 2 years ago

So it means the old WebApp is still in cache...

meaning the browser or in the server?

  
  
Posted 2 years ago

Hi MinuteWalrus85 ,
From your description I'm pretty sure you didn't shut down at least parts of the old server still running. Both the fact that the 8081 port is not free, as well the fact that you can still access the WebUI after shutting down...

  
  
Posted 2 years ago

I think you have the page cached - can you try reloading using Ctrl-F5 ?

  
  
Posted 2 years ago

Thanks Jake, clearing the Cache did the trick! thank you so much for your assistance!

  
  
Posted 2 years ago

going to the server URL:8080 -> old trains login (working as usual if I enter my credentials) -> Ctrl-F5 -> switched to the new interface

  
  
Posted 2 years ago

Hi MinuteWalrus85 .

looks like port 8081 is in use, can you check it? docker ps will output you the running dockers (with the ports)

  
  
Posted 2 years ago

after upgrade - if I go to the url and ending with :8080 I get the old "trains" welcome page

  
  
Posted 2 years ago

it will switch to the new one

  
  
Posted 2 years ago

and I didn't use the

-f

switch since it wasn't in the instructions

Are you sure this was not in the instructions? I'm going over them now and I see -f everywhere. If its missing, please point me there and I'll fix it

  
  
Posted 2 years ago

docker ps will also show any other containers still running (old Trains Server?)

  
  
Posted 2 years ago
252 Views
24 Answers
2 years ago
8 months ago
Tags