Update
Last updated
Was this helpful?
Last updated
Was this helpful?
As soon as a new on-premises version is available, you will receive an e-mail from us. In the email, you can get the current version numbers. You will also get the latest versions from .
Make sure to also keep the installed software components Pulsar Agent, Watchdog, Hacktor and Observer up to date. You can execute the updates directly in the platform.
We recommend to use our update script to automatically install the latest version of Enginsight.
1.Make sure that you have root privileges. If this is not the case, log in as superuser.
2. Navigate to the directory of your installation and run the update script.
Alternatively, you can have the update executed automatically via a cronjob.
1. Execute the following command to add a cronjob.
2. Copy the following line into the document, edit the execution time according to your needs and save the document.
In this example, the update is performed weekly on every Sunday 4:00 AM.
If you want to manually update software modules to special versions, use the following procedure.
1. Make sure that you have root privileges. If this is not the case, log in as superuser.
2. Navigate to /opt/enginsight/enterprise
3. Adjust the image versions of the various Docker services.
Example of services, ui-m1:
Save the docker-compose.yml
5. Execute the setup script and confirm all prompts.
You can update our four software components directly in the Enginsight platform.
The best way is to update the Pulsar agent on all hosts at the same time.
Go to Hosts → Overview.
Click on the "Update Agents" button. You will find it above the list of your hosts.
Click Refresh. If all agents are up to date, you will receive a message.
Go to Endpoints → Observers and check if all version numbers are up to date.
If an observer does not have the current version number, click the update icon in the right column at Actions.
Go to Discoveries → Watchdogs and check if all version numbers are up to date.
If a watchdog does not have the current version number, click the update icon in the right column at Actions.
Go to Penetration Testing → Hacktors and check if all version numbers are up to date.
If a hacktor does not have the current version number, click the update icon in the right column at Actions.
The following instructions explain the procedure for updating the Docker containers for Zookeeper, Solr and Traicer. It is imperative that you follow the instructions to prevent errors!
First run the central update script.
Make absolutely sure that the sequence described below is followed - especially for Zookeeper and Solr.
Zookeeper Update Avoid automatic updates for Zookeeper, or make sure that Zookeeper is fully started before the Solr update starts.
Solr Update Solr requires a running Zookeeper instance to start. If Solr is started before Zookeeper, there may be connection problems that can only be resolved by restarting Solr manually.
Traicer Update The Traicer container can be updated independently, without any special dependencies.
These instructions describe how to carry out updates in a partially offline scenario, in which the app server temporarily receives an internet connection in order to download updates. The downloaded data can then be transferred to other hosts without an internet connection. The focus here is on updates to the Enginsight components, in particular the Pulsar component.
Internet aktivieren Activate the internet connection on the app server to be able to download the updates.
Checking and updating the software components
Deactivating the Internet connection Once the updates are complete, disconnect the app server from the Internet.
If an update is required for the Pulsar component, proceed as follows:
Zum Enterprise-Verzeichnis wechseln
Navigate to the directory /opt/enginsight/enterprise
:
Download new script
Download the latest Pulsar update script from the official repository:
Make script executable Grant the downloaded script the necessary execution rights:
Execute script Execute the script to download the current version of the Pulsar in all variants:
Finalize setup Start the setup script to finalize the changes:
docker-compose.yml
Adjust the configuration of the docker-compose.yml
for the server-m2
service to mount the Pulsar directory correctly:
After the adjustment, restart the affected service to apply the changes:
After completing the steps described above, all relevant components should be updated to the latest version. Make sure that all services are running properly and that the system is stable.
Backup of the MongoDB-configuration
The Configuration in /etc/mongod.conf
gets deleted during the upgrade. It must therefore be backed up beforehand.
To do this, change to the installation directory and stop the Enginsight environment:
This step ensures that all running services are properly stopped before the upgrade.
Creation of a database dump
Basic command:
mongodump --host "rs0/<ipOfTheDBAsUsedByTheApi>:27017" --db enginsight
With RBAC (user name/password) Add the following parameters:
With TLS Add the following parameters:
A complete dump command with an example IP for a database without TLS and RBAC looks like this:
A complete dump command with an example IP for a database with TLS and RBAC looks like this:
Deinstallation of MongoDB 5
Deleting database remnants
rm -rf /var/lib/mongodb
MongoDB reinstallation After a system restart:
MongoDB setup
Restoring the configuration
Now restore the backup of the /etc/mongod.conf
file.
Updating the configuration syntax
Due to a change in the configuration syntax, an adjustment is required. The storage
section previously looked like this:
The journal
key is no longer supported and must be removed along with its suboptions. The section should then look like this:
Temporarily deactivating authentication
Temporarily comment out the security
: section in the /etc/mongod.conf
file if it exists.
This applies to the entire section including sub-items, i.e. the indented options under security:
!
Start the Mongo DB
Setting up the replica set Basic command:
With TLS
The following parameters must be added after the --host
parameter:
Complete command with exemplary IP without TLS:
Restore user (if previously available) Basic commands:
With TLS
The following parameters must be added after the --host
parameter:
Complete commands with exemplary IP without TLS:
Complete commands with exemplary IP with TLS:
Reactivation of the authentication The lines commented out in step 7.3. must now be commented in again. MongoDB must then be restarted:
Importing the dump Basic command:
With RBAC (Username/Password)
Add these parameters:
With TLS
Add these parameters:
A complete dump command with an example IP for a database without TLS and RBAC looks like this:
A complete dump command with an example IP for a database with TLS and RBAC looks like this:
This step ensures that all services run properly again after the upgrade.
executeupdate.sh
Execute the update script update.sh
on the app server. To do this, follow the steps in the .
After completing the update, check all relevant components, including Pulsar, Watchdog, Observer and Hacktor. To ensure that the updates are cached correctly, update at least one installation of each component. Further details can be found in the under Software components.
Upgrade of the Debian-system Perform the upgrade with the . The MongoDB repository is automatically updated to version 8.0. A restart of the system is mandatory.