Cloudron Forum

It looks like the problem is indeed gone with 8.1
Thank you!

For some reason, this never happened before and now happens every night. I cannot stop the (public) Mastodon instance and wait for the backup to complete. So I am patiently waiting for the fix.

Hi there,

It's the second day now that the backup fails with this error message.
The app ID points to Mastodon, which is running fine as far as I can tell.
I am running v8.0.6 with backups to Hetzner Storage Box via sshfs, but I understand correctly, it's not even getting to the upload part.

checkPreconditions errored with code 1 message Command failed: du -Dsb --exclude=*.lock --exclude=dovecot.list.index.log.* /home/yellowtent/appsdata/c5d30482-9837-4fdb-8c21-04ef653d691c du: cannot access '/home/yellowtent/appsdata/c5d30482-9837-4fdb-8c21-04ef653d691c/data/system/cache/media_attachments/files/113/345': No such file or directory du: cannot access '/home/yellowtent/appsdata/c5d30482-9837-4fdb-8c21-04ef653d691c/data/system/cache/media_attachments/files/113/346/860': No such file or directory du: cannot access '/home/yellowtent/appsdata/c5d30482-9837-4fdb-8c21-04ef653d691c/data/system/cache/media_attachments/files/113/346/861': No such file or directory du: cannot access '/home/yellowtent/appsdata/c5d30482-9837-4fdb-8c21-04ef653d691c/data/system/cache/media_attachments/files/113/346/865': No such file or directory du: cannot access '/home/yellowtent/appsdata/c5d30482-9837-4fdb-8c21-04ef653d691c/data/system/cache/media_attachments/files/113/346/867': No such file or directory du: cannot access '/home/yellowtent/appsdata/c5d30482-9837-4fdb-8c21-04ef653d691c/data/system/cache/media_attachments/files/113/347/542': No such file or directory du: cannot access '/home/yellowtent/appsdata/c5d30482-9837-4fdb-8c21-04ef653d691c/data/system/cache/media_attachments/files/113/347/545': No such file or directory du: cannot access '/home/yellowtent/appsdata/c5d30482-9837-4fdb-8c21-04ef653d691c/data/system/cache/media_attachments/files/113/347/541': No such file or directory du: cannot access '/home/yellowtent/appsdata/c5d30482-9837-4fdb-8c21-04ef653d691c/data/system/cache/media_attachments/files/113/347/556': No such file or directory du: cannot access '/home/yellowtent/appsdata/c5d30482-9837-4fdb-8c21-04ef653d691c/data/system/cache/media_attachments/files/113/347/548': No such file or directory du: cannot access '/home/yellowtent/appsdata/c5d30482-9837-4fdb-8c21-04ef653d691c/data/system/cache/media_attachments/files/113/347/550': No such file or directory du: cannot access '/home/yellowtent/appsdata/c5d30482-9837-4fdb-8c21-04ef653d691c/data/system/cache/media_attachments/files/113/347/553': No such file or directory du: cannot access '/home/yellowtent/appsdata/c5d30482-9837-4fdb-8c21-04ef653d691c/data/system/cache/preview_cards/images/001/263': No such file or directory du: cannot access '/home/yellowtent/appsdata/c5d30482-9837-4fdb-8c21-04ef653d691c/data/system/cache/preview_cards/images/001/278': No such file or directory

@joseph Sorry, my bad. I was misinterpreting Mastodon's blog post.

@nebulon Do you have any news for us?

If it'll take longer, can you make 4.2.13 available for the time being?

Ah, thanks! I was already running 8.0.5, but the upgrade to 8.0.6 got stuck. /home/yellowtent/box/setup/start.sh came up with an unbound error. I was able to start box manually and start all apps, but the backup volume did not mount. After installing unbound-anchor, I was able to run /home/yellowtent/box/setup/start.sh without errors, and now the backup is working again.

+1, I'd love to get rid of my AnyDesk subscription.

@necrevistonnezr I've been using it for a while now and did not encounter any problems.

Hi @girish - whatever you did with SSHFS, I am happy to report that after upgrading to 8.0.1, I was able to run a full backup incl. Mastodon for the 2nd consecutive day now.

@necrevistonnezr Works for me. However, I'm not sure if the push service works as it should. Had to manually sync on two or three occasions. Like in the old days.

Off-Topic: I'm considering moving to Proton Pass because I could not get Passkeys working on my Android devices with Bitwarden, but it works perfectly with Proton.

Happens from time to time. I always considered it to be the equivalent of entering a PIN when using my NitroKey or YubiKey.

I did a backup to the local file system before deploying today's Mastodon update. The backup went through without any issues. So I suppose the crash is only related to the upload part (CIFS or SSHFS) of the backup process. I guess you already knew and the result was to be expected, but I'm sharing it anyway just in case.

Thanks for the rapid execution!

Here we go
https://github.com/mastodon/mastodon/releases/tag/v4.2.10

From Mastodon Engineering:

"We are planning to release new Mastodon security updates for versions 4.1, 4.2 and nightly this Thursday, Jul 04, at 15:00 UTC. It solves multiple security issues, including a major one. We encourage server administrators to plan for a timely upgrade to ensure their Mastodon server is protected."

@nebulon
Thanks for looking into this.
Please note that I upgraded to Ubtunu 24.04 after the backup had already crashed for 3 consecutive days. So whatever the reason is was already there with Ubuntu 22.04.

Since my backup does not work anymore after upgrading to 8.0, I thought I can as well go all-in and do the Ubuntu update as well. It went smoothly and I did not discover any issues. It did not resolve the backup problem, though.

I switched from CIFS to SSHFS to check if it makes a difference. Unfortunately, the backup task crashes, too.

@girish There are lots of entries in dmesg, but I have no clue what exactly I am looking for.
Yes, I am able to access the CIFS volume. And the backup task actually has uploaded files on every run. It just seems that it could not finish the task.
I am used to the backup stalling (going down to 0 kbit/s), but before the 8.0 upgrade, it was eventually finishing what it had begun.