[graylog2] Re: [IndexerSetupService] Could not connect to Elasticsearch. [IndexerSetupService] If you're using multicast, check that it is working in your network and that Elasticsearch is accessible.

16 13:51:11 UTC+1, Dylan Humphreys wrote: >> >> elasticsearch_discovery_zen_ping_unicast_hosts >> >> Actually does, if (as it appears) its not for pointing graylog at the >> address(es) of the elasticsearch cluster. >> > > That is exactly what

[graylog2] Re: [IndexerSetupService] Could not connect to Elasticsearch. [IndexerSetupService] If you're using multicast, check that it is working in your network and that Elasticsearch is accessible.

ch > configuration and read > http://docs.graylog.org/en/2.1/pages/configuration/elasticsearch.html#configuration > > for more details. > > Cheers, > Jochen > > On Thursday, 24 November 2016 16:29:57 UTC+1, Dylan Humphreys wrote: >> >> Yes, its this one again.

[graylog2] [IndexerSetupService] Could not connect to Elasticsearch. [IndexerSetupService] If you're using multicast, check that it is working in your network and that Elasticsearch is accessible.

Yes, its this one again. Sadly none of the other cases of this seem to fix my problem, although I have an idea of where things are going wrong. bddvgl1:~ # dpkg -l elasticsearch graylog-server | grep ii | awk '{print $1,$2,$3}' ii elasticsearch 2.3.5 ii graylog-server 2.1.2-1 bddvgl1:~ # My

[graylog2] Re: threw an exception during a multi-realm authentication attempt: java.lang.IllegalArgumentException: Odd number of characters.

56 hash seems > to be invalid. It has to be exactly 64 characters long (the hexadecimal > representation of a 256-bit value). > > Cheers, > Jochen > > On Thursday, 3 November 2016 16:32:18 UTC+1, Dylan Humphreys wrote: >> >> Hi Everyone, >> graylog 2.1

[graylog2] threw an exception during a multi-realm authentication attempt: java.lang.IllegalArgumentException: Odd number of characters.

Hi Everyone, graylog 2.1.1-2 on debian 8, elasticsearch 2.4.1 and mongo 2.6.12 manual install. I have set password_secret = qBbUBsZDwL9... and root_password_sha2 = 240be518fa... Using the commands mentioned in server.conf, however whenever I try and login using the web interface I get this i

[graylog2] java.security.cert.CertificateParsingException: signed fields invalid with client TLS

Hi Everyone Im trying to setup syslog tcp input with TLS support with client TLS authentication I have succesfuly setup TLS on the graylog side only, and clients (syslog-ng) can connect and submit logging information as expected. However when I try and enable client side TLS auth, I get this exce