Full Cloudron Backups are failing on Cloudron version 7.7.0

[skeats]

@ChristopherMag I am on kernel version 5.15.0-102

[ChristopherMag]

I have made a /backups directory and run sudo chown yellowtent:yellowtent /backups and then configured the system to backup to that directory and am currently running a backup.

After that completes I will work on copying that over to /mnt/cloudronbackup

@skeats ps, if you want to paste logs I recommend putting ``` on a new line before the log output and ``` on the line after the log output and then the system will format it with a fixed width font and make it easier to read. Same thing when including commands inline by adding ` at the start of the command and ` at the end of the command so that ps -a turns into ps -a. You can try it out by editing your previous posts if you want to try it.

[necrevistonnezr]

If you’re on 22.04, you can safely update to the 6.x kernel: https://www.omgubuntu.co.uk/2023/08/ubuntu-22-04-linux-kernel-6-2

[ChristopherMag]

@nebulon I have added the previously used cloudron backup directory as a volume in cloudron and mounted it.

I am about to run cp -r /backups/2024-04-11-161325-365 /mnt/volumes/43cfcd99b751486ea8b2f56a194eb88b

Given that the snapshot directories are different in the local /backups folder vs the remote /mnt/volumes/43cfcd99b751486ea8b2f56a194eb88b is that going to cause an issue now or later when I switch back to using the original cifs share as the backup destination?

[ChristopherMag]

@necrevistonnezr The article made it sound like running sudo apt update && sudo apt full-upgrade would get the update and this was back in 2023 so wouldn't we already have it given that cloudron runs apt to do updates periodically?

I also didn't see anything that would update the kernel in the output of sudo apt upgrade listed in my post above. The article also indicated that this would be included in new ISO's but this server was just installed from a freshly downloaded iso about a month ago so it doesn't seem to be included in recent ISOs either.

[ChristopherMag]

@necrevistonnezr I think if I am understanding this correctly ubuntu has this notion of a HardWare Enablement (HWE) kernel that they maintain for older releases but it isn't the default. So in my case I believe I would need to run sudo apt install linux-generic-hwe-22.04 to get the HWE kernel which would be a 6.x kernel and should resolve this issue.

[ChristopherMag]

@skeats I have run sudo apt install linux-generic-hwe-22.04, rebooted, confirmed via uname -r that I am running 6.5.0-27-generic, reconfigured my backup settings (you probably wont have to do this as I was changing things to get a local backup), and now I can backup to the cifs share again.

@necrevistonnezr Thank you for pointing me in the right direction to be able to use the HWE kernel to bypass this bug.

[skeats]

@ChristopherMag thank you because I ran that command and it worked and my backups are working again with the 6.5.0-27-generic kernel!

[odie]

I had the same issue. For me, it worked to enable “use seal encryption” in the backup configuration. At least when I triggered a manual backup it worked. I’ll just have to wait to see if the scheduled backup runs as well.

[necrevistonnezr]

@ChristopherMag said in Full Cloudron Backups are failing on Cloudron version 7.7.0:

@necrevistonnezr The article made it sound like running sudo apt update && sudo apt full-upgrade would get the update and this was back in 2023 so wouldn't we already have it given that cloudron runs apt to do updates periodically?

apt full-upgrade is non-standard and not run by Cloudron, I believe.

[nebulon]

Please do not run a full apt upgrade as such, as it may update packages which Cloudron relies on and could render the instance broken. Explicitly updating the kernel should be ok though.

[girish]

Another customer of ours hit this issue. I wonder what has changed that suddenly CIFS requires SEAL encryption. We have made this default now for next release in any case.

[ChristopherMag]

@girish I don't think it requires seal encryption.

I believe using seal encryption causes a different code path to be taken that avoids the underlying bug but it is not the presence or absence of seal encryption in and of itself that I believe fixes the issue.

After a kernel upgrade this works fine without seal encryption though I have now enabled it as it seems like a good idea to have anyway so making it the default is probably a good idea but as long as Ubuntu 22.04's default kernel version is 5.15.0-102 this issue will likely still occur.