Hi Joshua, on the appliances MongoDB runs without a configuration file. Settings are given by command line options. If you want to change something you can add or delete options in the start script of MongoDB: /opt/graylog/service/mongodb/run
Afterwards restart the service. I think your confusion comes from the pre-build Graylog appliance. The setup is fundamentally different than what is explained in the Graylog installation documentation. The appliance is not just a VM with an installed Graylog, dumped into a file. It's an own world with special toolings. Making it easy for new users to get everything running and play around with the different operating modes of Graylog. To reach that the graylog-ctl command is rendering all configuration files for you (this is also the reason for redundant configurations in YAML format). You provide as little informations as possible and the appliance will create a working setup for you. The downside is that you can't just edit some files here and there and fiddle around until you reach the state you are looking for. The graylog-ctl command will reset your changes on the next 'reconfigure' run. Long story short either you pick an appliance installation and everything is prepared for you (with some limitations) or you manually install a server with Graylog and that one will follow you own installation rules and standards. Cheers, Marius On 13 December 2016 at 15:50, Joshua Waclawski <jbwaclaw...@gmail.com> wrote: > Hey Jochen, > > Looks like you may be at least partially correct, my apologies for the > confusion on this. That section does point to most of the configuration > files, I still need access to change configurations of MongoDB to close up > some pretty problematic security holes. That documentation is telling me > that the settings for mongodb are stored in the graylog-settings.json file > in /etc/graylog; I checked this file and don't see any mongo specific > settings. Is it as simple as adding the mongo configuration keys and values > here and restarting graylog? > > On Sunday, December 11, 2016 at 6:53:34 AM UTC-5, Jochen Schalanda wrote: >> >> Hi Joshua, >> >> On Saturday, 10 December 2016 19:27:40 UTC+1, Joshua Waclawski wrote: >>> >>> As I mentioned in my previous post, that documentation is incorrect when >>> using the EC2-AMI's provided on the graylog website. Here's some examples... >> >> >> I think you've been looking at the wrong section of the documentation. The >> paths in the AMIs are identical to the ones used in the OVA (because both >> are based on the Omnibus package, just as the comment in the documentation >> states): >> http://docs.graylog.org/en/2.1/pages/configuration/file_location.html#omnibus-package >> >> Cheers, >> Jochen > > -- > 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 graylog2+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/graylog2/09aa0944-44b5-46d2-a020-05626fd50167%40googlegroups.com. > > For more options, visit https://groups.google.com/d/optout. -- Developer Tel.: +49 (0)40 609 452 077 Fax.: +49 (0)40 609 452 078 TORCH GmbH - A Graylog Company Poolstraße 21 20335 Hamburg Germany https://www.graylog.com Commercial Reg. (Registergericht): Amtsgericht Hamburg, HRB 125175 Geschäftsführer: Lennart Koopmann (CEO) -- 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 graylog2+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/graylog2/CAMqbBbJihx8fk%3DZXTgVvwweWJ1j_YrcCrO985fFJewCV8AY8%2BA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
