Hi kluch,
all Graylog server nodes in a cluster must use the same password_secret (and
application.secret for the web interface) which is, among other things,
being used to encrypt and decrypt the LDAP credentials in MongoDB.
Cheers,
Jochen
On Friday, 18 March 2016 13:12:14 UTC+1, kluch wrote:
>
> W dniu czwartek, 17 marca 2016 22:07:49 UTC+1 użytkownik Mike Daoust
> napisał:
>>
>> I dont know for sure if this will help, but what I would look at is that
>> all 3 nodes server.conf have the same hashed password as the web.conf
>>
>> I've checked hashed password for all 3 nodes and:
> 1. fields named "root_password_sha2" in graylog.conf are exactly the same
> on all 3 nodes,
> 2. fields "password_secret" in graylog.conf are different on all 3 nodes,
> 3. fields in graylog-web-interface.conf named "application.secret" are
> also different on all nodes.
> Should the "password_secret" and "application.secret" be the same on all 3
> nodes in cluster?
> PS. I also did some exploration (I've upgraded to 1.3.4 too):
> shutdown node 2 and 3 and setup ldap (login OK via node 1).
> started node 2, shutdown node 1, setup ldap (login OK via node 2),
> started node 1 so there were 2 nodes online and it occured that settings
> were ERASED(!?) from node1 and when I browse API on port
> 12900/system/ldap/settings I can only find
> {"type":"ApiError","message":"Null systemPassword"} instead od ldap
> settings.
> So I looks like there is a bug in Graylog 1.3.x when using AD and clusters.
>
>
--
You received this message because you are subscribed to the Google Groups
"Graylog Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/graylog2/52e37778-a8e5-4c79-a2a9-b992ab3d3dce%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
