To complete the upgrade from OES 2018 SP1 standalone CIS (configured) server to OES 2018 SP2:
Follow the step-by-step instructions for upgrading to OES 2018 SP2 server. For more information, see Upgrading to OES 2018 SP2 in the OES 2018 SP2: Installation Guide.
Ensure the database that you configured for CIS is up and running.
If it is a local database, verify the status of the database service:
systemctl status mysql.service
Enable and restart the database:
systemctl enable mysql.service
systemctl restart mysql.service
Verify the if the logging service is up and running:
systemctl status oes-cis-fluentbit.service
If it is not running, start the service:
systemctl start oes-cis-fluentbit.service
Start the Reporting Collector service:
systemctl start oes-cis-repcollector.service
Ensure all the CIS services are running, by executing the following command:
docker ps -a
This displays the status of all the CIS services.
To verify the health of the CIS server, run the follow:
cishealth
When the status displays “Healthy”, then the CIS server is successfully upgraded.
NOTE:The upgrade takes time to complete depending on the size of the database getting migrated from the OES 2018 SP1 server. During this phase, the CIS health might display the status of some services as “Not Healthy” because the scanned data is getting updated. On completing the update, the health status changes to “Healthy”.
Verify the status of the CIS agent and scanner service on the OES servers and ensure it is running.
systemctl status oes-cis-agent.service
systemctl status oes-cis-scanner.service