NetIQ Sentinel Log Manager Release Notes

March 2015

Sentinel Log Manager resolves specific previous issues. This document outlines why you should install this hotfix.

Many of these improvements were made in direct response to suggestions from our customers. We thank you for your time and valuable input. We hope you continue to help us ensure that our products meet all your needs. You can post feedback in the Sentinel Community Support Forums on NetIQ Communities, our online community that also includes product information, blogs, and links to helpful resources.

1.0 What’s New?

The following sections outline issues resolved in this release:

1.1 Java 8 Upgrade

Sentinel Log Manager now includes Java 8, which includes fixes for several security vulnerabilities.

1.2 Software Fixes

Sentinel Log Manager provides software fixes for the following issues:

Security Vulnerability in SSL 3.0

Issue: A vulnerability exists in SSL 3.0, which might allow the plaintext of secure connections to be calculated. For more information, see CVE-2014-3566 or (BUG 902061 and 902233)

Fix: Sentinel Log Manager fixes the vulnerability in the following ports:

  • 8443

  • 10013

  • 61616

  • 61617

The open ports now use only TLS protocol. Sentinel Log manager disables all SSL 2.0 and SSL 3.0 protocols on these ports.

Sentinel Log Manager Runs Out of Memory if the raw data is Corrupt

Issue: Sentinel Log Manager does not parse raw data if it is corrupt. Sentinel Log Manager stops receiving events from the remote collector manager and generates an out of memory error. (BUG 844087)

Fix: Sentinel Log Manager now drops the corrupt raw data and proceeds with the data collection.

Unable to Search Events After Upgrading to Sentinel Log Manager

Issue: After you upgrade Sentinel Log Manager to, when you initiate a search for events, the search does not complete and becomes unresponsive. (BUG 901524)

Fix: When you initiate a search, it now completes and displays the appropriate results.

2.0 System Requirements

For more information about system requirements, see System Requirements in the Sentinel Log Manager 1.2.2 Installation Guide.

3.0 Upgrading to Sentinel Log Manager

You can upgrade to Sentinel Log Manager from Sentinel Log Manager 1.2 or later. To upgrade to Sentinel Log Manager, see “Upgrading Sentinel Log Manager” in the Sentinel Log Manager 1.2.2 Installation Guide. After performing the upgrade procedure, restart the Sentinel Log Manager server to apply updates for SLES 11 Service Pack 3.

IMPORTANT:If you are upgrading Sentinel Log Manager appliance on an operating system prior to SLES 11 SP3, you must upgrade the appliance by using the zypper command line utility because user interaction is required to complete the upgrade. WebYaST is not capable of facilitating the required user interaction. For information about using zypper to upgrade the appliance, see “Upgrading the Appliance by Using zypper” in the Sentinel Log Manager 1.2.2 Installation Guide.

4.0 Known Issues

NetIQ Corporation strives to ensure our products provide quality solutions for your enterprise software needs. The following issue is currently being researched. If you need further assistance with any issue, please contact Technical Support.

For the list of known issues in the supported SLES 11 Service Pack, see the SUSE Release Notes.

For the list of known issues in previous releases, see the Sentinel Log Manager 1.2.1 Documentation Web site.

4.1 Cannot Uninstall the Remote Collector Manager

Issue: When you uninstall the remote collector manager, an error message displays and stops the uninstallation. (BUG 921683)

Workaround: To ensure that the remote collector manager is uninstalled properly, perform the following:

For Windows: When uninstalling on Windows, the system prompts for the Java location. Set the location as: <install_directory>\SP_1.2.2.1_<upgrade_date>_bak\jre\bin\java.exe and continue with the remaining steps.

For SLES: Before you uninstall the remote collector manager, perform the following:

  1. Log in as the root user.

  2. Navigate to the folder where the remote controller manager JRE is installed.

    cd <install_directory>/jre/bin

  3. Rename the existing java file to java8 to create a backup.

    mv java java8
  4. Navigate to <install_directory>/SP_1.2.2.1_<upgrade_date>_bak/jre/bin folder and change the java7 file permission to executable.

    chmod u+x <install_directory>/SP_1.2.2.1_<upgrade_date>_bak/jre/bin/java
  5. Set the location to the java7 file.

    ln -s <install_directory>/SP_1.2.2.1_<upgrade_date>_bak/jre/bin/java java
  6. Navigate to the uninstall folder.

    cd <install_directory>/_uninst
  7. Run the uninstall command.

    ./uninstall.bin -console

5.0 Contact Information

Our goal is to provide documentation that meets your needs. If you have suggestions for improvements, please email We value your input and look forward to hearing from you.

For detailed contact information, see the Support Contact Information website.

For general corporate and product information, see the NetIQ Corporate website.

For interactive conversations with your peers and NetIQ experts, become an active member of our community. The NetIQ online community provides product information, useful links to helpful resources, blogs, and social media channels.