Solved Backup fails repeatedly because of mongodbdump timeout

[gml]

Hi all

The backups in my Cloudron fail repeatedly with the following message:

Backup failed: Could not pipe http://172.18.0.5:3000/databases/<omitted>/backup?access_token=<omitted> to /home/yellowtent/appsdata/<omitted>/mongodbdump: Request timedout. Logs are available here.

In the last 7 days the backup failed 5 times.

Usually, it is enough to restart the mongodb service and initiate a backup right after the service has started up. Unfortunately, this workaround stopped to work and the backups fail anyway.

Memory wise I already upgraded mongodb two times (it is now 8GB!):

I somehow doubt increasing the memory further will be a longterm solution.

The app that is causing the mongodbdump timeout is a Rocketchat instance.

Any ideas on how to tackle and solve this?

[nebulon]

@gml do you actually get out of memory notifications in your dashboard for the mongodb service? Setting the limit in Cloudron is just the max upper limit, this does not mean 8GB are actually reserved for it, the system as a whole has to have memory available as well.

[girish]

Which cloudron version are you on? We fixed a mongodb related issue in 7.2.2.

[gml]

Thx for your answers!
@nebulon There are no OOM notifications visible in the dashboard.
@girish It's 7.1.4. I would love to upgrade, but a recent backup prior to the upgrade would be nice. It would be great if the issue will disappear on 7.2.2.

[nebulon]

@gml that is sensible. You could enalbe remote SSH support for us https://docs.cloudron.io/support/#remote-support and send us a mail to support@cloudron.io with your dashboard domain, then we can locally patch that timeout value, which should make it work again for you to update finally.

[gml]

@girish So after the upgrade to 7.2.2 the problem vanished. Closing the Ticket.
Thank you for the help!