This guide describes the recommended way to upgrade Graylog on RHEL/CentOS 7, 8, and 9. All links and packages are present at the time of writing.

Warning: This guide does not cover security settings! The server administrator must make sure the Graylog server is not publicly exposed and is following security best practices.

Prerequisites

The following tasks must be completed before upgrading the Graylog server. If they are not completed, problems may occur. Once the prerequisites are satisfied, then you may proceed with the upgrade process.

  • Review the release notes of the version(s) of Graylog that you will upgrade to. You can find all stable releases under Upgrading Graylog.

Warning: Do not skip a major version when upgrading Graylog. For example, to upgrade from 3.3.x to 4.3.x, first upgrade to the major version 4.0.x and then to 4.3.x. To upgrade from 3.3.x to 5.x.x, follow the same progression, i.e. first upgrade to the major versions then to 5.x.x (3.1 > 4.0 > 5.0 > 5.1.6).

  • You may also need to perform manual edits to the Graylog server.conf configuration file before restarting the Graylog server. Information on manual tasks required by a version of Graylog can be found in the changelogs and the Upgrading Graylog pages in the documentation.

  • Ensure that you back up both the MongoDB and Elasticsearch/OpenSearch database state prior to upgrading any component of the Graylog stack to create a rollback option.

  • In preparation for upgrading Graylog, you must first satisfy any software prerequisites. MongoDB and Elasticsearch/OpenSearch must be running at least the minimum required version required for the version of Graylog to which you wish to upgrade. Please refer to the following chart to determine your version compatibility requirements:

Graylog Version Minimum MongoDB Version Maximum MongoDB Version Minimum Elasticsearch Version Maximum Elasticsearch Version Minimum OpenSearch Version Maximum OpenSearch Version
3.3.x 3.6 4.2 5.0 6.x Not Supported Not Supported
4.0.x 3.6 4.2 6.8 or 7.0 7.1 Not Supported Not Supported
4.1.x 3.6 4.4 6.8 or 7.0 7.1 Not Supported Not Supported
4.2.x 3.6 4.4 6.8 or 7.0 7.10.2 Not Supported Not Supported
4.3.x 3.6 5.0 6.8 or 7.0 7.10.2 1.1.x (or 1.3.x for Graylog Security) 1.3.x

5.0.x

5.0

6.x

7.10.2

7.10.2

1.1.x (or 1.3.x for Graylog Security)

2.13.x

Warning: We caution you not to install or upgrade Elasticsearch to 7.11+ or OpenSearch 2.14+! It is not supported. If you do so, it will break your instance!

Software Verification

In order to verify that you are running the desired version of either of the dependencies mentioned above, enter the following command, replacing the name of each application with the one you want to verify:

Copy 
sudo yum list installed | grep 'mongo\|elasticsearch\|opensearch\|graylog'

Upgrading Graylog on Red Hat

Complete the following steps to upgrade your Graylog instance using your package manager of choice (e.x. YUM or RPM):

1. Shutdown the Graylog node:

Copy 
sudo systemctl stop graylog-server

2. Monitor the status of the Graylog node:

Copy 
ps -aefww | grep graylog

3. Once the Graylog node is down, update the local package cache:

Copy 
sudo rpm -Uvh https://packages.graylog2.org/repo/packages/graylog-5.0-repository_latest.rpm
sudo yum clean all
sudo yum update

4. Display available versions of Graylog.

For Graylog Open: 

Copy 
sudo yum list graylog-server --showduplicates

For Graylog Operations:

Copy 
sudo yum list graylog-enterprise --showduplicates

5. Use the system tools to upgrade the Graylog package(s).

  • If the version is not specified in the command, then the latest version in the repository will be installed.

  • If you have a lock on the Graylog package, you may then be prompted to remove it before allowing the upgrade to execute.

For Graylog Open: 

Copy 
sudo yum upgrade graylog-server-5.0.2-1

For Graylog Operations:

Copy 
sudo yum upgrade graylog-enterprise-5.0.2-1

To display installed graylog-* packages:

Copy 
sudo yum list installed | grep graylog

6. Make any necessary changes to Graylog configuration file(s) as indicated by version.

7. Finally, restart the Graylog node:

Copy 
sudo systemctl restart graylog-server