Welcome to Gemini Central 3.2

This document provides the release notes for Gemini Central 3.2. It describes new capabilities and notable changes relative to the previous production release.

Upgrade from previous versions

Central 3.2 is released as a system upgrade pack containing new features, system-level changes, and patches released since the Manage 2.9.1 release.

Confirm your current Manage/Central version before applying this upgrade pack. An existing installation of Manage 2.9.1 is required for this upgrade pack.

For customers running earlier versions, please contact the Gemini Support team via the Support Portal for information on upgrading to the latest version.

What’s New in Gemini Central 3.2

System and Foundation

  • New Featured Platform that supports Neo4j. Neo4j is a graph database that Gemini Explore can cooperate with. This allows user to deploy Neo4j 4.x on Central by uploading binaries downloaded from Neo4j official website. User is able to control the services and watch it’s status.
    Please note:

    • It supports Neo4j 4.x only.

    • It provides a configuration editor that allows user to modify the neo4j settings.

    • The TLS certs has been integrated with Central. When user updates the TLS certs on Central, the certs will be applied to neo4j automatically.

    • There is a new OS user “neo4j” specific for this platform. 

    • There is a new mount point option “/opt/neo4j”.

    • There is a prerequisite check before deploying. It will check if the current system resources meet the following minimum requirements:

      • CPU: 2 cores

      • Free MEM: 2 GB

      • Free Disk(/opt): 10 GB

  • Support Gemini Explore v3.0 with it’s multiple projects capability. Note that it requires internet access in deployment.

  • Upgrade the JAVA runtime version to OpenJDK 11.

  • Fix multiple security vulnerabilities found and validated before Match 8, 2023.

Splunk Manager

  • Fix several incompatible issues during Splunk upgrade and now it supports Splunk 9.

Tableau Server

  • There is a prerequisite check added to prevent the deployment failure. It will check if the current system resources meet the following minimum requirements:

    • CPU: 8 cores

    • Free MEM: 64 GB

    • Free Disk(/opt): 50 GB

  • There is a RPM download link provided that will bring user to the official download site.

  • New capability that allows user to upgrade the service by uploading the new RPM. Please note that a valid license required during upgrade, or the service restart will fail.

  • It shows the current version of the installed Tableau Server.

  • New console output that will help user to understand the current status.

Fixed Issues

  • MGR-4287: Failed to create TCP/UDP destinations in log receiver

  • MGR-4275: Scheduled job still pending after the scheduled time

  • MGR-4280: Log rules can share the same destination file name

  • MGR-4282: Log filters cannot be copied completely

  • MGR-4284: Log files not created in /opt/sbox/data

  • MGR-4286: Failed to remove peer node from CLUSTER

  • MGR-4293: Tableau server produces warning messages when the memory is sufficient

  • MGR-4281: Log filter/destination created even user hit the cancel button

  • MGR-4278: “Learn More” button in license status page will lead to 404 page

Fixed Vulnerabilities

Since Central 3.1:

  • CentOS 7 : bind (CESA-2022:6765)

  • CentOS 7 : bind (CESA-2023:0402)

  • CentOS 7 : device-mapper-multipath (CESA-2022:7186)

  • CentOS 7 : expat (CESA-2022:6834)

  • CentOS 7 : git (CESA-2023:0978)

  • CentOS 7 : gzip (CESA-2022:2191)

  • CentOS 7 : java-1.8.0-openjdk (CESA-2022:5698)

  • CentOS 7 : java-1.8.0-openjdk (CESA-2022:7002)

  • CentOS 7 : java-11-openjdk (CESA-2023:0195)

  • CentOS 7 : kernel (CESA-2022:4642)

  • CentOS 7 : kernel (CESA-2022:4642)

  • CentOS 7 : kernel (CESA-2022:5232)

  • CentOS 7 : kernel (CESA-2023:0399)

  • CentOS 7 : krb5 (CESA-2022:8640)

  • CentOS 7 : linux-firmware (CESA-2021:0339)

  • CentOS 7 : open-vm-tools (CESA-2022:6381)

  • CentOS 7 : python (CESA-2022:5235)

  • CentOS 7 : rsync (CESA-2022:6170)

  • CentOS 7 : sssd (CESA-2023:0403)

  • CentOS 7 : sudo (CESA-2023:0291)

  • CentOS 7 : systemd (CESA-2022:6160)

  • CentOS 7 : xz (CESA-2022:5052)

  • CentOS 7 : zlib (CESA-2022:2213)

Known Issues

  • When deploying Neo4j database through Neo4j featured platform on Central instances which is running on AWS EC2, you will not be able to access to Neo4j’s console because the service port is listening to the specific internal IP address of this EC2 instance.

    • Solution: Connect to neo4j console by using SSH tunnel, or modify the neo4j system settings.

  • Sometimes Tableau Server will fail to restart after upgrade.

    • Workaround: Wait 20 minutes and see if it’s still not started. If the situation remains, restart it manually.

  • IMPORTANT: If there are iSCSI devices mounted, the bootup process will fail following an upgrade. Workaround:

    • Unmount all iSCSI devices before running the upgrade process.

Supported Platform Application Versions


Splunk Enterprise 8.0

Splunk Enterprise 8.1

Splunk Enterprise 8.2

Splunk Enterprise 9.0

Splunk Light 8.0

Splunk Light 8.1

Splunk Light 8.2

Splunk Light 9.0


Neo4j Enterprise 4.x

Gemini Explore

Gemini Explore 2.0

Gemini Explore 3.0

Tableau Server

Tableau Server 2022-3-2

Deprecated and removed features

Deprecated features

  • Integration Center is deprecated and no longer maintained. It will be removed in the next release.

Removed features

  • None.


All third-party products mentioned within this document are the property of their respective owners.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.