Perfom updates via script (recommended)

For maximum convienience we provide a collection of scripts to automate recurring tasks. Those tasks include updating of LOGS. If you haven`t install this script collection (per default installed under /opt/logs/scripts/) please refer to this article. Please note that In legacy installation scrript (/opt/installer.sh) only support LOGS versions below 3.1 and therefor can be removed.

 

To update LOGS to the most recent stable version execute:

 

 

To update LOGS to the a specific version execute:

 

 

Tip: Create a symbolic link to the update script inside /opt/logs for easier access using:

 

 

During the update process a backup of the database will be performed automatically. Depending on the amount of meta data this may take some time to finish before the download and installation of the new LOGS binary is performed. If your network / firewall does not allow to access our download server, copy the the new LOGS binary manually in /opt/logs before you running the update script. It will automatically recognize the local file and will skip attemping to download it.

 

IMPORTANT NOTES:

1) Never skip major versions. Make sure you always update first to the latest release of each major version.

2) Some major version updates will trigger internal DB or file migrations. Make sure that those migrations are finished before updating to the next version. The most easiest way is to check if you can log in into LOGS and if the dashboard is loading as usual. If not please wait some time and recheck. Depending on the number of datasets and samples,it might take between 5 minutes to overnight to finish. More advaned users can have a look at the internal log using "sudo ./logs logs" and look for the term "Migration". To exit the log view press Ctrl+c. 

3) There is a breaking change introduced in 3.1.100+. (Upgrade of the PostreSQL database version) which require the execution of a migration script in order to update from 3.1.x (x<=100) to 3.1.y (y >= 100). The migration script is part of the bash tools collection whose installation is described in this article. 

 

 

Use the following guide to to update your installation to the most recent version. If you are unsure please contact our support team before you start. Pay attention to all points described above, especially to wait until all migrations are finished.

 

• If you are updating from 2.7.x:  updateRelease.sh 2.7.145 -> updateRelease.sh 3.0.89 -> updateRelease.sh 3.1.52 -> run migration script -> updateRelease.sh 3.1.219 -> updateRelease.sh current
• If you are updating from 3.0.x: updateRelease.sh3.0.89 -> updateRelease.sh 3.1.52 -> run migration script -> updateRelease.sh3.1.219 -> updateRelease.sh current
• If you are updating from 3.1.x (x<100): updateRelease.sh 3.1.52 -> run migration script -> updateRelease.sh 3.1.219 -> updateRelease.sh current
• If you are updating from 3.1.y (y >=100): updateRelease.sh 3.1.219 -> updateRelease.sh current

 

Perform updates manually (depreciated)

Copy the new LOGS executable to the target directory, usually /opt/logs/. We recommend doing a manual backup of the database with /opt/logs/logs db-backup /usr/bin/date -Iminutes`. Stop LOGS with sudo ./logs down Adjust the symlink to point to the new LOGS executable. Start the new LOGS with sudo ./logs up