# Evaluating Search Guard - How to enable debug lo level. **URL:** \ **Category:** Search Guard\ **Created:** [February 8, 2019, 4:19am UTC](https://forum.search-guard.com/t/evaluating-search-guard-how-to-enable-debug-lo-level/1322 "2019-02-08T04:19:11Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![vigneshwar.rajkumar](https://avatars.discourse-cdn.com/v4/letter/v/bb73d2/32.png) [@vigneshwar.rajkumar](https://forum.search-guard.com/u/vigneshwar.rajkumar)\ **Post date:** [February 8, 2019, 4:19am UTC](https://forum.search-guard.com/t/evaluating-search-guard-how-to-enable-debug-lo-level/1322/1 "2019-02-08T04:19:11Z")
When asking questions, please provide the following information: - Search Guard and Elasticsearch version 6.6.0. - Installed and used enterprise modules, if any - JVM version and operating system version - Search Guard configuration files - Elasticsearch log messages on debug level - Other installed Elasticsearch or Kibana plugins, if any searchguard.ssl.transport.enabled: true searchguard.ssl.transport.keystore\_filepath: local-keystore.jks searchguard.ssl.transport.truststore\_filepath: local-truststore.jks searchguard.ssl.http.enabled: true searchguard.ssl.http.keystore\_filepath: local-keystore.jks searchguard.ssl.http.truststore\_filepath: local-truststore.jks searchguard.ssl.transport.enforce\_hostname\_verification: true searchguard.ssl.transport.resolve\_hostname: true Hi, We are currently evaluating search guard. Using self signed certificates. 3 Node cluster. Using truststore in the relative path of /etc/elasticsearch and we are currently getting the below error. io.netty.handler.codec.DecoderException: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty Not sure how to enable debug logs on elasticsearch for ssl using the log4j2. ---
**Author:** ![searchguard\_google\_group](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.search-guard.com/searchguard_google_group/32/462_2.png) [@searchguard\_google\_group](https://forum.search-guard.com/u/searchguard_google_group)\ **Post date:** [February 11, 2019, 7:50am UTC](https://forum.search-guard.com/t/evaluating-search-guard-how-to-enable-debug-lo-level/1322/2 "2019-02-11T07:50:02Z")
Check that local-truststore.jks is not empty (that could be the reason for "the trustAnchors parameter must be non-empty") To enable debug see [Search Guard logging | Security for Elasticsearch | Search Guard](https://docs.search-guard.com/latest/troubleshooting-setting-log-level#turn-on-debug-logging-temporarily) > **···** > > > Am 08.02.2019 um 05:19 schrieb vigneshwar.rajkumar@piecestech.com: > > > > When asking questions, please provide the following information: > > > > \* Search Guard and Elasticsearch version 6.6.0. > > \* Installed and used enterprise modules, if any > > \* JVM version and operating system version > > \* Search Guard configuration files > > \* Elasticsearch log messages on debug level > > \* Other installed Elasticsearch or Kibana plugins, if any > > searchguard.ssl.transport.enabled: true > > searchguard.ssl.transport.keystore\_filepath: local-keystore.jks > > searchguard.ssl.transport.truststore\_filepath: local-truststore.jks > > searchguard.ssl.http.enabled: true > > searchguard.ssl.http.keystore\_filepath: local-keystore.jks > > searchguard.ssl.http.truststore\_filepath: local-truststore.jks > > searchguard.ssl.transport.enforce\_hostname\_verification: true > > searchguard.ssl.transport.resolve\_hostname: true > > > > Hi, > > We are currently evaluating search guard. Using self signed certificates. 3 Node cluster. Using truststore in the relative path of /etc/elasticsearch and we are currently getting the below error. > > > > io.netty.handler.codec.DecoderException: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty > > > > Not sure how to enable debug logs on elasticsearch for ssl using the log4j2. > > > > -- > > You received this message because you are subscribed to the Google Groups "Search Guard Community Forum" group. > > To unsubscribe from this group and stop receiving emails from it, send an email to search-guard+unsubscribe@googlegroups.com. > > To post to this group, send email to search-guard@googlegroups.com. > > To view this discussion on the web visit [https://groups.google.com/d/msgid/search-guard/8c38e381-288f-40d0-8241-2b2a4aa71606%40googlegroups.com\](https://groups.google.com/d/msgid/search-guard/8c38e381-288f-40d0-8241-2b2a4aa71606%40googlegroups.com%5C). > > For more options, visit [https://groups.google.com/d/optout\](https://groups.google.com/d/optout%5C). ---
**Author:** ![jkressin](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.search-guard.com/jkressin/32/9_2.png) [@jkressin](https://forum.search-guard.com/u/jkressin)\ **Post date:** [February 18, 2019, 10:33am UTC](https://forum.search-guard.com/t/evaluating-search-guard-how-to-enable-debug-lo-level/1322/3 "2019-02-18T10:33:31Z")
Please also follow the TLS troubleshooting guide if you run into any certificate issues: > **[TLS troubleshooting](https://docs.search-guard.com/latest/troubleshooting-tls)** > > Step-by-step instructions to troubleshoot Search Guard TLS and certificates issues > **···** > > On Friday, February 8, 2019 at 5:19:11 AM UTC+1, [vigneshwar.rajkumar@piecestech.com](mailto:vigneshwar.rajkumar@piecestech.com) wrote: > > > When asking questions, please provide the following information: > > > - Search Guard and Elasticsearch version 6.6.0. > > > - Installed and used enterprise modules, if any > > > - JVM version and operating system version > > > - Search Guard configuration files > > > - Elasticsearch log messages on debug level > > > - Other installed Elasticsearch or Kibana plugins, if any > > > searchguard.ssl.transport.enabled: true > > > searchguard.ssl.transport.keystore\_filepath: local-keystore.jks > > > searchguard.ssl.transport.truststore\_filepath: local-truststore.jks > > > searchguard.ssl.http.enabled: true > > > searchguard.ssl.http.keystore\_filepath: local-keystore.jks > > > searchguard.ssl.http.truststore\_filepath: local-truststore.jks > > > searchguard.ssl.transport.enforce\_hostname\_verification: true > > > searchguard.ssl.transport.resolve\_hostname: true > > > > > > Hi, > > > We are currently evaluating search guard. Using self signed certificates. 3 Node cluster. Using truststore in the relative path of /etc/elasticsearch and we are currently getting the below error. > > > > > > io.netty.handler.codec.DecoderException: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty > > > > > > Not sure how to enable debug logs on elasticsearch for ssl using the log4j2.