4.3 Patching OES 2018 SP2 Update 8

In OES 2018 SP2 Update 8, we are addressing security vulnerability log4j2 that impacts Elasticsearch. Elasticsearch stores data that is displayed in Insights and Dashboard pages of the CIS Admin Console.

On patching the OES server to Update 8, you must perform the following steps to transfer the data from Elasticsearch 7.7 to 6.8.22:

4.3.1 Standalone CIS Server

Before applying the patch CIS server is running with Elasticsearch 7.7. Data is displayed in the Insights and Dashboard pages of the CIS Admin Console.

  1. Apply OES 2018 SP2 Update 8 patch, for more information, see OES 2018 SP2: Installation Guide.

  2. Restart the CIS server.

    There will be no data displayed in the Insights and Dashboard pages of the CIS Admin Console.

    1. (Conditional) If the configuration path is /media/nss/CISVOL (cluster volume), then ensure the cluster volume is up and running.

  3. Verify the status of Elasticsearch 6.8.22. If not running, restart the service.

    systemctl status oes-cis-elastic.service

    systemctl restart oes-cis-elastic.service

  4. Start Elasticsearch 7.7 and verify the status.

    systemctl start oes-cis-old-elastic.service

    systemctl status oes-cis-old-elastic.service

  5. Verify the health of CIS.

    cishealth

    Before proceeding ensure CIS is healthy.

  6. (Conditional) If the configuration path is a cluster volume, then move the configuration file from the cis_local location to the media path (/media/nss/CISVOL).

    sh /opt/novell/cis/bin/copy_upgraded_files.sh

  7. Run the following command to move data from Elasticsearch 7.7 to Elasticsearch 6.8.22

    sh /var/opt/novell/cis/elastic_move_data.sh migrate

    The migration takes some time to complete. You can verify the logs at /var/opt/novell/log/cis/cis_elastic_move_<timestamp>.log.

  8. On successful transferring the data, the Insights and Dashboard pages of the CIS Admin Console will populate the existing data.