# Getting track syntax error while running esrally Could not execute benchmark', TrackSyntaxError **URL:** \ **Category:** Elasticsearch\ **Tags:** rally\ **Created:** [November 22, 2018, 10:59am UTC](https://discuss.elastic.co/t/getting-track-syntax-error-while-running-esrally-could-not-execute-benchmark-tracksyntaxerror/157863 "2018-11-22T10:59:14Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Ronnie16](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ronnie16/32/66399_2.png) [@Ronnie16](https://discuss.elastic.co/u/Ronnie16)\ **Post date:** [November 22, 2018, 10:59am UTC](https://discuss.elastic.co/t/getting-track-syntax-error-while-running-esrally-could-not-execute-benchmark-tracksyntaxerror/157863/1 "2018-11-22T10:59:14Z")
Running esrally inside a container with - esrally --track=geonames --target-hosts=17.99.221.188:80 --pipeline=benchmark-only But getting the following error - [ERROR] Cannot race. ('Could not execute benchmark', TrackSyntaxError('Track 'geonames' is invalid.\n\nError details: 'type' is not of type 'object'\nInstance: "type"\nPath: deque(['indices', 0, 'types', 0])\nSchema path: deque(['properties', 'indices', 'items', 'properties', 'types', 'items', 'type'])',)) NOTE: - before running this I had deleted /root/.rally/benchmarks/tracks/default. as was getting the below error [ERROR] Cannot race. ('Could not execute benchmark', DataError('Cannot update [tracks] in [/root/.rally/benchmarks/tracks/default].',)) ---
**Author:** ![dliappis](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dliappis/32/56174_2.png) [@dliappis](https://discuss.elastic.co/u/dliappis)\ **Post date:** [November 27, 2018, 12:13pm UTC](https://discuss.elastic.co/t/getting-track-syntax-error-while-running-esrally-could-not-execute-benchmark-tracksyntaxerror/157863/2 "2018-11-27T12:13:23Z")
Hi @Ronnie16, I wasn't able to reproduce this. I created a simple docker-compose file deploying elasticsearch and a `python:3` image where I manually exec'd into to install esrally. NOTE: it's not recommended to run Rally as the root user inside the Docker image, as well as relying on the union filesystem for its `~/.rally` directory. At any rate, even with this repro-only setup, Rally started fine with a similar command to yours: ```auto $ docker exec -ti rallydocker_python3dev_1 /bin/bash root@a03b4a2d51c3:/# pip3 install esrally root@a03b4a2d51c3:/# esrally configure root@a03b4a2d51c3:/# esrally --track=geonames --target-hosts=tmpelasticsearch1:9200 --pipeline=benchmark-only ________ / __\____ _/ / /_ __ / /_/ / __ `/ / / / / / / _, _/ /_/ / / / /_/ / /_/ |_|\ __,_/_/_/\__ , / / ____ / ************************************************************************ **************WARNING: A dark dungeon lies ahead of you************** ************************************************************************ Rally does not have control over the configuration of the benchmarked Elasticsearch cluster. Be aware that results may be misleading due to problems with the setup. Rally is also not able to gather lots of metrics at all (like CPU usage of the benchmarked cluster) or may even produce misleading metrics (like the index size). ************************************************************************ ******Use this pipeline only if you are aware of the tradeoffs.****** ***************************Watch your step!*************************** ************************************************************************ [INFO] Racing on track [geonames], challenge [append-no-conflicts] and car ['external'] with version [6.4.2]. [INFO] Downloading data for track geonames (252.4 MB total size) [100.0%] [INFO] Decompressing track data from [/root/.rally/benchmarks/data/geonames/documents-2.json.bz2] to [/root/.rally/benchmarks/data/geonames/documents-2.json] (resulting size: 3.30 GB) ... [OK] [INFO] Preparing file offset table for [/root/.rally/benchmarks/data/geonames/documents-2.json] ... [OK] Running delete-index [100% done] Running create-index [100% done] Running check-cluster-health [100% done] Running index-append [75% done] ``` I'd try to start clean again and also ensure `~/.rally` is getting executing from a bind mount (to ensure the union fs isn't slowing things down). My docker-compose file: ```auto --- version: '2' services: tmpelasticsearch1: image: docker.elastic.co/elasticsearch/elasticsearch:6.4.2 container_name: tmpelasticsearch1 environment: - cluster.name=ESCluster - "ES_JAVA_OPTS=-Xms2g -Xmx2g" volumes: - tmpesdata1:/usr/share/elasticsearch/data ports: - 19200:9200 networks: - esnet1 python3dev: image: python:3 networks: - esnet1 command: tail -F foo volumes: tmpesdata1: driver: local networks: esnet1: ``` ---
**Author:** ![Ronnie16](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ronnie16/32/66399_2.png) [@Ronnie16](https://discuss.elastic.co/u/Ronnie16)\ **Post date:** [November 28, 2018, 11:34am UTC](https://discuss.elastic.co/t/getting-track-syntax-error-while-running-esrally-could-not-execute-benchmark-tracksyntaxerror/157863/3 "2018-11-28T11:34:15Z")
The problem is I'm running esrally in such an environment where there is no access to internet . So rally cannot download benchmark data ---
**Author:** ![danielmitterdorfer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/danielmitterdorfer/32/110510_2.png) [@danielmitterdorfer](https://discuss.elastic.co/u/danielmitterdorfer)\ **Post date:** [November 28, 2018, 12:05pm UTC](https://discuss.elastic.co/t/getting-track-syntax-error-while-running-esrally-could-not-execute-benchmark-tracksyntaxerror/157863/4 "2018-11-28T12:05:28Z")
Hi, please see our [offline usage docs](https://esrally.readthedocs.io/en/stable/offline.html). Daniel ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [December 26, 2018, 12:05pm UTC](https://discuss.elastic.co/t/getting-track-syntax-error-while-running-esrally-could-not-execute-benchmark-tracksyntaxerror/157863/5 "2018-12-26T12:05:31Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.