In OES 2018 SP3 Update 3, 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 3, you must perform the following steps to transfer the data from old to the updated Elasticsearch:
Before applying the patch, data is displayed in the Insights and Dashboard pages of the CIS Admin Console.
Apply OES 2018 SP3 Update 3 patch. For more information, see Updating (Patching) an OES 2018 SP3 Server in the OES 2018 SP3: Installation Guide.
Restart the CIS server.
There will be no data displayed in the Insights and Dashboard pages of the CIS Admin Console.
(Conditional) If the configuration path is /media/nss/CISVOL (cluster volume), then ensure the cluster volume is up and running.
Verify the status of the updated Elasticsearch. If not running, restart the service.
systemctl status oes-cis-elastic.service
systemctl restart oes-cis-elastic.service
Start the old Elasticsearch and verify the status.
systemctl start oes-cis-old-elastic.service
systemctl status oes-cis-old-elastic.service
Verify the health of CIS.
cishealth
Before proceeding ensure CIS is healthy.
(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
Run the following command to move data from the old Elasticsearch to the updated Elasticsearch:
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.
On successful transferring the data, the Insights and Dashboard pages of the CIS Admin Console will populate the existing data.