Move to new Server destroyed Baserow
-
@pbischoff said in Move to new Server destroyed Baserow:
The step "Restoring addons" fails after 30 minutes to hours (don't know exactly)
Most likely the database needs more memory. It's under Services -> Edit -> bump the memory limit a lot and then trigger a restore of the app again (App -> Backups -> the latest backup -> restore).
-
Thanks for your quick reply @nebulon and @girish
I increased the memory of postgres to 1 GB and triggered restore again, but got the same behavior.
After that I observed that mysql also seems to reach the memory limit and so I increased mysql limit to 1 GB as well.
I triggered the restore and have the same behavior. The task gets stuck in "Restoring addons" for hours now.Memory utilization of services
This is a screenshot of the services page.
Mysql and postgres are not reaching their memory limits.
But the server has 4 GB of RAM overall. Maybe this is the limiting factor?Thanks for help
Philipp -
@pbischoff Not sure what is going on, can you write to us at support@cloudron.io , so we can investigate further?
-
-
@nebulon thanks to your advice.
I was wondering how I can update to a "stable" 7.3 version. Normally it should update automatically to the newest version, when I'm getting your knowledge base right. But my Cloudron has version 7.2.5. for a while now and is not automatically updating. Am I doing something wrong here in any config or setting?
When I check for updates, it says that I can update to version 7.3.2, but that it is a prerelease and updating would be on my own risk.