Email or username:

Password:

Forgot your password?
Alex's posts Post Back to profile
Top-level
Alex Schroeder

Another strange effect of my #GoToSocial upgrade, perhaps coupled with my other problems – and I really don’t know who is to blame: the Toot! app I use just showed me all my recent direct conversations as “new” (with those weird bubbles along the left side). I don’t think the Mastodon Client protocol offers a “seen” flag so perhaps the messages all got new ids? I have no idea. It’s not very annoying just surprising.

28 October at 0:49 | Open on social.alexschroeder.ch
3 comments
Tom

@alex didn't gts only just implement the direct messages api? Maybe they were just never seen (from that api) by your client?

28 October at 5:04 | Open on goto.ryuslash.org
Alex Schroeder

Today I noticed database corruption warnings in my #GoToSocial database after trying to create an account from the command line. I stopped the service, dumped the data, imported it into a new file, moved the old file away, started to gzip it, and started running out of disk space; aborted the operation, deleted the dump, the new file, moved the old file back, restarted the instance, and it locked up. After a while I realized that perhaps it was those two extra files next to the database, so I removed those and tried again; locked up after a bit; waited for twenty minutes, nothing; restarted it again… and now it works again! But the database is still corrupt in some way. There are a lot of "error dereferencing remote status … : enrichStatus: failed to dereference status author … : enrichAccount: error putting in database: sqlite3: database disk image is malformed (code=11 extended=11)" or "0xc0091c61e0: error processing: CreateAnnounce: error dereferencing announce: EnrichAnnounce: error fetching boost target … : enrichStatus: failed to dereference status author … : enrichAccount: error putting in database: sqlite3: database disk image is malformed (code=11 extended=11)"
There's something about these authors that's not working.
I've added some more notes at the end of this blog post but right now I'm stumped and I have to go to bed. Some other day!

Today I noticed database corruption warnings in my #GoToSocial database after trying to create an account from the command line. I stopped the service, dumped the data, imported it into a new file, moved the old file away, started to gzip it, and started running out of disk space; aborted the operation, deleted the dump, the new file, moved the old file back, restarted the instance, and it locked up. After a while I realized that perhaps it was those two extra files next to the database, so I removed...

29 October at 23:11 | Open on social.alexschroeder.ch
Alex Schroeder

I kept updating my blog post at https://alexschroeder.ch/view/2024-10-27-upgrade-gotosocial … current status is that the system runs, there are no more sqlite errors, as far as I can tell, but there are still occasional lock-ups that I have no explanation for. Monit restarts the instance if the website is down for half an hour (6 failed checks in a row with 5 minutes between checks). I've increased the memory allocation by systemd to high 600M and max 1000M; systemd is reporting about 315M being used, currently.

31 October at 11:33 | Open on social.alexschroeder.ch
Go Up