syslog-ng Store Box 6.9.0 - Upgrade Guide

For details on upgrading your syslog-ng Store Box (SSB) installation to 6.9.0, see the following procedures.

Topics:

If you want to upgrade a SSB cluster, see Upgrading an SSB cluster.

Prerequisites

Read the following warnings before starting the upgrade process.

To upgrade a standalone SSB node to version 6.9.0

1. Stop SSB from accepting the incoming log traffic. Navigate to Basic Settings > System > Service control and click Disable.

2. Update the firmware of SSB using the web interface.

   1. Navigate to Basic Settings > System > Upgrade.

   2. Upload the new .ISO file.

   3. When the upload is finished, click Upgrade and reboot node.

3. Navigate to Basic Settings > System > System Control > This node, and choose Reboot.

   SSB attempts to boot with the new firmware. Wait for the process to complete.

4. Recommended step. To help troubleshoot potential issues following the upgrade, collect and save system information (create a debug bundle) now.

   Navigate to Basic Settings > Troubleshooting > System debug and choose Collect and save current system state info.

5. Navigate to Basic Settings > System > Version details and check the version numbers of SSB. In case you encounter problems, you can find common troubleshooting steps in Troubleshooting.

6. Enable SSB to receive the incoming log traffic. Navigate to Basic Settings > System > Service control and click Enable.

Prerequisites

Make sure that you have physically connected the IPMI interface to the network and that it is properly configured. This is important because you can only power the secondary node on through the IPMI interface. For details on configuring the IPMI interface, see "Out-of-band management of SSB" in the Administration Guide.

To upgrade an SSB cluster

1. Stop SSB from accepting the incoming log traffic. Navigate to Basic Settings > System > Service control and click Disable.

2. Update the firmware of SSB using the web interface.

   1. Navigate to Basic Settings > System > Upgrade.

   2. Upload the new .ISO file.

   3. When the upload is finished, click Upgrade, reboot master, and shut down slave.

3. Log in to the SSB web interface to verify that the primary node upgrade was successful.

   Navigate to Basic Settings > System > Version details and check the version numbers of SSB. In case you encounter problems, you can find common troubleshooting steps in Troubleshooting.

4. Use the IPMI interface to start the secondary node.

   The secondary node attempts to boot with the new firmware, and reconnects to the primary node to sync data. During the sync process, certain services (including Heartbeat) are not available. Wait for the process to finish, and the secondary node to boot fully.

5. Navigate to Basic Settings > System > High availability & Nodes and verify that the secondary node is connected, and has the same firmware versions as the primary node.

   NOTE:

   When upgrading an SSB cluster, the upgrade process on the slave node will only be completed once a takeover has been performed.

6. Enable SSB to receive the incoming log traffic. Navigate to Basic Settings > System > Service control and click Enable.

If you experience any strange behavior of the web interface, first try to reload the page by holding the SHIFT key while clicking the Reload button of your browser to remove any cached version of the page.

In the unlikely case that SSB encounters a problem during the upgrade process and cannot revert to its original state, SSB performs the following actions:

• Initializes the network interfaces using the already configured IP addresses.

• Enables SSH access to SSB, unless SSB is running in sealed mode. That way it is possible to access the logs of the upgrade process, which helps the Support Team to diagnose and solve the problem. Note that SSH access will be enabled on every active interface, even if management access has not been enabled for the interface.

In case the web interface is not available within 30 minutes of rebooting SSB, check the information displayed on the local console and contact our Support Team.