Re: [Logging] searchguard configuration issue? ["warning", "elasticsearch"], "pid":1, "message":"Unable to revive connection: https://logging-es:9200/"}

2017-07-12 Thread Stéphane Klein
2017-07-12 15:41 GMT+02:00 Peter Portante : > > > On Wed, Jul 12, 2017 at 9:28 AM, Stéphane Klein < > cont...@stephane-klein.info> wrote: > >> >> 2017-07-12 15:20 GMT+02:00 Peter Portante : >> >>> This looks a lot like this BZ: https://bugzilla.redhat.co

Re: [Logging] searchguard configuration issue? ["warning", "elasticsearch"], "pid":1, "message":"Unable to revive connection: https://logging-es:9200/"}

2017-07-12 Thread Peter Portante
On Wed, Jul 12, 2017 at 9:28 AM, Stéphane Klein wrote: > > 2017-07-12 15:20 GMT+02:00 Peter Portante : > >> This looks a lot like this BZ: https://bugzilla.redhat.co >> m/show_bug.cgi?id=1449378, "Timeout after 30SECONDS while retrieving >>

Re: [Logging] searchguard configuration issue? ["warning", "elasticsearch"], "pid":1, "message":"Unable to revive connection: https://logging-es:9200/"}

2017-07-12 Thread Stéphane Klein
2017-07-12 15:20 GMT+02:00 Peter Portante : > This looks a lot like this BZ: https://bugzilla.redhat. > com/show_bug.cgi?id=1449378, "Timeout after 30SECONDS while retrieving > configuration" > > What version of Origin are you using? > > Logging image :

Re: [Logging] searchguard configuration issue? ["warning", "elasticsearch"], "pid":1, "message":"Unable to revive connection: https://logging-es:9200/"}

2017-07-12 Thread Peter Portante
This looks a lot like this BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1449378, "Timeout after 30SECONDS while retrieving configuration" What version of Origin are you using? I found that I had to run the sgadmin script in each ES pod at the same time, and when one succeeds and one fails,

[Logging] searchguard configuration issue? ["warning", "elasticsearch"], "pid":1, "message":"Unable to revive connection: https://logging-es:9200/"}

2017-07-12 Thread Stéphane Klein
Hi, Since one day, after ES cluster pods restart, I have this error message when I launch logging-es: $ oc logs -f logging-es-ne81bsny-5-jdcdk Comparing the specificed RAM to the maximum recommended for ElasticSearch... Inspecting the maximum RAM available... ES_JAVA_OPTS: