This guide describes the fastest way to install Graylog on Red Hat Enterprise Linux 7-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

Hint: This guide assumes that any firewall is disabled and traffic can flow across all necessary ports.

Graylog 5.0 requires the following to maintain compatibility with its software dependencies: 

  • OpenJDK 17 (This is embedded in Graylog 5.0 and does not need to be separately installed.)
  • OpenSearch 1.x, 2.x (or Elasticsearch 7.10.2)
  • MongoDB 5.x or 6.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!

MongoDB

To install MongoDB on Red Hat follow the tutorial for Red Hat from the MongoDB documentation. Graylog 5.0 is compatible with MongoDB 5.x-6.x.

1. First, add the repository file /etc/yum.repos.d/mongodb-org.repo with the following contents:

Copy 
[mongodb-org-6.0]
name=MongoDB Repository
baseurl=https://repo.mongodb.org/yum/redhat/$releasever/mongodb-org/6.0/x86_64/
gpgcheck=1
enabled=1
gpgkey=https://www.mongodb.org/static/pgp/server-6.0.asc

2. After that, install the latest release of MongoDB:

Copy 
sudo yum install -y mongodb-org

3. Enable MongoDB during the operating system’s startup and verify it is running:

Copy 
sudo systemctl daemon-reload
sudo systemctl enable mongod
sudo systemctl start mongod
sudo systemctl status mongod

Hint: For the following sections on OpenSearch and Elasticsearch, select which data node you will be using for your Graylog instance and complete only the requisite section.

OpenSearch

If you are using OpenSearch as your data node, refer to the OpenSearch install page for detailed instructions.

The installation example below utilizes the YUM repository for installation.

1. Create a local repository file for OpenSearch.

Copy 
sudo curl -SL https://artifacts.opensearch.org/releases/bundle/opensearch/2.x/opensearch-2.x.repo -o /etc/yum.repos.d/opensearch-2.x.repo

2. Disable GPG check.

Copy 
sudo sed -i "s/^gpgcheck=.*/gpgcheck=0/g" /etc/yum.repos.d/opensearch-2.x.repo

3. Install OpenSearch.

