[graylog2] Re: How to upgrade Graylog 2.1 > 2.2 ?
Hey! Okay, thank you! This is extremely valuable information. Br, Henri On Friday, 17 February 2017 10:52:05 UTC+2, Jan Doberstein wrote: > > Hej Henri, > > this will be the best method for upgrading your environment. > > with kind regards > Jan > > On Thursday, February 16, 2017 at 7:18:24 PM UTC+1, Henri Volotinen wrote: >> >> Hi, >> >> So rolling upgrade is not supported? Good to know, because I was going to >> upgrade our production setup (with 3 graylog-server nodes version 2.1.3) >> using the rolling upgrade method. >> >> So basically the upgrade steps are in my scenario are: >> 1) Shutdown all (three) graylog-server nodes >> 2) Upgrade all (three) graylog-server nodes to version 2.2.0 >> 3) Start the master node and wait for it to do some indexing magic to the >> Elasticsearch cluster until it fully starts up >> 4) Start the other two non-master nodes >> >> Is this the correct way to do the upgrade? >> >> Thanks! >> >> Br, >> Henri >> >> On Thursday, 16 February 2017 12:08:36 UTC+2, Jochen Schalanda wrote: >>> >>> Hi, >>> >>> On Thursday, 16 February 2017 10:34:07 UTC+1, jtkarvo wrote: >>>> >>>> Is is possible to do a rolling upgrade to a graylog cluster (from 2.1 >>>> to 2.2)? If so, should I upgrade master first or non-master nodes first? >>>> >>> >>> Due to some changes in the index management it's not possible to do a >>> rolling upgrade from Graylog 2.x to Graylog 2.2.0. >>> >>> You should upgrade and start the master node first, then the upgrade and >>> start the secondary nodes. >>> >>> 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/6681fa6c-3665-409e-850e-adc1d8402ccd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[graylog2] Re: How to upgrade Graylog 2.1 > 2.2 ?
Hi, So rolling upgrade is not supported? Good to know, because I was going to upgrade our production setup (with 3 graylog-server nodes version 2.1.3) using the rolling upgrade method. So basically the upgrade steps are in my scenario are: 1) Shutdown all (three) graylog-server nodes 2) Upgrade all (three) graylog-server nodes to version 2.2.0 3) Start the master node and wait for it to do some indexing magic to the Elasticsearch cluster until it fully starts up 4) Start the other two non-master nodes Is this the correct way to do the upgrade? Thanks! Br, Henri On Thursday, 16 February 2017 12:08:36 UTC+2, Jochen Schalanda wrote: > > Hi, > > On Thursday, 16 February 2017 10:34:07 UTC+1, jtkarvo wrote: >> >> Is is possible to do a rolling upgrade to a graylog cluster (from 2.1 to >> 2.2)? If so, should I upgrade master first or non-master nodes first? >> > > Due to some changes in the index management it's not possible to do a > rolling upgrade from Graylog 2.x to Graylog 2.2.0. > > You should upgrade and start the master node first, then the upgrade and > start the secondary nodes. > > 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/30bc6f68-b2c0-4733-879b-26ab11351834%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[graylog2] Re: Manipulating pipelines via REST API by non-admin user in Graylog 2.1.2
Hello! Thank you very much. This solved my problem! -hege On Friday, 20 January 2017 10:37:16 UTC+2, Jochen Schalanda wrote: > > Hi Henri, > > On Thursday, 19 January 2017 20:30:51 UTC+1, Henri Volotinen wrote: >> >> But I wonder, what permissions do I need to grant to a non-admin system >> user that should only be allowed to read and write stuff related to >> pipelines? >> > > You can find the pipeline-related permissions at > https://github.com/Graylog2/graylog-plugin-pipeline-processor/blob/1.1.2/src/main/java/org/graylog/plugins/pipelineprocessor/rest/PipelineRestPermissions.java#L30-L44 > > 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/14c7ca86-842b-4e9e-b97e-6bd3aabf5f90%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[graylog2] Manipulating pipelines via REST API by non-admin user in Graylog 2.1.2
Hey, I have coded a Python script that creates a pipeline rule, and adds that rule to a pipeline stage via Graylog's REST API. This works perfectly fine when using the built-in admin user that has all the access rights to the REST API. But I wonder, what permissions do I need to grant to a non-admin system user that should only be allowed to read and write stuff related to pipelines? I checked the source code from https://github.com/Graylog2/graylog2-server/blob/2.1.0/graylog2-server/src/main/java/org/graylog2/shared/security/RestPermissions.java but I cannot tell which permissions give the rights I need. Please, could you shed some light on this matter? Thanks! -hege -- 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/62425d64-08b7-490a-b358-53ef8048c039%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
