New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This role doesn't work for production deploys #89
Comments
FYI I'm building a PoC integration of graylog for OpenStack clusters deployed with OpenStack-Ansible. Bridging communities would be great. |
Is there someone here that can help at pointing me to the |
Sounds like your Graylog servers doesn't share one MongoDB instance. In that case they all run there own local database with own authentication data. Try to change the Mongo URL so that all servers point to one instance. |
Thanks. So that's mongo DB the factor here. |
That's currently not implemented by this role (and actually not so easy to do). |
I know the feeling :) |
I added a cluster example to the README. Hopefully, this suits people's needs. It is not perfect, but it does set up a MongoDB replica set, and gives a good idea of how to go about the whole thing. |
I would give hugs on that last thing, but I know it's not covid safe. In the meantime, thanks @malcyon ! |
My pleasure! |
I've noticed this isn't production ready deployment of graylog:
I've followed this: http://docs.graylog.org/en/2.4/pages/configuration/web_interface.html#using-a-layer-3-load-balancer-forwarding-tcp-ports . But the only way I can reach a page after authentication on the graylog web interface is to put 2 of my 3 servers into maintenance mode in my Load Balancer. I suspect that the authentication information are not shared between backends.
The text was updated successfully, but these errors were encountered: