Versions Compared

Old Version 8

changes.mady.by.user Dominique Burnand

Saved on

compared with

New Version Current

changes.mady.by.user Dominique Burnand

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Updating PI-Server

Excerpt
  • The whole bundle will need more RAM (approximately +1GB)
  • Make sure that your admin account has a valid email. You will receive a mail to set a new PW at first start after the update.
  • TLS is now required. A self singed certificate will be created if no certificate is provided.
  • You need to specify a SMTP server as passwords can only be set by mail
  • Team-logins will not exist anymore. Only admin accounts with an e-mail address will be migrated to user-accounts
  • Configuration:
    • ALM: Custom request timeout can not be set anymore via piplanning.cfg -> set timeouts in the ALM configuration in the cockpit.
    • ALM: verify_tls_cert can not be set anymore via piplanning.cfg → set that in the ALM configuration in the cockpit.
    • use_tls can not be set in piplanning.cfg anymore. TLS is always on and required by default.

Backup all the important data to make sure you can roll back

Do a backup as described here: 2.7.0 Backup

Update Docker images

If your server has a connection to the internet:

Request a login (username and password) for the Rentouch-Docker-Hub from Rentouch if you do not already have one.

Code Block
docker login harbor3.piplanning.io


If your server does not have a connection to the internet:

Install the updated offline installable images

  • Request a download link from rentouch for the updated .tar archived docker images.
  • Move the .tar archive to the server on which you are installing pi-server.
  • Input the command: (this may take a few minutes..)
Code Block
docker load -i pi-server-images_2.7.0.tar

Give your admin account an email address

Warning

Before updating: Make sure that your admin account has a valid email (login to the cockpit, settings → set a email address). You will receive a mail to set a new PW at first start after the update. You will need to contact Rentouch if you overlooked that and are locked out.

Update PI-Server config files

On the host-system download the newest version (checkout https://binaries.rentouch.ch/on-premise to see all versions) of the PI-Server docker archive and extract it:

Code Block
wget https://s3.eu-central-1.amazonaws.com/static.-piplanning.io/releases/on-premise/pi-server-docker_2.7.0.tar
mkdir -p pi-server-docker_2.7.0 && tar -xf pi-server-docker_2.7.0.tar -C pi-server-docker_2.7.0
cd pi-server-docker_2.7.0

Run the updater. You have to pass the path to your PI-Server folder (which contains the docker-compose and all the data) as the first argument.

Code Block
python update.py /path/to/my/pi-server/installation

When the migration to the newest version is finished restart the pi-server by

Code Block
cd /path/to/my/pi-server/installation
./install.sh

As a last step: You can clean up by removing the installer

Code Block
rm pi-server-docker_2.7.0.tar pi-server-docker_2.7.0


Possible failure of FA

If you run into the error showed above (500 Internal Server Error) after the first start. Solution: Start the server once again:

Code Block
./install.sh