I upgraded from 6.1.2 to 6.2.4. After the upgrade, following apps are stuck in " Restarting - Waiting for Cloudron to initialize":
- Invoice Ninja
- Rocketchat (2x)
Following Apps could start:
- Riot / Element
- Simple Torrent
I assume it could be a DB issue.
I did already reboot the server, restart box, restart mysql, mongodb & postgresql, no success so far.
@gml Yes, it seems some servers hit this issue. Still investigating why. As a workaround,
- Around line 785, comment out this line:
// return iteratorCallback(app.installationState === apps.ISTATE_ERROR ? null : error);
- systemctl restart box
This will make the code and apps come up step by step. You might have to restore a few apps manually from their last backup after the upgrade is complete.
Thx @girish, that solved it!
Should the line be activated after everything is up and running again?
BTW: I was looking for an option to rollback the upgrade to the previous release - is it somehow possible to rollback the whole cloudron to a backup without setting up everything from scratch?
@girish That works, yes. But my question was if there is a way to rollback a complete cloudron upgrade (so including the box part). In some cases this is the fastest path when you need the services up and running quickly.
I just saw that Sogo is not responding. Restore the backup and restart the app did not help. The logs say the following:
Mar 14 20:19:14 => Convert the sql schema
Mar 14 20:19:14 Converting c_content from TEXT to LONGTEXT in the sogo_user_profile table
Mar 14 20:19:14 mysql: [Warning] Using a password on the command line interface can be insecure.
Mar 14 20:19:14 ERROR 2026 (HY000): SSL connection error: unknown error number
@gml The SOGo issue is because you are using the old sogo app. We haven't been maintaining that package for over 2 years now. You can verify this by going to the Updates section. The Package Version field shows the appstore id as
nu.sogo.cloudronapp. The new SOGo app has the package version as
Are you able to migrate to the new package? You have to just install new sogo and emails etc should be there already.
@girish As i'm using Sogo for calendars - nope, that's not possible to migrate... And as it does not start, it's also not possible to download the data and start from scratch via import. Anyway, no need for me to put extra efforts in it - but for Businesses this would not be a good situation I guess.
Are there other apps that have been silently replaced with a new version which is not updatable and will be deprecated? Did I miss communication about it or was there none? Probably an indicator in the GUI would help, like a (!) top right at the App tile, where you find more information about the app being deprecated and you need to migrate (or a migration routine in cloudron directly would be preferred i think).
@gml we would announce such a new appstore id with deprecation of an app package ideally with migration steps. The SOGo move was mentioned at https://blog.cloudron.io/cloudron-2-3-released/ but I guess that was not enough for this case.
Since that SOGo version cannot work with the new mysql addon, the app has to be restored onto a Cloudron version 6.1.2 then the app will be able to run for exporting the data. We did not really expect anyone to still be on that old version and since we don't closely track users, it is hard to tell from our side. Still unfortunate situation.
As a heads up, invoice ninja will face the same. There is no automatic migration path from v4 to v5 . Which is why both versions are available currently in the app library (while v5 is unstable) There is an official migration guide, but generally once they stop pushing upstream v4 releases, that app cannot be maintained much further then.
app has to be restored onto a Cloudron version 6.1.2 then the app will be able to run for exporting the data
Did this. Calendars present but no content. No contacts either. Same username.
This is terrible. Please advice. Following "install new sogo and emails etc should be there already" wiped my data.
@yusf hm I am not sure anymore how users are mapped in that old instance, looks like they are not mapped by username but maybe uid which is a uuid so that would not help. I guess you would have to restore the Cloudron wholesome to the old version