# Shield: Why do I get timeout on my own node **URL:** \ **Category:** Elasticsearch\ **Created:** [February 12, 2015, 8:41pm UTC](https://discuss.elastic.co/t/shield-why-do-i-get-timeout-on-my-own-node/22143 "2015-02-12T20:41:04Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Jettro\_Coenradie](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jettro_coenradie/32/59704_2.png) [@Jettro\_Coenradie](https://discuss.elastic.co/u/Jettro_Coenradie)\ **Post date:** [February 12, 2015, 8:41pm UTC](https://discuss.elastic.co/t/shield-why-do-i-get-timeout-on-my-own-node/22143/1 "2015-02-12T20:41:04Z")
Hi I am trying to create a cluster that is secured on a number of raspberry pi's. If I start just one node with the following config I get a timeout to that same node. So it is trying to ping itself and that does not work. Any ideas? Config: cluster.name: jc-mypi node.name: jc-pi-red marvel.agent.indices: my\* marvel.agent.interval: 10s marvel.agent.enabled: false shield.audit.enabled: true shield.ssl.keystore.path: /etc/elasticsearch/jcpi.jks shield.ssl.keystore.password: geheim shield.transport.ssl: true discovery.zen.ping.multicast.enabled: false discovery.zen.ping.unicast.hosts: ["192.168.1.11:9300", "192.168.1.12:9300"] In the log: [2015-02-12 21:36:40,078][WARN][shield.transport] [jc-pi-red] Received response for a request that has timed out, sent [21455ms] ago, timed out [17704ms] ago, action [internal:discovery/zen/unicast], node [[jc-pi-red][o4b8he9qQFiSzBV3ckkF1Q][jc-pi-red][inet[192.168.1.10/192.168.1.10:9300]]], id [0] Thanks -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/791792bc-9ee3-48ca-9f61-e2bd71952cc9%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/791792bc-9ee3-48ca-9f61-e2bd71952cc9%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Jettro\_Coenradie](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jettro_coenradie/32/59704_2.png) [@Jettro\_Coenradie](https://discuss.elastic.co/u/Jettro_Coenradie)\ **Post date:** [February 13, 2015, 7:57am UTC](https://discuss.elastic.co/t/shield-why-do-i-get-timeout-on-my-own-node/22143/2 "2015-02-13T07:57:22Z")
As pointed out by Jay Modi when discussing another question I had, this is a timeout issue. The pi's do not have a lot of processing power and adding ssl is to heavy for the pi. Upgrading the timeout to 30 seconds did help. On Thu, Feb 12, 2015 at 9:41 PM, Jettro Coenradie \< [jettro.coenradie@gmail.com](mailto:jettro.coenradie@gmail.com)\> wrote: > Hi I am trying to create a cluster that is secured on a number of > raspberry pi's. If I start just one node with the following config I get a > timeout to that same node. So it is trying to ping itself and that does not > work. Any ideas? > > Config: > cluster.name: jc-mypi > node.name: jc-pi-red > marvel.agent.indices: my\* > marvel.agent.interval: 10s > marvel.agent.enabled: false > shield.audit.enabled: true > shield.ssl.keystore.path: /etc/elasticsearch/jcpi.jks > shield.ssl.keystore.password: geheim > shield.transport.ssl: true > discovery.zen.ping.multicast.enabled: false > discovery.zen.ping.unicast.hosts: ["192.168.1.11:9300", "192.168.1.12:9300 > "] > > In the log: > > [2015-02-12 21:36:40,078][WARN][shield.transport] [jc-pi-red] > Received response for a request that has timed out, sent [21455ms] ago, > timed out [17704ms] ago, action [internal:discovery/zen/unicast], node > [[jc-pi-red][o4b8he9qQFiSzBV3ckkF1Q][jc-pi-red][inet[ > 192.168.1.10/192.168.1.10:9300]] > [http://192.168.1.10/192.168.1.10:9300]]](http://192.168.1.10/192.168.1.10:9300%5D%5D)], id [0] > > Thanks > > -- > You received this message because you are subscribed to a topic in the > Google Groups "elasticsearch" group. > To unsubscribe from this topic, visit > [https://groups.google.com/d/topic/elasticsearch/9B3K7\_J-hCg/unsubscribe](https://groups.google.com/d/topic/elasticsearch/9B3K7_J-hCg/unsubscribe). > To unsubscribe from this group and all its topics, send an email to > [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/791792bc-9ee3-48ca-9f61-e2bd71952cc9%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/791792bc-9ee3-48ca-9f61-e2bd71952cc9%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/791792bc-9ee3-48ca-9f61-e2bd71952cc9%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/791792bc-9ee3-48ca-9f61-e2bd71952cc9%40googlegroups.com?utm_medium=email&utm_source=footer) > . > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- Jettro Coenradie > **[Gridshore](https://www.gridshore.nl/)** > > A weblog about software engineering, Architecture, Technology an other things we like. -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CABB4caPD3X9U9A%3DT\_JirRA5nocanu-WfarJU6X%2BepHyLj0i5UA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CABB4caPD3X9U9A%3DT_JirRA5nocanu-WfarJU6X%2BepHyLj0i5UA%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 12:33am UTC](https://discuss.elastic.co/t/shield-why-do-i-get-timeout-on-my-own-node/22143/3 "2017-07-06T00:33:01Z")
Closed on July 6, 2017, 12:33am UTC