After some time, Girish has added extra code that would increase re-tries count and timeouts, so eventually B2 started working, more or less.
With this said, I've just switched over to Hetzner and will see how that will work for me. Don't feel like paying money to B2 if their backend is overloaded and constantly results in various issues.
@joseph I cannot even fathom how switching off IPv6 would help with this issue, but since you're saying that backup task uses MySQL db and connects to it - who knows, maybe IPv6 might have some effect there.
I've checked logs for mysql. There are few of them there zipped and they all are 0 bytes / empty, even on the days when backup task fails.
Backup keeps failing - in the past 4 days it succeeded only once. This is getting really annoying as not having backups for DR is a problem.
Hi guys,
I've been using Backblaze for backups for some time now. Lately have been seeing issues with a lot of automated backups just stalling and not finishing - navigating to Backups screen shows a backup task in progress with some random step it's at and it wouldn't time out (today it was sitting there after 9 pm, while the backup is scheduled to kick off at 1 am).
Happens about 50-60% of the time lately - for example over the past week I had only couple successful automated backups. I've planned on upgrading from 7.x to 8.x and it took me 3 or 4 attempts over the weekend before a backup finally went through. So I could then finally upgrade my Cloudron.
Using basic .tgz format for backups (seems to be the fastest way).
What I see in backup logs is the following:
2024-09-23T15:07:18.019Z box:database Connection 194 error: Packets out of order. Got: 0 Expected: 2 PROTOCOL_PACKETS_OUT_OF_ORDER
2024-09-23T15:07:18.020Z box:database Connection 195 error: Packets out of order. Got: 0 Expected: 2 PROTOCOL_PACKETS_OUT_OF_ORDER
2024-09-23T15:07:18.021Z box:database Connection 197 error: Packets out of order. Got: 0 Expected: 2 PROTOCOL_PACKETS_OUT_OF_ORDER
I've seen something very similar before.
Not sure if Backblaze is to blame - I've had some issues with them few months ago, when I couldn't properly access my files via their website. After a ticket things started working fine, but it's been couple of month since then. And if they are to blame, I'd appreciate some guidance on where / how I can obtain logs / details that would prove it's them and not me.
Thank you!
@djxx Sorry, I don't know what you mean exactly. If we're talking about backup configuration, then I have memory limit set to 1.5GB and upload part size to 10MB. Don't think I've changed any of these values, when setting up Backblaze as a target.
If what your second message says about RAM required > projected backup size, then I would see it as a problem with Cloudron. I cannot imagine how that could be the case with installs with data in tens of gigabytes in size. @nebulon is that really the case?
My backups are about 6.5 GB, if I were to trust Backblaze console.
@Nozy Thanks for letting me know about IPv6. Didn't event think whether it's enabled or not, and turns out it is.
Would turning it off have any detrimental effects on Cloudron, do you know? Do I need to be aware of something before switching it off?