Notices by Masto.host (mastohost@mastodon.social)

Database Server 14 had a problem.

It stopped responding at around 12:05 AM UTC. I had to issue a manual restart, and at 12:25 AM, it was back online.

So, there was around 20 minutes of downtime for any instance using that server.

Everything looks good now, and I will investigate further to understand what caused the problem.

I am sorry for the trouble this caused.

Thanks 🐘

The Object Storage authentication issue is starting to work.

Some servers may have many background jobs that need to catch up but hopefully it should all be back to normal soon.

There is currently an Object Storage authentication problem that is causing instances to slowdown or to become unresponsive.

The issue is identified and is being addressed: https://public-cloud.status-ovhcloud.com/incidents/9myc4g6tfvlb

Really sorry for the trouble this is causing.

Upgrade installed!

Everyone running on Masto.host is now on Mastodon v4.3.5.

Any issues or questions, please let me know.

Thanks 🐘

I will be starting the installation of Mastodon v4.3.5 on Masto.host.

There will be about 15 seconds of downtime during the upgrade.

Changelog: https://github.com/mastodon/mastodon/releases/tag/v4.3.5

I will be starting the installation of Mastodon v4.3.4 on Masto.host.

There will be about 15 seconds of downtime during the upgrade.

Changelog: https://github.com/mastodon/mastodon/releases/tag/v4.3.4

I'm doing some maintenance in the Masto.host infrastructure. This will cause a reboot on all hosted instances and about 15 seconds of downtime.

No other impact is expected.

@augustocc parabéns 🎉❤️

Upgrade installed!

Everyone running on Masto.host is now on Mastodon v4.3.3.

Any issues or questions, please let me know.

Thanks 🐘

I will be starting the installation of Mastodon v4.3.3 on Masto.host.

There will be about 15 seconds of downtime during the upgrade.

Changelog: https://github.com/mastodon/mastodon/releases/tag/v4.3.3

@ironchamber Well, the backup will only be useful in a last case scenario. There is no easy way to restore it without losing all federation since the backup was generated until the restore happens.

@ironchamber Regarding being safe, it's safe to set a 'Content cache retention period' as long as you are OK with the consequences of losing all cached posts from remote users older than the time you set in there. That signifies that if you favorited, boosted, bookmarked, received a reply from a user that is remote and that is older than that time, that will be lost and unrecoverable.

@ironchamber The easiest way to reduce the database size is to set a 'Content cache retention period', that has consequences like I explain here https://masto.host/mastodon-content-retention-settings/ but that can slow down the growth and even reduce the database size, depending on what you set it to.

Feel free to reach out if you have any questions or if there is something I can help with.

@ironchamber Hello! The work in the web interface and every update is done by the Mastodon dev team, not me. But really glad you like it.

Regarding the database size, the number of local users is not a good deterministic on the storage usage. If you start a new server and follow 200 remote accounts and then never go back to the server, the storage will grow and grow endlessly because every post from those 200 remote accounts will be stored/cached locally.

New post about what happens when a Mastodon server is deleted and the pros/cons of running `self-destruct` before deleting a server.

https://masto.host/what-happens-when-a-mastodon-server-is-deleted/

Upgrade installed!

Everyone running on Masto.host is now on Mastodon v4.3.2.

Any issues or questions, please let me know.

Thanks 🐘

I will be starting the installation of Mastodon v4.3.2 on Masto.host.

There will be about 15 seconds of downtime during the upgrade.

Changelog: https://github.com/mastodon/mastodon/releases/tag/v4.3.2

Our CDN provider (Bunny) is currently experiencing a problem and media files will be failing to load: https://status.bunny.net/incidents/zggwc6h7tcdt

I am monitoring the situation and will inform once I know more.

Sorry for the inconvenience.

Upgrade installed!

Everyone running on Masto.host is now on Mastodon v4.3.0.

Any issues or questions, please let me know.

Thanks 🐘

I will be starting the upgrade to Mastodon v4.3.0 on Masto.host.

This is a large upgrade and I will need to monitor the infrastructure while it is being deployed. So, it can take a while to reach every instance on Masto.host.

You can expect a couple of minutes of downtime during the upgrade.

Changelog: https://github.com/mastodon/mastodon/releases/tag/v4.3.0