Copy 
sudo OPENSEARCH_INITIAL_ADMIN_PASSWORD=$(tr -dc A-Z-a-z-0-9_@#%^-_=+ < /dev/urandom  | head -c${1:-32}) yum -y install opensearch.x86_64

Warning: RHEL 9 may fail with a SHA-1 warning; please see the Red Hat documentation for guidance.

4. Update the following fields for a minimum unsecured running state in the configuration file located at /etc/opensearch/opensearch.yml:

Copy 
cluster.name: graylog
node.name: ${HOSTNAME}
path.data: /var/lib/opensearch
path.logs: /var/log/opensearch
discovery.type: single-node
network.host: 0.0.0.0
action.auto_create_index: false
plugins.security.disabled: true
indices.query.bool.max_clause_count: 32768

5. Edit /etc/opensearch/jvm.options both Xms and Xmx to half system memory.

6. For RHEL 9, update /usr/lib/tmpfiles.d/opensearch.conf and change /var/run/opensearch to /run/opensearch.

7. Configure the kernel parameters at runtime:

Copy 
sudo sysctl -w vm.max_map_count=262144
sudo echo 'vm.max_map_count=262144' >> /etc/sysctl.conf

8. Enable OpenSearch during operating system’s startup and verify it is running:

Copy 
sudo systemctl daemon-reload
sudo systemctl enable opensearch
sudo systemctl start opensearch
sudo systemctl status opensearch

Elasticsearch

Elasticsearch 7.10.2 is the only version that is compatible with Graylog 5.0; however, we recommend OpenSearch for new Graylog cluster installations.

The following commands will begin the installation of the open-source version of Elasticsearch. See the Elasticsearch install page for more detailed instructions.

1. First, install the Elasticsearch GPG key:

Copy 
rpm --import https://artifacts.elastic.co/GPG-KEY-elasticsearch

2. Then add the repository file /etc/yum.repos.d/elasticsearch.repo with the following contents:

Copy 
sudo rpm --import https://artifacts.elastic.co/GPG-KEY-elasticsearch

echo "[elasticsearch-7.10.2]
name=Elasticsearch repository for 7.10.2 packages
baseurl=https://artifacts.elastic.co/packages/oss-7.x/yum
gpgcheck=1
gpgkey=https://artifacts.elastic.co/GPG-KEY-elasticsearch
enabled=1
autorefresh=1
type=rpm-md" | sudo tee /etc/yum.repos.d/elasticsearch.repo

sudo yum install elasticsearch-oss

3. Install the 7.10.2 release with:

Copy 
sudo rpm install elasticsearch-oss

4. Modify the Elasticsearch configuration file (/etc/elasticsearch/elasticsearch.yml), set the cluster name to graylog, and uncomment action.auto_create_index: false to enable the action:

Copy 
echo "cluster.name: graylog
action.auto_create_index: false" | sudo tee /etc/elasticsearch/elasticsearch.yml

5. After you have modified the configuration, you can start Elasticsearch:

Copy 
sudo systemctl daemon-reload
sudo systemctl enable elasticsearch.service
sudo systemctl restart elasticsearch.service
sudo systemctl --type=service --state=active | grep el

Graylog

Now install the Graylog repository configuration and Graylog Open itself with the following commands:

Copy 
sudo rpm -Uvh https://packages.graylog2.org/repo/packages/graylog-5.0-repository_latest.rpm
sudo yum install graylog-server

If you are installing Graylog Operations, then you will use the following commands:

Copy 
sudo rpm -Uvh https://packages.graylog2.org/repo/packages/graylog-5.0-repository_latest.rpm
sudo yum install graylog-enterprise

Edit the Configuration File

Read the instructions within the configurations file and edit as needed, located at /etc/graylog/server/server.conf. Additionally add password_secret and root_password_sha2 as these are mandatory and Graylog will not start without them.

1. To create your password_secret, run the following command:

Copy 
< /dev/urandom tr -dc A-Z-a-z-0-9 | head -c${1:-96};echo;

2. To generate a root_password_sha2:

Copy 
echo -n "Enter Password: " && head -1 </dev/stdin | tr -d '\n' | sha256sum | cut -d" " -f1

3. To be able to connect to Graylog, set http_bind_address to the public host name or a public IP address of the machine with which you can connect. More information about these settings can be found in Configuring the Web Interface.

Hint: If you’re operating a single-node setup and would like to use HTTPS for the Graylog web interface and the Graylog REST API, it’s possible to use NGINX or Apache as a reverse proxy.

4. The last step is to enable Graylog during the operating system’s start up:

Copy 
sudo systemctl daemon-reload
sudo systemctl enable graylog-server.service
sudo systemctl start graylog-server.service
sudo systemctl --type=service --state=active | grep graylog

Now you can ingest messages into your Graylog instance and extract the messages with extractors or use pipelines to work with the messages.

SELinux Information

Hint: We assume that you have policycoreutils-python installed to manage SELinux.

If you’re using SELinux on your system, you must address the following settings:

  • Allow the web server to access the network: sudo setsebool -P httpd_can_network_connect 1
  • If the policy above does not comply with your security policy, you can also allow access to each port individually:
    • Graylog REST API and web interface: sudo semanage port -a -t http_port_t -p tcp 9000
    • Elasticsearch (only if the HTTP API is being used): sudo semanage port -a -t http_port_t -p tcp 9200
  • Allow using MongoDB’s default port (27017/tcp): sudo semanage port -a -t mongod_port_t -p tcp 27017

If you run a single-server environment with NGINX or Apache proxy, enabling the Graylog REST API is enough. All other rules are only required in a multi-node setup. Having SELinux disabled during installation and enabling it later requires you to manually check the policies for MongoDB, OpenSearch, Elasticsearch, and Graylog.

Depending on your actual setup and configuration, you might need to add more SELinux rules to get to a running setup.

Further Reading

Multiple Server Setup

If you plan to have multiple server taking care of different roles in your cluster like we have in this big production setup you need to modify only a few settings. This is covered in our Multi-Node Setup guide. The Default File Location guide will give you the file you need to modify in your setup.