Upgrading to Graylog 3.2 is more involved than previous dot releases.
As mentioned in the announcement post…
PLEASE do yourself a favor and read the upgrading guidelines before attempting the upgrade.
https://docs.graylog.org/en/3.2/pages/upgrade/graylog-3.2.html
I wonder why they did not run the curl command when the upgrade to 3.2 is performed rather than hoping someone would see web page. It negates automated updating. Lesson is to remove graylog from yum-cron.
it looks simple from a user perspective but is it not easy to solve. That step is only needed if you want to make use of the gl2_accounted_message_size field. If that is not important for you - leave it and on the next rotate of indices that field will be added with the correct mapping.
The system will not break if you did not do this. In addition - only bug-fix releases are able to be updated automatically. Dot releases should always include that you check the upgrade notes and if configuration has changed or not.
This is not mentioned in upgrade instructions, so people like me think it’s mandatory step.
I have created a PR to make that more clear: https://github.com/Graylog2/documentation/pull/803
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
