Backups appear to not work after upgrade

[nebulon]

@robin looks like something in the backup config migration during the release is off. Is that mountpoint by any chance sshfs?

[Robin]

@nebulon said in Backups appear to not work after upgrade:

@robin Is that mountpoint by any chance sshfs?

Yes, it is indeed sshfs

[girish]

@robin Can you tell me how you mounted your sshfs i.e the mounting options ? It seems that chown does not work. @nebulon hit a similar issue but I haven't managed to reproduce it but it seems to be maybe related to sshfs in ubuntu 18. I am just testing this out.

[girish]

I figured out the problem. It happens with sshfs is not mounted as "root" user.

[Robin]

@girish Yeah, I'm using uid=yellowtent,gid=yellowtent, so I think that is indeed my problem

[mazarian]

Seems like I'm having the same issue. Is there a workaround for this? Not quite sure how to fix it!

[girish]

@mazarian We have put in a fix in 6.3.5. Can you try updating to that by going to Settings -> Check for updates. And then you have to update with "Skip backup" checkbox checked since of course the backups are failing.

After the update, you can configure the Backups to use the new SSHFS backend. Can you please try that?

[Robin]

@girish Fix seems to have worked for me, thanks!

For satisfying my own curiosity, can you explain why using the mountpoint method was no longer sufficient?

[mazarian]

@girish Thank you! I was already on 6.3.5 and was experiencing that issue. I decided to delete the /mnt/cloudronbackup directory and set the SSHFS settings again (I had already reset the SSHFS settings with no success) and it works now. The permissions of the new cloudronbackup directory are totally different.

Initially, the cloudronbackup directory was root:root. Then I got a warning saying it should be yellowtent:yellowtent- it still didn't work after making that change.

Not Working:
drwxr-xr-x 3 yellowtent yellowtent 4.0K Jul 11 21:33 cloudronbackup

Working:
drwxrwxrwx 1 1032 users 100 Jul 12 14:09 cloudronbackup

[girish]

@mazarian that's correct, the permission is the thing I fixed in 6.3.5. Glad it's working now and thanks for reporting back!