@<1734020208089108480:profile|WickedHare16> Do you mean that you see the plots now? Are there still any _attempt_serialize_numpy errors in the apiserver logs?

🙂

Hi @<1523701601770934272:profile|GiganticMole91> , I do not see any difference that could lead to Elasticsearch from v1.16 not being able to start from the data that was stored in v1.15. Probably some more information can be retrieved from ES logs right after the upgrade and services restart. If there are some reasons the prevent ES from loading the existing data they may be listed in the logs

Thank you for the fix:) I will update the script for future usages

@<1734020208089108480:profile|WickedHare16> Can you please share an example plot url that is not opened in UI but you can see it in a separate tab?

Hi @<1526734383564722176:profile|BoredBat47> , please try to remove the ", "case_insensitive": true" from the last line of the command that I sent to you

Hi @<1734020208089108480:profile|WickedHare16> , what is the image of the apiserver that you are running?

Please take a look here:
None
Does it match you scenario? Can you try the suggested workaround?

Hi @<1523701601770934272:profile|GiganticMole91> , what is the exact version of Elasticsearch that is running now in your 1.15.0 installation? You can see it in the output of 'sudo docker ps'

Can you please run 'sudo docker ps' and share the results? I want to see what is the real version of the apiserver image used

clearml:1 as well as clearml:latest point to the latest version which is 1.16.2:
None
This version is not able to work with the version of Elasticsearch that you use. I suggest to use the docker compose from the latest version that uses the updated versions of all the required infrastructure

Can you please describe what working deployments you current have and what is you final goal?
Do you have an old deployment working or it was corrupted?
Do you want to upgrade that old deployment to a new one? Or you want to have a new deployment in some other place based on the data from the old deployment?

Hi @<1526734383564722176:profile|BoredBat47> , it seems that your Elasticsearch version is out of sync with what the latest version of the apiserver requires (7.17.18). Can you please follow the instructions here to make sure that you use the latest images for the ClearML Server?
None

@<1526734383564722176:profile|BoredBat47> So your upgraded your source deployment to the latest clearml server, then backed up the data and tried to restore it on the target deployment that runs the same (latest) clearml server, correct? What is the error that you see in elastic logs on the target deployment?

Yes, it seems so. I though we were talking about the fresh installation that you did.

The path then would be as following:

• Upgrade the old deployment to the latest clearml server according to the clearml server upgrade procedure. This will automatically upgrade the data
• Backup your data folders (mongo and elastic)
• Deploy the latest clearml server on another machine and restore the data from the backup

Hi @<1547028074090991616:profile|ShaggySwan64> , by default ES allocates up to 50% of total RAM. If you think that this is an overkill for your case then you can limit it with ES_JAVA_OPTS parameters. I think that the 2GB limit that we had their earlier is too restrictive and may affect the ES performance and stability. So try putting there the number that depends on your needs and available memory but I would not go with less than 4Gb

Hi @<1689446563463565312:profile|SmallTurkey79> , we identified the problem and working on the fix

@<1523701601770934272:profile|GiganticMole91> Is your ES deployment a single node or a cluster? If you compare the elaststicsearch section of the docker compose of your currently working version (1.15.0) and then one that you tried to install (v1.16) do you see any difference?

@<1526734383564722176:profile|BoredBat47> Can you please share the exact command that you are running?

Great! Thanks:)

No. It is actually string concatenation. What you actually get is that an original string is broken into several parts. That are concatenated as following:
-d'{....' + ' + '....}'

@<1526734383564722176:profile|BoredBat47> Please try running the following command

curl -XPOST -H 'Content-Type: application/json' 'localhost:9200/events-training_debug_image-*/_update_by_query?conflicts=proceed' -d'{
    "script": {
        "source": "ctx._source.url = ctx._source.url.replace('

.<OLD_ADDRESS>', '

.<NEW_ADDRESS>')",
        "lang": "painless"
    },
    "query": {"prefix": {"url": {"value": "

.<OLD_ADDRESS>", "case_insensitive": true...

Hi @<1577468611524562944:profile|MagnificentBear85> , the instructions that you followed should fix the addresses of debug images. For artifacts there are different instructions. Please follow the instructions from "For artifacts" item:
[https://clear.ml/docs/latest/docs/faq/#debug-images-andor-artifacts-are-not-loading-in-the-u[…]clearml-server-to-a-new-address-how-do-i-fix-this----](https://clear.ml/docs/latest/docs/faq/#debug-images-andor-artifacts-are-not-loading-in-the-ui-after-i-migra...

A bit confusing. But this is what linux shell wants if you have single quotes inside double quotes inside outer single quotes

Yeah, they should:) The problem is that they are inside outer single quotes -d'{...}'

''' = ' + ' + '

Please share you command

About the prefix part I think it should not matter. Just put your prefix instead of ' None .<ADDRESS>'

Hi @<1526734383564722176:profile|BoredBat47> , did the last update urls command work for you? I want to update our documentation