AppetizingMouse58 yes, sure

I was helped by running from user 1000 and the command "http_proxy= docker-compose -f /opt/trainz/docker-compose.html up"
AppetizingMouse58 SuccessfulKoala55 Thank you so much!

AppetizingMouse58 I made my user the owner (sudo chown liz:liz -R /opt/trains/), but the problem still remains.

SuccessfulKoala55 Sure. I can attach an archive with the elastic folder if necessary. But it weighs 500MB

AppetizingMouse58 There should be enough space on the disks

AppetizingMouse58 thanks a lot! After I deleted the indices, I was able to migrate the data and update the trains version to 0.16.0

In this case I have err: {"error":{"root_cause":[{"type":"parse_exception","reason":"request body is required"}],"type":"parse_exception","reason":"request body is required"},"status":400}(

Amount of memory

AgitatedDove14 We have projects that we would like to restrict access to within a team, but we would like to avoid raising a seperate trains-server for these projects )

AppetizingMouse58 When I tried to go to http://localhost:9200/_xpack/license/start_basic , I received this err msg: {"error":{"root_cause":[{"type":"index_not_found_exception","reason":"no such index","resource.type":"index_expression","resource.id":"_xpack","index_uuid":"_na_","index":"_xpack"}],"type":"index_not_found_exception","reason":"no such index","resource.type":"index_expression","resource.id":"_xpack","index_uuid":"_na_","index":"_xpack"},"status":404}

AgitatedDove14 Well, thank you for your answers and the link )

AppetizingMouse58 In general, I first had the trains version 0.15.1, it worked. I decided to upgrade to version 0.16.0, made a data backup, but did not make the data migration, and I got the following error (the screenshot). Then I tried to make a migration, but then there was a problem, I already wrote about it. After that, I tried to roll back by downloading http://docker-compose.ml from git (with tag 0.15.1) and making docker-compose-f /opt/trainz/docker-compose.yml pull , and als...

AppetizingMouse58 I tried it, but now I have new errors with shards (

AppetizingMouse58 yes, I see two indices with red status. And now should I delete them? If yes, command for that like this:
curl -XDELETE localhost:9200/queue_metrics/d1bd92a3b039400cbafc60a7a5b1e52b_2020-08?

AppetizingMouse58

In the attached file my new log from elastic-upgrade, and some info about the elastic cluster.

AppetizingMouse58 I updated my lincense, but it doesnt work for me. And I have not --extra_source-env argument in elastic_upgrade.py