Iâm running the Nextcloud Box with the Raspberry Pi in it. My guess is the update to 15 is being pushed out because today I found my desktop client greyed out and going to the web page I see:
This Nextcloud instance is currently in maintenance mode, which may take a while.
That was about 4 hours ago. Iâm not sure how long I ought to wait before doing something like rebooting the system. I have to look at the actual system so seldom Iâll have to look up my password I think.
I havenât seen a reply yet so Iâve been trying things.
One was running the command âsudo nextcloud.occ maintenance:mode --offâ
This echoes a warning that comes up in red when I type âsudo nextcloud.occ upgradeâ concerning updatenotification. I now see this message when I go to the web interface:
âThe files of the app (updatenotification) were not replaced correctly. Make sure it is a version compatible with the server.â
I have no idea what I ought to be doing at this point.
Well, I may have messed up big time here. I tried âsudo snap revert nextcloudâ
This has a good result, which is the desktop sync clients are working again, because I just got files that I dropped into a folder a work on my home machine.
This has a bad result, the web interface is totally messed up.
Then I did âsudo nextcloud.occ maintenance:mode --offâ
Got same error in browser," Error The files of the app (updatenotification) were not replaced correctly. Make sure it is a version compatible with the server."
Edit: also returned the following in SSH terminal:
Nextcloud or one of the apps require upgrade - only a limited number of commands are available
You may use your browser or the occ upgrade command to do the upgrade
Maintenance mode disabled
Tried, âsudo snap refresh nextcloudâ but got âsnap ânextcloudâ has no updates availableâ
There is a message on RPi CLI, âNew release â18.04.1 LTSâ available. Run âdo-release-upgradeâ to upgrade to it.â but not sure how that could be relevant.
Interesting, I tried that snap refresh command and Iâm back to maintenance mode and no client response.
The revert command that messed up my web interface reported it had gone back to version 13. The refresh command says Iâm a ânextcloud 14.0.5snap1â
Not sure which I prefer, partly working, or back to my original issue.
Same issue here on Nextcloud Box. Standing By. Only interesting thing discovered is the result of running:
sudo nextcloud.occ status
Produced:
ERROR: ld.so: object â/usr/lib/arm-linux-gnueabihf/libarmmem.soâ from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.
The current PHP memory limit is below the recommended value of 512MB.
Nextcloud or one of the apps require upgrade - only a limited number of commands are available
You may use your browser or the occ upgrade command to do the upgrade
Solved ? Here is what I just tried and it seems to be workingâŚ
=> Turned off maintenance mode.
sudo nextcloud.occ maintenance:mode --off
=> Reloaded Nextcloud Web Interface, recieved the following.
The files of the app (updatenotification) were not replaced correctly. Make sure it is a version compatible with the server.
=> Reloaded Web page. It reloaded with the following -
Nextcloud will be updated to version 14.0.5
These apps will be updated:
Activity (activity)
Auditing / Logging (admin_audit)
Comments (comments)
WebDAV (dav)
Default encryption module (encryption)
Federated file sharing (federatedfilesharing)
Federation (federation)
Files (files)
External storage support (files_external)
PDF viewer (files_pdfviewer)
File sharing (files_sharing)
Text editor (files_texteditor)
Deleted files (files_trashbin)
Versions (files_versions)
Video player (files_videoplayer)
First run wizard (firstrunwizard)
Gallery (gallery)
Lookup Server Connector (lookup_server_connector)
Notifications (notifications)
OAuth 2.0 (oauth2)
Password policy (password_policy)
Provisioning API (provisioning_api)
Monitoring (serverinfo)
Share by mail (sharebymail)
Usage survey (survey_client)
Collaborative tags (systemtags)
Theming (theming)
Two factor backup codes (twofactor_backupcodes)
Files workflow engine (workflowengine)
Please make sure that the database, the config folder and the data folder have been backed up before proceeding.
To avoid timeouts with larger installations, you can instead run the following command from your installation directory:
Yes!
Dez, Thank you!
Followed your instructions, and exactly the same happened for meat all stages.
All working on the web interface now
I havent set up the client yet, but will report back in a mo to confirm if that works too - Iâm sure it will