# Transport is not up and running in 3 node cluster 6.8.0
**URL:** https://discuss.elastic.co/t/transport-is-not-up-and-running-in-3-node-cluster-6-8-0/188381
**Category:** Elasticsearch
**Created:** [July 1, 2019, 6:01pm UTC](https://discuss.elastic.co/t/transport-is-not-up-and-running-in-3-node-cluster-6-8-0/188381 "2019-07-01T18:01:20Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@Balamurugan\_Sethuram](https://discuss.elastic.co/u/Balamurugan_Sethuram)
#### Post date: [July 1, 2019, 6:01pm UTC](https://discuss.elastic.co/t/transport-is-not-up-and-running-in-3-node-cluster-6-8-0/188381/1 "2019-07-01T18:01:20Z")
Hi,
I have 3 node cluster, and my elasticsearch.yml
# ----------------------------------- Node -------------------------------------
node.name: "machine1"
node.master: true
node.data: true
search.remote.connect: true
#---------------------------------- Network ------------------------------------
network.host: "10.198.238.142"
http.port: "9200"
transport.tcp.port: "9301"
....
....
# --------------------------------- Discovery ---------------------------------
discovery.zen.ping.unicast.hosts:
- "10.198.238.142:9301"
- "10.198.238.4:9301"
- "10.198.238.6:9301"
discovery.zen.minimum\_master\_nodes: 3
bootstrap.memory\_lock: true
Wrote a playbook to elastic stop and stop via systemctl commands. only 1 node comes back with transport port on 9300 or 9301.
But another 2 nodes are not up with transport port.
fatal: [machine2]: FAILED! =\> {
"changed": false,
"elapsed": 300
}
MSG:
Timeout when waiting for 10.198.238.4:9301
fatal: [machine3]: FAILED! =\> {
"changed": false,
"elapsed": 300
}
MSG:
Timeout when waiting for 10.198.238.6:9301
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 29, 2019, 6:01pm UTC](https://discuss.elastic.co/t/transport-is-not-up-and-running-in-3-node-cluster-6-8-0/188381/2 "2019-07-29T18:01:25Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.