Skip to content
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

Closed
evrardjp opened this issue Apr 2, 2018 · 9 comments · Fixed by #181
Closed

This role doesn't work for production deploys #89

evrardjp opened this issue Apr 2, 2018 · 9 comments · Fixed by #181

Comments

@evrardjp
Copy link

evrardjp commented Apr 2, 2018

I've noticed this isn't production ready deployment of graylog:

  • There are assumptions in the role that software runs on localhost (I have PR to fix that for one part, but others like mongodb are still under the assumption of localhost)
  • Even when ignoring the tests of localhost, the deploy doesn't work in multi-node.
    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.
@evrardjp
Copy link
Author

evrardjp commented Apr 2, 2018

FYI I'm building a PoC integration of graylog for OpenStack clusters deployed with OpenStack-Ansible. Bridging communities would be great.

@evrardjp
Copy link
Author

evrardjp commented Apr 6, 2018

Is there someone here that can help at pointing me to the why of the authentication failure?

@mariussturm
Copy link
Contributor

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.

@evrardjp
Copy link
Author

evrardjp commented Apr 6, 2018

Thanks. So that's mongo DB the factor here.
I will have a look at the role to know why the mongo DB isn't clustered by default when running the role on multiple nodes.

@mariussturm
Copy link
Contributor

That's currently not implemented by this role (and actually not so easy to do).

@evrardjp
Copy link
Author

evrardjp commented Apr 6, 2018

I know the feeling :)

@malcyon
Copy link
Contributor

malcyon commented Nov 12, 2021

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.

@evrardjp
Copy link
Author

I would give hugs on that last thing, but I know it's not covid safe. In the meantime, thanks @malcyon !

@malcyon
Copy link
Contributor

malcyon commented Nov 15, 2021

My pleasure!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants