491
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.
General usage:
- To update LOGS to the most recent stable version execute: sudo /opt/logs/scripts/updates/updateRelease.sh current
- To update LOGS to the a specific version execute: sudo /opt/logs/scripts/updates/updateRelease.sh <version-number>
Tip: Create a symbolic link to the update script inside /opt/logs for easier access using: sudo ln -s /opt/logs/scripts/updates/updateRelease.sh /opt/logs/updateRelease.sh
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: Never skip major versions. Make sure you always update first to the latest release of each major version. Additionally there is a breaking change introduced in 3.1.100+ (Upgrade of the PostreSQL database version) which require the execution of a migration script (sudo /opt/logs/scripts/migrations/upgradeToLOGS-3.1.100x.bash in order to update from 3.1.x (x<=100) to 3.1.y (y >= 100).
- If you are updating from 2.7.x: updateRelease.sh 2.7.145 -> updateRelease.sh 3.0.89 -> updateRelease.sh 3.1.52 -> migration script -> updateRelease.sh 3.1.219 -> updateRelease.sh current
- If you are updating from 3.0.x: updateRelease.sh 3.0.89 -> updateRelease.sh 3.1.52 -> migrationscript -> updateRelease.sh3.1.219 -> updateRelease.sh current
- If you are updating from 3.1.x (x<100): updateRelease.sh 3.1.52 -> migrationscript -> 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
