[solved] Issue with pydio upgrade 7.0.4 to 8.0.1

Pydio 8
, ,
1

Hi,

I am running Pydio 7.0.4 on ubuntu 14.04 with PHP “PHP 7.0.17-2+deb.sury.org~trusty+1” and Nginx
For info, SELINUX Disabled.

I have an issue when I try to upgrade my pydio server from v7.0.4 - 2017-02-02 to version 8.0.1.
When I click on “Start Upgrade”, I have the following error message.

Applying upgrade pydio-core-upgrade-7.0.4-8.0.0.zip
Checking download permissions
- OK
Downloading upgrade archive
- File saved in /var/www/pydio/data/tmp/update/pydio-core-upgrade-7.0.4-8.0.0.zip
Checking archive integrity
- Hash is ok (43ee2a94037a1d9784bac8ebbd77b79e)
Checking folders permissions
- OK
Extracting Archive
- Error : Crawling folder to check all files are writeable : File FAIL! Please make sure that the whole tree is currently writeable by the webserver, or upgrade may probably fail at one point.

I already read the post “Problem with upgrade from version 7.0.4 to 8.0.0”.

Charles said that it was a table collation issue so I checked my engine and charset used for my tables but all my tables are using “innodb” natively and the charset are “utf8_unicode_ci” except for table “ajxp_version”.

Below the extract :

mysql> SELECT TABLE_NAME, ENGINE, TABLE_COLLATION FROM information_schema.TABLES WHERE  TABLE_SCHEMA = 'pydiodb';
+---------------------+--------+-----------------+
| TABLE_NAME          | ENGINE | TABLE_COLLATION |
+---------------------+--------+-----------------+
| ajxp_changes        | InnoDB | utf8_unicode_ci |
| ajxp_feed           | InnoDB | utf8_unicode_ci |
| ajxp_groups         | InnoDB | utf8_unicode_ci |
| ajxp_index          | InnoDB | utf8_unicode_ci |
| ajxp_log            | InnoDB | utf8_unicode_ci |
| ajxp_mail_queue     | InnoDB | utf8_unicode_ci |
| ajxp_mail_sent      | InnoDB | utf8_unicode_ci |
| ajxp_mq_queues      | InnoDB | utf8_unicode_ci |
| ajxp_plugin_configs | InnoDB | utf8_unicode_ci |
| ajxp_repo           | InnoDB | utf8_unicode_ci |
| ajxp_repo_options   | InnoDB | utf8_unicode_ci |
| ajxp_roles          | InnoDB | utf8_unicode_ci |
| ajxp_simple_store   | InnoDB | utf8_unicode_ci |
| ajxp_tasks          | InnoDB | utf8_unicode_ci |
| ajxp_tasks_nodes    | InnoDB | utf8_unicode_ci |
| ajxp_user_bookmarks | InnoDB | utf8_unicode_ci |
| ajxp_user_prefs     | InnoDB | utf8_unicode_ci |
| ajxp_user_rights    | InnoDB | utf8_unicode_ci |
| ajxp_user_teams     | InnoDB | utf8_unicode_ci |
| ajxp_users          | InnoDB | utf8_unicode_ci |
| ajxp_version        | InnoDB | latin1_swedish_ci |
+---------------------+--------+-----------------+
21 rows in set (0.00 sec)

Do you know where and which logs I can check to get more informations about the error messages given by the GUI ?

Thanks for your help.
Bye

2

You should give read/write permission on /var/www/pydio/[code php] recursively to nginx so that he can carry out the replacement of files/folder during update

3

Hello c12simple,

I did a snapshot before doing this

I am not sure to fully understand what do you mean by “/var/www/pydio/[code php]”. but I run the below command from the repertory “/var/www/pydio” but the error is exactly the same as before.

find . -type f -name '*.php' -exec chmod -R -u+rw {} \;

Could you developp what I should do please ? Or do you have any tips about where I can look for logs about this error ?

Thanks you very much.
Br,

4

Hi again,

I just find out why the upgrade didn’t work as expected. In my case, the file “phpinfo.php” located in “/var/www/pydio” and a custom image in the directory “/var/www/pydio/plugins/gui.ajax/res/themes/orbit/images” was belonging to root instead of “www-data”.

Thanks you.

Best regards,