Ok, if you run mastodon with any username -other- than 'mastadon' then your psql db user has to have -THAT- username in it.
This is obvious in retrospect but apparently I've been burning caffeine like nothing else today.
Remote
Munin
@munin@mastodon.social
mastodon 4.8.0-nightly.2026-10-06You probably want @munin@mastodon.hasameli.com
568 Followers
39 Following
13 Posts
Joined March 21, 2017
Whoever is trying to fax me from New Hampshire needs to stop.
First and foremost, I am NOT the person you're looking for.
Second, this is the 21st century. Yes, I realize that the medical profession is largely lodged in the 18th, but kindly get with the program.
....OK, finding a bug here, apparently. You'll want @ munin @ mastodon.hasameli.com for the me on the instance that's mine.
Replying to
[Not counting the ruby gems or the...........]
Wait, what? 1055 more?
....42THOUSAND more?
What is this thing installing?
Testing 123
Alrighty. This looks like it's working correctlyish, so I'll be absconding over to the me at hasameli.
HAH
My instance has come up by -itself-
Now to look into how to administer the benighted thing.
Replying to
@er1n@mastodon.social The 'deployment guide' is written for ubuntu 16 which is accursed with that benighted garbage fire.
@NickDe@mastodon.social You're not the only one.
Replying to
@er1n@mastodon.social The current hell is systemd.
Systemd is, of course, an utter travesty that needs to die, horribly.
[I can get the instance to run by hand at the moment, but the 'streaming' service won't start by itself because of some idiocy that systemd entails....troubleshooting THAT right now]