# Not able to execute rally track as many process running already

**URL:** <https://discuss.elastic.co/t/not-able-to-execute-rally-track-as-many-process-running-already/222899>\
**Category:** Elasticsearch\
**Tags:** rally\
**Created:** [March 10, 2020, 9:43am UTC](https://discuss.elastic.co/t/not-able-to-execute-rally-track-as-many-process-running-already/222899 "2020-03-10T09:43:13Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![jbaskaran\_123](https://avatars.discourse-cdn.com/v4/letter/j/8e7dd6/32.png) [@jbaskaran\_123](https://discuss.elastic.co/u/jbaskaran_123)\
**Post date:** [March 10, 2020, 9:43am UTC](https://discuss.elastic.co/t/not-able-to-execute-rally-track-as-many-process-running-already/222899/1 "2020-03-10T09:43:13Z")

</div>

Hi,  
I have a single node elasticsearch cluster in a kubernetes cluster.  
Also Rally installed in a separate docker container in same namespace where ES is running.

I am able to run default track "geonames" and test completed successfully against the Es cluster.  
But not able to export the result to csv file. Also after the below error comes, not able to execute any other test tracks.

Test:  
esrally --track=geonames --target-hosts=17.99.251.106:9200 --pipeline=benchmark-only

Error:  
[ERROR] Cannot race. There are other Rally processes running on this machine (PIDs: [52, 53, 75, 96, 98, 100, 101]) but only one Rally benchmark is allowed to run at the same time. Please check and terminate these processes and retry again.

Please help me on this.

---

<div class="post-metadata">

**Author:** ![baz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/baz/32/5183_2.png) [@baz](https://discuss.elastic.co/u/baz)\
**Post date:** [March 10, 2020, 3:32pm UTC](https://discuss.elastic.co/t/not-able-to-execute-rally-track-as-many-process-running-already/222899/2 "2020-03-10T15:32:06Z")

</div>

Those existing rally processes typically mean that a rally run is executing currently, or a rally run was not shut down properly. You should be able to just `kill` the processes and rerun your benchmark.

If you find this is reproducible without you shutting down rally improperly, it very well could indicate a bug.

---

<div class="post-metadata">

**Author:** ![jbaskaran\_123](https://avatars.discourse-cdn.com/v4/letter/j/8e7dd6/32.png) [@jbaskaran\_123](https://discuss.elastic.co/u/jbaskaran_123)\
**Post date:** [March 11, 2020, 1:27pm UTC](https://discuss.elastic.co/t/not-able-to-execute-rally-track-as-many-process-running-already/222899/3 "2020-03-11T13:27:57Z")

</div>

I tried killing the process by using below.

## ps -ef kill pid

# ps -ef

PID USER TIME COMMAND  
1 root 0:00 python3  
6 root 0:00 sh  
38 root 0:00 [esrally]  
39 root 0:00 [esrally]  
40 root 0:00 [esrally]  
41 root 0:00 {esrally} /usr/local/bin/python /usr/local/bin/esrally --track=geonames --track-params=bulk\_size:10000,clients:20 --target-hosts=_**:9200 --pipeline  
62 root 0:00 [esrally]  
63 root 0:02 {esrally} /usr/local/bin/python /usr/local/bin/esrally --track=geonames --track-params=bulk\_size:10000,clients:20 --target-hosts=**_:9200 --pipeline  
64 root 0:57 {esrally} /usr/local/bin/python /usr/local/bin/esrally --track=geonames --track-params=bulk\_size:10000,clients:20 --target-hosts=\*\*\*\*\*:9200 --pipeline  
85 root 0:00 sh  
92 root 0:00 ps -ef

* * *

But it seems to be processes are not getting killed.  
Please let me know how to kill the running esrally processes inside a docker container.

---

<div class="post-metadata">

**Author:** ![baz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/baz/32/5183_2.png) [@baz](https://discuss.elastic.co/u/baz)\
**Post date:** [March 12, 2020, 5:17pm UTC](https://discuss.elastic.co/t/not-able-to-execute-rally-track-as-many-process-running-already/222899/4 "2020-03-12T17:17:24Z")

</div>

> Please let me know how to kill the running esrally processes inside a docker container.

Killing a rally process in docker is no different from killing any process in docker. There are some suggestions [here from a quick google search](https://stackoverflow.com/questions/27757405/how-to-kill-process-inside-container-docker-top-command).

You may want to also `kill -9` the processes.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [April 9, 2020, 5:17pm UTC](https://discuss.elastic.co/t/not-able-to-execute-rally-track-as-many-process-running-already/222899/5 "2020-04-09T17:17:28Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
