#tootctl — Public Fediverse posts

I've cleaned up my Mastodon instance's headers and purged old assets, and woah, this is a huge cleanup.

The issue was, iDrive e2 had randomly started to give timeout errors on my api key, so I could not even browse the bucket with another client. I'm assuming it's due to having too much object in the storage.

The errors were like this:

> Net::ReadTimeout with #<TCPSocket:(closed)>

Here's some before and after:

#mastoadmin #mastodon #idrive #idrivee2 #s3 #tootctl

Frage an die #Mastodon #administratoren

mein Server ist zu ca. 60% "voll" - den größten Teil davon beansprucht der Ordner cache/media_attachments und accounts

die Admin-tools #tootctl cache clear, media remove usw habe ich durch - kleine Verbesserungen ja - aber der Server schleppt noch immer gut 51,3 GB (!!) Daten mit von denen nur gut 0,05 GB local sind - doch wie bekommt ich diese nachhaltig bereinigt ??

ach ja - aufbewahren von Inhalte ist auf 2 Tage gesetzt

Bild = tootctl media usage

@zaherg You see now why I have been trying to find a decent #storage and #cdn solution now? 😆

Usage shows 16.25 GB on my bucket solution.

You can find the details attached. Headers take a lot of space, but this #pr on #github will bring a #tootctl command to remove them on the next release:

https://github.com/mastodon/mastodon/pull/22149

The story: https://github.com/mastodon/mastodon/issues/9567

I didn't want to kill my #ssd on the long run, and settled on #idrive #idrivee2 for #s3 storage, and #cloudflare for cdn solution.

#mastoadmin