Once a new version is available, a popup message will appear in the iDNA Applications user interface. This notification links the release notes and download links for the new version.
Two upgrade packages are available:
The offline package also includes files that may not be required in your installation. Significantly less data will be transferred if the appliance has access to docker.panagenda.com, since only the files necessary for the upgrade will be downloaded. |
Please upload the upgrade package to the appliance's /tmp/ directory using the scp client of your choice (e.g. WinSCP or pscp on Windows).
Use the ssh client of your choice (e.g. putty on Windows) to connect to the appliance and execute the following commands:
cd /tmp unzip idnaapplications-upgrade-online/offline.zip ./ifa-upgrade.sh |
Logs are available in the log directory, e.g. /opt/panagenda/logs/ia-upgrade_<year>-<month>-<day>_<timestamp>.log.
In case there is not enough space left on the root partition (~8GB free space are required), the installation will abort and one of the following error messages will be displayed among the last few output lines:
An alternative method is to place the installer file on a partition that has enough free space and set an environment variable to tell the installer to also use this partition for temporary files. The /opt/panagenda/appdata or /opt/panagenda/pgdata partitions should typically have enough disk space available to hold the temporary files during the upgrade process.
These are the recommended steps for the workaround using the pgdata partition:
If major changes to the data warehouse occurred during the upgrade, parts of the application may not be available until the data warehouse is rebuilt. This process runs automatically at night, but can be triggered manually after the update. On the first login after the installation, more information on this topic will be displayed, along with the option to trigger the rebuild. It's safe to ignore this message until it vanishes by itself.
You may also encounter an issue with Metabase dashboards after the first login (see image below). Simply logging out (not just closing the browser) and in again will resolve this issue.
Go to the current iDNA Applications Release Notes.