The cause is unclear to me, but the processes that manage incoming and outgoing federation were "stuck" until I manually intervened. It's running now. I'm adding to my to-do list for after my job ends in 10 days to implement some sort of detection and hopefully automated restart for when this happens again.
ok - I took a bit different approach. Since I know what error in rabbitmq's log file is associated with things coming to a stop on fedia.io, I installed swatchdog and set it up to look for that word (which is, btw, "timeout"). I created a script that stops all the messengers, then stops php-fpm, keydb, and rabbitmq. Then it start rabbit, keydb, and php-fpm in order. Finally, it restarts the messengers.
I will be surprised if it works first time, so it may still crash again but I'll be watching
Let me preface my response by saying: my answer is kbin specific. It might or might not also apply to mbin since they may have changed things (or kept older features that kbin changed) since they forked. I know a few of the differences between them, but I haven't kept up with most of mbin's specifics.
Also, if anyone stumbles into this in the far future: note that this post is from March 2024. If that seems like a long time ago, check for newer information...
Can searches be made more specific? On Lemmy, you could define whether you wanted to search for communities/magazines, threads, comments, users and urls.
You can search for magazines specifically from the magazine page. The general search searches in microblogs, thread text -- but not the thread title(?), and comments/replies, I think. You can search for exact user profiles as well with the "@ user @ instance" syntax -- e.g. searching for @TamperTanuki@fedia.io shows a link to your profile as the result. (That also applies to magazines/communties -- e.g. @kbinMeta@kbin.social will find both a user called "kbinMeta" and this magazine as search results -- but searching for magazines from the magazine page is probably better for most use cases.) You can sometimes also find the local version of a federated thread if you search for the original post URL. Note that searching for a post on another instance may not always work; if you're copying a link to a thread you found in a comment post and someone linked to their instance's local version of a thread and that isn't the original source it probably won't find it. (I've had decent luck with it in practice though. For the latter problematic case, load the post on the instance and then find the fediverse link which should take you to the original source and then search for that to find it on your instance.)
@piotrsikora@ernest -- FYI searching for this thread by the exact title "Multiple questions regarding Kbin" does not find it currently but searching text like "as a new Kbin/Mbin user" will find it. Is that a bug?
@piotrsikora@ernest -- Searching for a URL that is not a thread causes a 50x error.
Lastly, you can change the result order (newest/controversial/oldest).
You can change newest/top/hot/active etc. for the results on kbin by clicking on the tabs above the search results.
To send toots/tweets, do I have to specify a magazine? I seem to be unable to send a toot without specifying a magazine first, although I only try to adress a mastodon user directly.
Unclassified microblogs (e.g. from Mastodon users) usually end up in random, but I'm not sure how to post them intentionally since I don't use the microblog feature much. Hopefully someone else can chime in with an answer for this.
Is this even the right magazine to ask these questions in? Is there a dedicated kbin support magazine?
It's fine for kbin questions but you might get a better response for details about your specific instance (which runs mbin) on a local magazine like /m/fedia@fedia.io maybe? Sorry if that doesn't link correctly; I rarely link anything other than lemmy communities. (EDIT: https://fedia.io/m/fedia )
On Lemmy, users can send each others direct messages. It seems like Kbin/Mbin has no way of displaying those direct messages. Is that correct or is there a way to show direct messages?
DMs do not work between kbin and lemmy as far as I know. I have a lemmy alt linked in my profile in case lemmy users want to DM me.
You should be able to send messages to local users on your instance though by going to a user's profile and clicking "Send Message" on the right side.
Trying to access the send message interface for your account from kbin doesn't work here, so I doubt mbin/kbin DMs work. (@ernest this seems to redirect to login and then immediately to the home view instead of opening the message page or showing an error -- is this a bug?)
Hope that helps!
@piotrsikora@ernest -- this thread did not show up on other instances (e.g. I couldn't see it from my alt on reddthat.com despite being subscribed to this magazine from there as well) when I found it originally. I upvoted it here on kbin.social and now it shows up on reddthat. Is that a federation bug (either on fedia.io's side or on kbin.social's side)?
@piotrsikora -- FYI: I got a lot of 50x errors trying to edit this comment.
Thanks for taking the time for your long message. I tried searching for this topic on my lemmy alt. This topic did not show up on either my fedia account, nor the kbin magazine at first, but does now. One more oddity I noticed is that the mbin UI did not hotlink your mentions, but the lemmy UI did so correctly.
Unclassified microblogs (e.g. from Mastodon users) usually end up in random, but I'm not sure how to post them intentionally since I don't use the microblog feature much. Hopefully someone else can chime in with an answer for this.
I can answer this, go to your own profile, choose add new post (not thread) and then from the "select a magazine" dropdown choose random. Then just use your @ tag like normal if you want to @ someone in the fediverse.
The recent version seems to cause PHP to off into space somewhat frequently. I am working to mitigate it - which will likely, at least for a while, require me to restart the services every few hours until we can figure out what the actual cause is.
fedia.io
Top