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
Hey, I Moved My Trains-Server To Another Machine, Zipping The /Opt/Trains/Data Folder As Described In The Docs

Hey, I moved my trains-server to another machine, zipping the /opt/trains/data folder as described in the docs https://allegro.ai/docs/deploying_trains/trains_server_linux_mac/#upgrading , but now elasticsearch refuses to start with the following logs:
# LICENSE [EXPIRED] ON [THURSDAY, JULY 16, 2020]. IF YOU HAVE A NEW LICENSE, PLEASE UPDATE IT. trains-elastic | # OTHERWISE, PLEASE REACH OUT TO YOUR SUPPORT CONTACT. trains-elastic | # trains-elastic | # COMMERCIAL PLUGINS OPERATING WITH REDUCED FUNCTIONALITY trains-elastic | # - security trains-elastic | # - Cluster health, cluster stats and indices stats operations are blocked trains-elastic | # - All data operations (read and write) continue to work trains-elastic | # - watcher trains-elastic | # - PUT / GET watch APIs are disabled, DELETE watch API continues to work trains-elastic | # - Watches execute and write to the history trains-elastic | # - The actions of the watches don't execute trains-elastic | # - monitoring trains-elastic | # - The agent will stop collecting cluster and indices metrics trains-elastic | # - The agent will stop automatically cleaning indices older than [xpack.monitoring.history.duration] trains-elastic | # - graph trains-elastic | # - Graph explore APIs are disabled trains-elastic | # - ml trains-elastic | # - Machine learning APIs are disabled trains-elastic | # - deprecation trains-elastic | # - Deprecation APIs are disabled trains-elastic | # - upgrade trains-elastic | # - Upgrade API is disabledThis has something to do with the license of elasticsearch?

  
  
Posted 4 years ago
Votes Newest

Answers 11


JitteryCoyote63 There is a basic elastic license that should always be there. If for some reason it was deleted/expired then the following command should fix it:
curl -XPOST ' http://localhost:9200/_xpack/license/start_basic '

  
  
Posted 4 years ago

I was able to fix by applying for a license and registering it

  
  
Posted 4 years ago

Bottom line is: trains-server uses elastichsearch image: http://docker.elastic.co/elasticsearch/elasticsearch:5.6.16 which does not have an unlimited license (only free license that expires after some time). From versions 6.3, elasticsearch provides an unlimited free license. Trains should use >=6.3, WDYT?

  
  
Posted 4 years ago

JitteryCoyote63 next week is the Trains next release with upgrade to ES 7, do you want to wait or sort a solution for this one ?
(BTW: I think that you can mount a license file or delete one, and it should be okay, I'll ask the backend guys regradless)

  
  
Posted 4 years ago

Well it is there, do you have it in your docker-compose as well?
https://github.com/allegroai/trains-server/blob/master/docker-compose.yml#L55

  
  
Posted 4 years ago

I think this is because this API is not available in elastic 5.6

  
  
Posted 4 years ago

JitteryCoyote63 This seems like exactly what you are saying, elastic license issue...

  
  
Posted 4 years ago

Relevant issue in Elasticsearch forums: https://discuss.elastic.co/t/elasticsearch-5-6-license-renewal/206420

  
  
Posted 4 years ago

AgitatedDove14 Yes I have the xpack security disabled, as in the link you shared (note that its xpack.security.enabled: "false" with brackets around false), but this command throws:

{"error":{"root_cause":[{"type":"parse_exception","reason":"request body is required"}],"type":"parse_exception","reason":"request body is required"},"status":400}

  
  
Posted 4 years ago

JitteryCoyote63 Not sure how/why the X-Pack feature was on (it is not used by the system), but you can disable it with an environment variable in the docker-compose
xpack.security.enabled=falseShould solve the problem ...

From here:
https://medium.com/@ospaarmann/tidbits-solving-the-elasticsearch-x-pack-license-issue-in-docker-d15bb22d82fd

  
  
Posted 4 years ago

Nice!

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