# Enabling debug logging for node client discovery

**URL:** <https://discuss.elastic.co/t/enabling-debug-logging-for-node-client-discovery/20938>\
**Category:** Elasticsearch\
**Created:** [November 25, 2014, 3:19pm UTC](https://discuss.elastic.co/t/enabling-debug-logging-for-node-client-discovery/20938 "2014-11-25T15:19:22Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![raidex](https://avatars.discourse-cdn.com/v4/letter/r/db5fbb/32.png) [@raidex](https://discuss.elastic.co/u/raidex)\
**Post date:** [November 25, 2014, 3:19pm UTC](https://discuss.elastic.co/t/enabling-debug-logging-for-node-client-discovery/20938/1 "2014-11-25T15:19:22Z")

</div>

Hi all --

Can anyone point out how one can enable debug-level logging for discovery  
on a standalone client using the Node client? I have the following code,  
trying to join a single-node remote cluster. The discovery times out after  
30 seconds (yet transport works fine, and starting a bootstrapped ES node  
on this same host with master=false, data=false works perfectly).

val settings = ImmutableSettings.settingsBuilder().  
put("discovery.zen.ping.multicast.enabled", false).  
put("node.data","false").  
put("node.master","false").  
put("discovery.zen.ping.unicast.hosts ", "myeshost").  
build

val node = nodeBuilder().  
loadConfigSettings(false).  
settings(settings).  
client(true).  
node.  
start

But this only results in:

...  
[run-main-0] INFO org.elasticsearch.node - [Hebe] starting ...  
[run-main-0] INFO org.elasticsearch.transport - [Hebe] bound\_address  
{inet[/0.0.0.0:9301]}, publish\_address {inet[/10.60.35.37:9301]}  
[run-main-0] WARN org.elasticsearch.discovery - [Hebe] waited for 30s and  
no initial state was set by the discovery  
...

I found this doc article  
[http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/logging.html](http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/logging.html) talking  
about dynamic changes to logger.discovery values, but this likely doesn't  
work on a standalone client since discovery happens well before the HTTP  
listener is started to even receive the update request. Adding  
'put("logger.discovery","DEBUG")' to the settings builder above didn't  
help either.

Any pointers are sincerely appreciated.

--  
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/da615b1f-c749-4a00-aaf6-cd0c20cf39c9%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/da615b1f-c749-4a00-aaf6-cd0c20cf39c9%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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:** [July 6, 2017, 12:47am UTC](https://discuss.elastic.co/t/enabling-debug-logging-for-node-client-discovery/20938/2 "2017-07-06T00:47:44Z")

</div>


