# Cluster provision and benchmark stalls using Rally **URL:** \ **Category:** Elasticsearch\ **Tags:** rally\ **Created:** [March 12, 2020, 1:19am UTC](https://discuss.elastic.co/t/cluster-provision-and-benchmark-stalls-using-rally/223231 "2020-03-12T01:19:30Z")\ **Posts on this page:** 1\ **Showing post:** 6
**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:** [March 13, 2020, 4:58pm UTC](https://discuss.elastic.co/t/cluster-provision-and-benchmark-stalls-using-rally/223231/6 "2020-03-13T16:58:12Z")
@palani Can you add debug logging? Just `"level": "INFO"` to `"level": "DEBUG"` in your `~/.rally/logging.json`, rerun and share `~/.rally/logs/rally.log`. One other test, to verify connectivity: Ensure all rally/rallyd processes are killed on all vms. Then on target vms `vm-2` and `vm-4` run: `nc -k -v -l 1900` On the coordinator `vm-1` run: `printf "message from coordinator to vm-2\n" | nc 10.156.129.121 1900` `printf "message from coordinator to vn-4\n" | nc 10.156.129.169 1900` You should see both messages from the coordinator on the target nodes. --- _[View the full topic](https://discuss.elastic.co/t/cluster-provision-and-benchmark-stalls-using-rally/223231)._