# Run Rally custom track. got "gradle clean" failed error **URL:** \ **Category:** Elasticsearch\ **Tags:** rally\ **Created:** [March 20, 2017, 10:03pm UTC](https://discuss.elastic.co/t/run-rally-custom-track-got-gradle-clean-failed-error/79317 "2017-03-20T22:03:29Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Eugene22](https://avatars.discourse-cdn.com/v4/letter/e/eb8c5e/32.png) [@Eugene22](https://discuss.elastic.co/u/Eugene22)\ **Post date:** [March 20, 2017, 10:03pm UTC](https://discuss.elastic.co/t/run-rally-custom-track-got-gradle-clean-failed-error/79317/1 "2017-03-20T22:03:29Z")
I was trying to run Rally using our own custom track and data . I have put my own documents.json, document.tar.gz , and mappings and track.json in the respective data and track folder. Then I started running Rally. Before running it, I used $esrally list tracks --offline it listed my custom track "spectre" there. then I ran it, using the below command. It got some 'gradle clean" failed error in the end. See below screen shot. [eyang@App-Agent97 elasticsearch-5.1.2]$esrallyd start --node-ip=172.20.115.95 --coordinator-ip=172.20.115.95 [INFO] Successfully started actor system on node [172.20.115.95] with coordinator node IP [172.20.115.95]. [eyang@App-Agent97 elasticsearch-5.1.2]$ esrally --track=spectre --target-hosts=172.20.115.97:9200 --offline --report-file=spectre-2017-03-20-13 --report-form at=csv ``` ________ ``` / \_\_ \_\_\_\_ _/ / /_ \_\_ / /_/ / \_\_ `/ / / / / / / , / // / / / // / /_/ |_|\ __,_/_/_/\__ , / /\_\_\_\_/ # [INFO] Writing logs to /home/eyang/.rally/logs/rally\_out.log [INFO] Preparing for race ...Downloading sources from [https://github.com/elastic/elasticsearch.git](https://github.com/elastic/elasticsearch.git) to /home/eyang/.rally/benchmarks/src. Cloning into '/home/eyang/.rally/benchmarks/src'... remote: Counting objects: 768220, done. remote: Compressing objects: 100% (91/91), done. remote: Total 768220 (delta 42), reused 3 (delta 3), pack-reused 768122 Receiving objects: 100% (768220/768220), 322.37 MiB | 800.00 KiB/s, done. Resolving deltas: 100% (424894/424894), done. Checking connectivity... done. [FAILED] [ERROR] Cannot race. Executing '/home/gradle/gradle-3.4.1/bin/gradle clean' failed. The last 20 lines in the build log file are: ``` > Could not GET 'https://repo1.maven.org/maven2/org/apache/rat/apache-rat/0.11/apache-rat-0.11.pom'. > Connect to repo1.maven.org:443 [repo1.maven.org/151.101.40.209] failed: Connection timed out (Connection timed out) > Could not resolve ru.vyarus:gradle-animalsniffer-plugin:1.2.0. Required by: project : > Could not resolve ru.vyarus:gradle-animalsniffer-plugin:1.2.0. > Could not get resource 'https://jcenter.bintray.com/ru/vyarus/gradle-animalsniffer-plugin/1.2.0/gradle-animalsniffer-plugin-1.2.0.pom'. > Could not GET 'https://jcenter.bintray.com/ru/vyarus/gradle-animalsniffer-plugin/1.2.0/gradle-animalsniffer-plugin-1.2.0.pom'. > Connect to jcenter.bintray.com:443 [jcenter.bintray.com/54.148.163.235, jcenter.bintray.com/52.24.162.39] failed: Connection timed out (Connection timed out) > Could not resolve ru.vyarus:gradle-animalsniffer-plugin:1.2.0. > Could not get resource 'https://repo1.maven.org/maven2/ru/vyarus/gradle-animalsniffer-plugin/1.2.0/gradle-animalsniffer-plugin-1.2.0.pom'. > Could not GET 'https://repo1.maven.org/maven2/ru/vyarus/gradle-animalsniffer-plugin/1.2.0/gradle-animalsniffer-plugin-1.2.0.pom'. > Connect to repo1.maven.org:443 [repo1.maven.org/151.101.40.209] failed: Connection timed out (Connection timed out) * Try: Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. BUILD FAILED Total time: 53 mins 16.206 secs ``` ========================================================================================================= The full build log is available at [/home/eyang/.rally/benchmarks/races/2017-03-20-20-24-57/local/logs/build.log]. Getting further help: * * * - Check the log file at /home/eyang/.rally/logs/rally\_out.log for errors. - Read the documentation at [https://esrally.readthedocs.io/en/0.5.2/](https://esrally.readthedocs.io/en/0.5.2/) - Ask a question in the forum at [https://discuss.elastic.co/c/elasticsearch/rally](https://discuss.elastic.co/c/elasticsearch/rally) - Raise an issue at [https://github.com/elastic/rally/issues](https://github.com/elastic/rally/issues) and include the log file in /home/eyang/.rally/logs/rally\_out.log. * * * ## [INFO] FAILURE (took 3623 seconds) **Any clues as what was the issue?** thanks Eugene ---
**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:** [March 27, 2017, 7:44am UTC](https://discuss.elastic.co/t/run-rally-custom-track-got-gradle-clean-failed-error/79317/2 "2017-03-27T07:44:34Z")
Hi @Eugene22, based on the logs the problem is that your machine seems not be able to connect to the Internet while building Elasticsearch from sources (and it seems it is intentional as you also specified `--offline`). If you want to benchmark a released version of Elasticsearch it is also not necessary that you build it from sources. You can just specify `--distribution-version=5.1.2`. However, Rally will want to download the distribution for you if it is not already available locally in `~/.rally/benchmarks/distributions/` as a `.tar.gz`. I see that in your setup there are two machines involved: `172.20.115.95` and `172.20.115.97`. To run your benchmark, do the following: On 172.20.115.95 (coordinator node): 1. `esrallyd start --node-ip=172.20.115.95 --coordinator-ip=172.20.115.95` On 172.20.115.97 (target node where Elasticsearch will run later): 1. `esrallyd start --node-ip=172.20.115.97 --coordinator-ip=172.20.115.95` 2. Ensure that Elasticsearch 5.1.2 is available in `~/.rally/benchmarks/distributions/` e.g. by downloading it on another machine and `scp`ing it to the target server. Then you can start the benchmark on the coordinator node: `esrally --distribution-version=5.1.2 --track=spectre --target-hosts=172.20.115.97:9200 --offline --report-file=spectre-2017-03-20-13 --report-format=csv` Daniel ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 24, 2017, 7:44am UTC](https://discuss.elastic.co/t/run-rally-custom-track-got-gradle-clean-failed-error/79317/3 "2017-04-24T07:44:59Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.