API Security adds Continuous Discovery and Risk Scoring PLUS a Free Version | LEARN MORE>

The Graylog blog

v4.1.4 & v4.0.12 Release Pulled

We’ve discovered that the Graylog RPM packages contained a blank systemd unit file. As a result, we have pulled these two releases. If you have already upgraded your Graylog platform to versions 4.1.4 or 4.0.12, you will need to downgrade. Below we have outlined two options for how to do this. 

How to Downgrade

Downgrade using your system package manager by using something like:

yum downgrade graylog-server graylog-enterprise-plugins graylog-integrations-plugins graylog-enterprise-integrations-plugins

How to Manually Edit

If you are taking the manual edit route, you will need to edit your systemd unit file located at /usr/lib/systemd/system/graylog-server.service to include the following:

[Unit]

Description=Graylog server

Documentation=http://docs.graylog.org/

Wants=network-online.target

After=network-online.target


[Service]

Type=simple

Restart=on-failure

RestartSec=10

User=graylog

Group=graylog

LimitNOFILE=64000


ExecStart=/usr/share/graylog-server/bin/graylog-server


# When a JVM receives a SIGTERM signal it exits with 143.

SuccessExitStatus=143


# Make sure stderr/stdout is captured in the systemd journal.

StandardOutput=journal

StandardError=journal


[Install]

WantedBy=multi-user.target

After editing the unit file, run  systemctl daemon-reload to have systemd read the changes. Once you’ve run that command, you can start Graylog back up using:

 sudo systemctl start graylog-server.service  

Get the Monthly Tech Blog Roundup

Subscribe to the latest in log management, security, and all things Graylog Blog delivered to your inbox once a month.