Upgrading from a version prior to 2.1.0

These instructions are specific to the 2.1.0 version, and should be followed if you upgrade from a version prior to 2.1.0 to any version greater or equal to 2.1.0.

These steps should be followed in addition to the common upgrade procedure found in the standard upgrade protocol. None of these steps are automated by horizon-upgrade.

Setting an event seal secret

You must manually create an entry to pass an event seal secret to Horizon in the /etc/default/horizon file. horizon-config won’t do that automatically.

To do so, open the /etc/default/horizon file with a text editor:

$ vi /etc/default/horizon

And add a new line under the Horizon variables section:

# Horizon variables
HORIZON_NOTIFICATION_SMTP_HOST=127.0.0.1
HORIZON_HOSTNAME=
HORIZON_DEFAULT_SSV_KEY=
HORIZON_EVENT_SEAL_SECRET=changeme # <- this one

Then, near the end of the file, after the # Setting Horizon Mongo DB uri section, create a new section for the event seal secret:

# Setting the Horizon event seal secret
JAVA_OPTS="$JAVA_OPTS -Dhorizon.event.seal.secret=${HORIZON_EVENT_SEAL_SECRET}"

Horizon won’t boot if the HORIZON_EVENT_SEAL_SECRET is set to changeme. Therefore, you should set your secret to something hard to guess. Refer to the Initial Configuration guide to learn how to generate a seal secret with horizon-config.