# Running Two nodes on a single Server (RH) - ES 2.3.3 **URL:** \ **Category:** Elasticsearch\ **Created:** [June 29, 2016, 3:02pm UTC](https://discuss.elastic.co/t/running-two-nodes-on-a-single-server-rh-es-2-3-3/54299 "2016-06-29T15:02:38Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![mark.ricci](https://avatars.discourse-cdn.com/v4/letter/m/0ea827/32.png) [@mark.ricci](https://discuss.elastic.co/u/mark.ricci)\ **Post date:** [June 29, 2016, 3:02pm UTC](https://discuss.elastic.co/t/running-two-nodes-on-a-single-server-rh-es-2-3-3/54299/1 "2016-06-29T15:02:38Z")
I'm trying to run two ES nodes on a single cluster on the same server. I have two config files located in separate directories: elasticsearch-2.3.3/config/node1 elasticsearch-2.3.3/config/node2 Each node-# folder contains a config file. When I startup each node it is not taking the hostname/node name values in the config file. It is defaulting to the Marvel comic name for each node. It does appear to take the port #'s I'm assigning for transport and listening. /opt/ElasticSearch/elasticsearch-2.3.3/bin/elasticsearch -Des.path.conf=/opt/ElasticSearch/elasticsearch-2.3.3/config/node-1 /opt/ElasticSearch/elasticsearch-2.3.3/bin/elasticsearch -Des.path.conf=/opt/ElasticSearch/elasticsearch-2.3.3/config/node-2 starting up node-1 results: [2016-06-29 14:53:32,071][WARN][bootstrap] unable to install syscall filter: seccomp unavailable: CONFIG\_SECCOMP not compiled into kernel, CONFIG\_SECCOMP and CONFIG\_SECCOMP\_FILTER are needed [2016-06-29 14:53:32,192][INFO][node] [Psyche] version[2.3.3], pid[3030], build[218bdf1/2016-05-17T15:40:04Z] [2016-06-29 14:53:32,192][INFO][node] [Psyche] initializing ... [2016-06-29 14:53:32,644][INFO][plugins] [Psyche] modules [reindex, lang-expression, lang-groovy], plugins [], sites [] [2016-06-29 14:53:32,663][INFO][env] [Psyche] using [1] data paths, mounts [[/opt/ElasticSearch (/dev/mapper/1t-clear)]], net usable\_space [955.5gb], net total\_space [1006.8gb], spins? [possibly], types [ext4] [2016-06-29 14:53:32,664][INFO][env] [Psyche] heap size [989.8mb], compressed ordinary object pointers [true] [2016-06-29 14:53:32,664][WARN][env] [Psyche] max file descriptors [4096] for elasticsearch process likely too low, consider increasing to at least [65536] [2016-06-29 14:53:34,127][INFO][node] [Psyche] initialized [2016-06-29 14:53:34,127][INFO][node] [Psyche] starting ... [2016-06-29 14:53:34,185][INFO][transport] [Psyche] publish\_address {127.0.0.1:9300}, bound\_addresses {[::1]:9300}, {127.0.0.1:9300} [2016-06-29 14:53:34,189][INFO][discovery] [Psyche] elasticsearch/dfmNmn1xTiumZ\_GdnJiYAw [2016-06-29 14:53:37,248][INFO][cluster.service] [Psyche] new\_master {Psyche}{dfmNmn1xTiumZ\_GdnJiYAw}{127.0.0.1}{127.0.0.1:9300}, reason: zen-disco-join(elected\_as\_master, [0] joins received) [2016-06-29 14:53:37,284][INFO][http] [Psyche] publish\_address {127.0.0.1:9200}, bound\_addresses {[::1]:9200}, {127.0.0.1:9200} [2016-06-29 14:53:37,284][INFO][node] [Psyche] started [2016-06-29 14:53:37,341][INFO][gateway] [Psyche] recovered [0] indices into cluster\_state ^C^C[2016-06-29 14:53:43,766][INFO][node] [Psyche] stopping ... [2016-06-29 14:53:43,783][INFO][node] [Psyche] stopped [2016-06-29 14:53:43,783][INFO][node] [Psyche] closing ... [2016-06-29 14:53:43,791][INFO][node] [Psyche] closed If I run a single elastic command with the default path for config, data, logs etc. it starts up with the correct node name, directories and I can hit the 9200 port via browser. Node-1 config values: [cluster.name](http://cluster.name): ES\_US-East\_Cluster\_Dev-1 [node.name](http://node.name): "ES\_\_US-East\_Node-1\_Dev-1" network.host: els-mstr-1 network.bind\_host: 10.x.x.x network.publish\_host: 10.x.x.x http.port: 9200 transport.tcp.port: 9300 ---
**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\ **Post date:** [July 4, 2016, 8:38am UTC](https://discuss.elastic.co/t/running-two-nodes-on-a-single-server-rh-es-2-3-3/54299/2 "2016-07-04T08:38:21Z")
Hey, nothing of your config file is actually applied. The service is also bound to 127.0.0.1. Are you sure the file is picked up? Do you have any prefixed tabs or spaces in the config file? --Alex ---
**Author:** ![mark.ricci](https://avatars.discourse-cdn.com/v4/letter/m/0ea827/32.png) [@mark.ricci](https://discuss.elastic.co/u/mark.ricci)\ **Post date:** [July 5, 2016, 8:04pm UTC](https://discuss.elastic.co/t/running-two-nodes-on-a-single-server-rh-es-2-3-3/54299/3 "2016-07-05T20:04:01Z")
Got it working because it isn't explicitly stated that the config files for multi-nodes configs on a single server can be in different folders but have to be named elasticsearch.yml for it to be recognized. I have named my config files els-node-1.yml and els-node-2.yml. Changed the names to elasticsearch.yml and they were recognized. ---
**Author:** ![mark.ricci](https://avatars.discourse-cdn.com/v4/letter/m/0ea827/32.png) [@mark.ricci](https://discuss.elastic.co/u/mark.ricci)\ **Post date:** [July 11, 2016, 7:23pm UTC](https://discuss.elastic.co/t/running-two-nodes-on-a-single-server-rh-es-2-3-3/54299/4 "2016-07-11T19:23:43Z")
The second node isn't connecting to the cluster which is run by the first node that I have set as master. At startup, it pulls the cluster name from it's config file but say this: [2016-07-11 19:17:31,026][INFO][discovery] [Node-2\_Dev-1] Cluster\_Dev-1/y4BStusNhOv1yP9Sw [2016-07-11 19:18:01,029][WARN][discovery] [Node-2\_Dev-1] waited for 30s and no initial state was set by the discovery ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 10:36pm UTC](https://discuss.elastic.co/t/running-two-nodes-on-a-single-server-rh-es-2-3-3/54299/5 "2017-07-05T22:36:28Z")