Today at 12:35 my Nextbox started to upgrade Nextcloud.
Since then I get the error, when I try to open the nextbox website. All connecting apps give me an http 500 error, too.
What I tried already:
Reboot of the nextbox
I have ssh access. But i did nothing special there. I noticed the admin page was complaining about some column format, but think this has nothing to do with the problem.
Is this update error already known, is nitrokey working on this?
I may send some logs, if you say which ones you need.
i think i made a little progress: Even occ got me an exception. the message said something about custom_apps/spreed/… . So i moved the spreed folder to spreed.broken. Now php occ apps:list is working again. It lists me the spreed.broken app as disabled (as i would expect.) Somehow spreed got installed by itself again, it is now listed as active again with working occ.
Now the Nextcloud was in maintenance mode. After an hour time, looking into the logs, the problem solved itself now.
(PS, i used the ssh access and worked inside the docker image.)
This threw an exception. I don’t have the exact error trace anymore, but it complained about 'custom_apps/spreed/’
You may adapt if some other app seems to be the cause.
What i would try now is
php occ app:disable spreed
What i did was moving the folder custom_apps/spreed to custom_apps/spreed.broken
Then i exited the container, and did sudo shutdown -r now.
After that i waited some hours. The spreed package got new installed by itself. And everything started working again. So i cleaned up by removing the spreed.broken directory
i figure it is richdocuments in my case. Disabling is not working, again a trace pops up. i now renamed the folder and will reboot - keep you updated in a few hours - thanks for the comprehensive guide!
well, i am back again on purple LEDs … this time php occ app:list is not throwing an error. @Thamos any chances you can throw me some ideas what do look at?
Box in general reachable but stays on purple (or falls back shortly after going to green) after pressing the reset pin for one time a short period of time
/solved: probably the nextcloud had a reboot cycle or something and occ stumbled over the richdocuments.old folder i created / renamed richdocuments before.
What helped identifying? tail -n 200 /var/log/nextbox.log with some big red errors
Great — thanks for solving the problem and sharing your solution. I had a good instinct when I cleaned up the folders; that saved me some trouble. I get the feeling the occ tool is very brittle when it comes to custom apps. That seems like a poor design choice in Nextcloud, but I don’t know enough about Nextcloud to complain — I’m just happy when it works.
Vielleicht kann einer von Nitrokey ( @daringer oder @jan.knittel ) erklären wie es immer wieder zu solchen Problemen kommt und wie das gelöst werden könnte. So wie ich es verstanden habe sollten eigentlich die custom apps deaktiviert werden bevor das Update durchgeführt wird damit es nach dem Update eben nicht zu solchen Problemen kommt. Vielleicht wäre ein Watchdog für den Update-Prozess sinnvoll?
now.