Chat now with support
Chat with Support

syslog-ng Store Box 6.3.0 - Administration Guide

Preface Introduction The concepts of SSB The Welcome Wizard and the first login Basic settings User management and access control Managing SSB Configuring message sources Storing messages on SSB Forwarding messages from SSB Log paths: routing and processing messages Configuring syslog-ng options Searching log messages Searching the internal messages of SSB Classifying messages with pattern databases The SSB RPC API Monitoring SSB Troubleshooting SSB Security checklist for configuring SSB

Upgrade checklist

The following list applies to all configurations:

  • The firmware of your SSB appliance is not tainted (that is, none of its files were modified locally). If the firmware is tainted, a warning is displayed on the Basic Settings > System > Version details page.

    Upgrading is not supported if the firmware is tainted. If your firmware is tainted, contact our Support Team.

  • You have created a configuration backup of syslog-ng Store Box (SSB).

    For detailed instructions, refer to Exporting the configuration of SSB.

  • You have a valid support portal account.

    To download the required .ISO file and the license, you need a valid support portal account. Note that the registration is not automatic, and might require up to two working days to process.

  • You have downloaded the latest .ISO file from the Downloads page. For further information, see Firmware in SSB.

  • You have read the Release Notes of the firmware(s) before updating. The Release Notes might include additional instructions specific to the firmware version.

    The Release Notes are available here on the Downloads page.

If you have a high availability cluster:

  • You have IPMI access to the slave node. You can find detailed information on using the IPMI interface in the following documents:

    For syslog-ng Store Box Appliance 3000 and 3500, see the IPMI User's Guide.

  • You have verified on the Basic Settings > High Availability page that the HA status is not degraded.

  • If you have a high availability cluster with geoclustering enabled:

    Perform the firmware upload steps an hour before the actual upgrade. Geoclustering can introduce delays in master-slave synchronization, and the slave node might not be able to sync the new firmware from the master node on time.

If you are upgrading SSB in a virtual environment:

  • You have created a snapshot of the virtual machine before starting the upgrade process.

  • You have configured and enabled console redirection (if the virtual environment allows it).

During the upgrade, SSB displays information about the progress of the upgrade and any possible problems to the console, which you can monitor with IPMI (ILOM) or console access.

We recommend that you test the upgrade process in a non-productive (virtual, etc.) environment first.

Upgrading SSB requires a reboot. We strongly suggest that you perform the upgrade on the productive appliance during maintenance hours only, to avoid any potential data loss.

Upgrading SSB

To upgrade syslog-ng Store Box (SSB) (single node)

  1. Navigate to Basic Settings > System > Upgrade.

  2. Click Choose File and select the .ISO file you want to upload.

  3. Click Upload.

    When the upload is finished, read the Upgrade notes pop-up window.

  4. Click . SSB will automatically upgrade and reboot the new version. Wait for the process to complete.
  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.

Upgrading an SSB cluster

To upgrade syslog-ng Store Box (SSB)

  1. Navigate to Basic Settings > System > Upgrade.

  2. Click Choose File and select the .ISO file you want to upload.

  3. Click Upload. When the upload is finished, read the Upgrade notes pop-up window.

  4. Click . SSB will automatically upgrade and reboot the new version. Wait for the process to complete.

    NOTE:

    In High Availability mode, you have to start the slave node through the IPMI interface. Failing to start the slave node results in a DEGRADED HA status.

  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.

Troubleshooting

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 (or the F5 key on your keyboard) to remove any cached version of the page.

In the unlikely case that syslog-ng Store Box (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 that helps the our 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.

Related Documents