Upgrade: OC8.2.7 -> OC9.0.5 -> OC9.1.1 | "**Installation Error and Hangup Solved**" || & "**Internal Server Error solution**"

I had a constant problem with OC 8.2.7 and the Clients for OSX and Android. OSX Clients reported "Internal Server Error", and hung up the Syncs. After reading and hunting off and on for a solution for the last few months, I read that the problem maybe solved by an Upgrade o the Server to OC 9.1.1.
First I had to upgrade to OC 9.0.5 by unpacking the tarball (zip) and installing as directed by https://doc.owncloud.org/server/9.1/admin_manual/maintenance/upgrade.html.
It worked fine for upgrade from OC 8.2.7.
Upgrade to OC 9.1.1. produced errors, even if I followed exactly the same procedure as upgrading the OC 9.0.5.
Upgrade to the OC 9,1,1 produced an error at install and prompted to reload the browser page. Then the following appeared:


"This ownCloud instance is currently in maintenance mode, which may take a while.

This page will refresh itself when the ownCloud instance is available again.

Contact your system administrator if this message persists or appeared unexpectedly.

Thank you for your patience.


Now it hangs there and reloading the page makes no difference.

Checking with ps and top there does not seem to be any problems or overloads.

Any Ideas?

https://doc.owncloud.org/server/9.0/admin_manual/configuration_server/occ_command.html#maintenance-commands-label

sudo -u www-data php occ maintenance:mode --off

Turn off maintenance mode after the update

Thanx for the quick reply mrow4a!

Did that and now I have an error with the set-up of memory:

sudo -u apache php occ maintenance:mode --off

PHP Fatal error: Allowed memory size of 262144 bytes exhausted (tried to allocate 12288 bytes) in /var/www/vhosts/default/htdocs/oc911/lib/base.php on line 139

Not a programmer and I see no setup possibility in base.php.

Where do I set the memory?

BR

OK, I found php.ini and it was changed because a previous installation also complained. It is set to 256M.
Restarted httpd service, but it would not deactivate the maintenance mode yet.

What steps did you do in order to upgrade your installation from OC 8.2.7 - OC 9.0.5? Are you sure you did it correctly?

https://doc.owncloud.org/server/9.1/admin_manual/maintenance/manual_upgrade.html

https://doc.owncloud.org/server/9.1/admin_manual/maintenance/upgrade.html

?

I followed the procedure as I said in my OP on Website: https://doc.owncloud.org/server/9.1/admin_manual/maintenance/upgrade.html

The first upgrade to 9.0.5 worked first shot. I may have to redo the OC 9.1.1 again on a test website.

Will report back ... it takes quite a long time with my data.

I had some problems with the VPS Inodes - they were exhausted. It prevented some file transfers and configurations to be written.

Upgrade OC_8.2.7 -> OC_9.0.5 -> OC_9.1.1 works perfectly when following:

Installation Step-by-Step in 10 Steps:

Ref: https://doc.owncloud.org/server/9.1/admin_manual/maintenance/upgrade.html.
For CentOS 6 (ignore quotation marks "_" when copying)
0. unpack owncloud-9.0.5.zip into /home/user/user_name/owncloud.
1. Copy original to temp directory to do update and test.
"sudo copy /var/www/vhosts/default/htdocs/oc/data /var/www/vhosts/default/htdocs/oc905/data" (Copy original to temp-upgrade directory).
"sudo copy /var/www/vhosts/default/htdocs/oc/config /var/www/vhosts/default/htdocs/oc905/config".
Note: /var/www/vhosts/default/htdocs/oc905 will be updated first and moved back to /var/www/vhosts/default/htdocs/oc later.
2. Delete unwanted files and directories, and move unpacked new files to web-server document_root.
"rm -R /home/user_name/owncloud/data" if it exists (mostly not there) &
"rm -R /home/user_name/owncloud/config" (is always there).
"sudo mv /home/user/user_name/owncloud/* /var/www/vhosts/default/htdocs/oc905/*" (or /var/www/vhosts/default/htdocs/owncloud/* if you prefer).
3.1. Copy data and config from original system into update system.
"sudo copy -R /var/www/vhosts/default/htdocs/oc905/data /var/www/vhosts/default/htdocs/oc905/data"
"sudo copy -R /var/www/vhosts/default/htdocs/oc905/config /var/www/vhosts/default/htdocs/oc905/config"
4.0. Set owner: "sudo chown -R apache:apache /var/www/vhosts/default/htdocs/oc905"
4.1. Set access: "sudo chmod -R 750 /var/www/vhosts/default/htdocs/oc905"
5. Browser login to https://URL/oc905/ for updating new system.
6. Follow instructions on Web-server screen output.
7. Old system is still live and available at https://URL/oc/ (or https://URL/owncloud - depending on your setup)
8. When update is finished at https://URL/oc905/, then it automatically opens the login screen for the updated site.
9. Swap directories to use old URL's for new system: "sudo mv /var/www/vhosts/default/htdocs/oc /var/www/vhosts/default/htdocs/oc-8xx-backup", and "sudo mv /var/www/vhosts/default/htdocs/oc905 /var/www/vhosts/default/htdocs/oc" (or /var/www/vhosts/default/htdocs/owncloud).
10. Finish.
... To upgrade to CO_9.1.1 follow exactly same procedure and use /var/www/vhosts/default/htdocs/oc911, just replace all the 905 labels with 911 ...

Additional Info to "Internal Sever Error" with Clients:

Installing OC_9.1.1 indeed solved the problem of OSX clients reporting "Internal Sever Error" in my case. See below.

Installing OC_9.1.1 indeed solved the problem of OSX clients reporting "Internal Sever Error" in my case.

The installation was not a mere update, nor a complete empty installation. Elsewhere in this thread (No. 7) is my How-To for an installation with previous data and configuration directories incorporated into a new installation.

Systems:
Server: centos-6-x86_64, CentOS release 6.8 (Final)
Client: OSX (Version 2.2.3 (build 3601).)

1 Like