General Guidelines for Updating (v2.1 to v2.2, and beyond)


#1

I’ve inherited a single node Graylog server that I’d like to start updating. I’m new with this product so I am proceeding very cautiously. We are currently running v2.1.2 and this is a manual rpm install on CentOS.

I have only found these two pages:
http://docs.graylog.org/en/2.4/pages/installation/operating_system_packages.html#operating-package-upgrade-rpm-yum-dnf
and
http://docs.graylog.org/en/2.4/pages/upgrade.html

This first page basically states that all I have to do is update the repository and then “yum install graylog-server” (the 2nd page states that after the update some of my streams and alerts may need reconfiguration).

Is it really that easy? Is there anything else I need to be aware of? Should I go from 2.1 to 2.2 then 2.3 etc… or can I update from 2.1 to 2.4? Will all of my configuration settings will remain in place? Do I need to stop the graylog-server service, or/and elasticsearch & mongodb before the yum? During the update will any log entries be lost or will Graylog/ES continue to capture everything?

Thanks in advance


(Jochen) #2

While upgrading from Graylog 2.1.2 to 2.4.3 directly might work, I’d recommend taking the minor steps and make sure that it still works after each upgrade.

Of course you should create a (working) backup of your Graylog node before upgrading. :wink:

Also make sure to thoroughly read the upgrade notes for each release at http://docs.graylog.org/en/2.4/pages/upgrade.html.

Yes, although some settings have been changed between Graylog 2.1.x and 2.4.x. See the upgrade notes for details.

I would recommend stopping Graylog before upgrading the package.

Log entries will be lost for the time Graylog is down. If you’re running a cluster with proper load-balancing and failover, you can minimize the downtime.


(system) #3

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.