Skip to content
This repository has been archived by the owner on Nov 25, 2020. It is now read-only.

Performing Troubleshooting Upgrade

Charles du Jeu edited this page Sep 28, 2016 · 20 revisions

Known Limitations / Issues

Currently at version 6.5.2

  • Please note that Linux packages (RPM/Debian) are NOT available at this time, only tarballs (zip / tar.gz)

  • DB Upgrade scripts were tested with MySQL only. Versions are now present for PG and SQLite but not tested. Contributions welcome on that.

  • Potential issues during upgrade

  • data/public/share.php is updated but with a blank line at the beginning of the file (before the <?php tag), breaking the existing share links. Just remove the blank line (fixed in 6.5.2)

  • Server stuck when installing Pydio Enterprise with a valid license : we are in the process of removing any dependency to mcrypt extension, as it will be deprecated in php7.1. We use a pure-php implementation for decrypting legacy strings (inc. license string) and it seems it can get stuck if the encoded data is wrong. Make sure to copy paste license name / license string at one in the field boxes, so that the installer will only test a correct value.

Backup!

We are pretty confident that this beta will not mess up your installation. That said, we would not recommend you enough to backup the whole installation (files and DB) to make sure to be able to easily revert if anything goes wrong.

Best case would be to use snapshots if you are working in a virtualized environment.

In-App Updater

Pydio Beta2 is available as Pydio Core 6.5.2 on the "Development" Channel. You just have to switch the updater plugin to this channel and check for update. You can upgrade from 6.4.2 or from previous beta 6.5.1

Upgrade should successfully load the new source code, and apply the following changes :

  • Update .htaccess content
  • Update data/public/share.php content for backward compatibiliy
  • Update AWS SDK Version to v3 (the aws.phar is no longer required, we embed an up-to-date sdk in Pydio).

After the upgrade procedure, and until you are logged out, you will probably see some "Internal Errors" appear, as the data stored in your session (inc. your user object) will be out-of-sync with the new code. Clearing your browser cookies and reload should fix the problem.

Some UI resources may require a hard refresh (clearing your browser cache) as well.

Troubleshooting if something went wrong during upgrade

The step described just above should avoid ending in an unstable state. However, if this should happen, please refer to the 6.5.2.* scripts located the code repository :

Install new version from scratch

Zip / Tar.gz packages are available on our download sites :

For Pydio Enterprise packages, please contact us through the chatroom.

NEXT