Chat now with support
Chat with Support

syslog-ng Store Box 6.0 - Release Notes

Known issues

The following is a list of issues, including those attributed to third-party products, known to exist at the time of release.

Table 7: General known issues
Known Issue Issue ID

When rebooting an SSB node under high load, it might happen that the indexer processes do not stop before the node reboots. As a result, the log messages that were indexed at the time of the reboot can be displayed incorrectly (not displayed in the search results, or misplaced on the timeline) when searching for these messages. If you experience such problems, contact our Support Team. Note that no log data is lost.

To avoid this situation, when you want to reboot SSB, complete the following steps:

  1. Temporarily disable incoming log traffic: Basic Settings > System > Service control > Disable

  2. Wait a few minutes for the indexers to finish processing the log messages.

  3. Reboot SSB.

  4. Enable incoming log traffic: Basic Settings > System > Service control > Enable

 

When upgrading a high-availability SSB cluster from version 5.3 to 6.0, in some rare cases the primary node does not automatically reboot after clicking Upgrade, reboot master, and shut down slave, but displays the following error message instead:

Internal Error
stream_socket_client(): unable to connect to tcp://1.2.4.1:8000 (No route to host)

To solve the problem, click System control > This node > Reboot.

 

RSA-PSS certificates that use the RSASSA-PSS signature algorithm are currently not supported in SSB. Typically, the Active Directory - Certificate Services (AD CS) of Windows servers generate such certificates when using PKCS #1 v2.1 signatures. Do not upload such certificates. Uploading such certificates causes the SSB web interface to become inaccessible.

One Identity recommends to configure your PKI systems to use an alternate signature format, for example, use the SHA256RSA signature algorithm instead.

 

Product licensing

To enable a trial license

  1. Log in to the Trial Licenses page. Watch the short demo under How to Create a Trial License using Trial Depot?.

  2. Request a Trial License using the Trial Depot.

    The license keys will be emailed to you.

  3. Once you have the license keys, download the ISO image from the Free Trial of syslog-ng Store Box page.

To enable a purchased commercial license

  1. Navigate to My Account > My License Assets on the support portal.
  2. To access your license key, click Retrieve Key next to your product.
  3. Once you have the license keys, navigate to My Account > My Products and click Download next to your product. The Download Software page is displayed.
  4. Download the ISO image (install cdrom) of your product.

If you need help with accessing your license, navigate to the Licensing Assistance page, and follow the instructions on screen.

Upgrade and installation instructions

For details on upgrading to version 6.0.0, see Upgrade Guide.

Related Documents