Lemmy.ca Support / Questions

501 readers

6 users here now

Support / Questions specific to lemmy.ca.

For support / questions related to the lemmy software itself, go to [email protected]

founded 4 years ago

MODERATORS

Time outs (self.lemmy_ca_support)

submitted 2 weeks ago by GlassHalfHopeful to c/lemmy_ca_support

20 comments fedilink hide all child comments

Ever since things came back up after the Jan 5th outage, I've started to encounter regular timeouts. I will scroll past a couple dozen number posts and then it will stop as of there are no more. Within a few seconds, the application produces a time out error.

I use Boost for Lemmy as my client, but I'm not convinced that the issue is the app since switching my instance allows me to continue scrolling without a problem. And to be clear, prior to January 5th, I've never experienced a timeout in the app.

I'm curious if I'm the only one experiencing timeouts on Lemmy.ca. If so, then I'm curious if the admins are aware of any issue.

you are viewing a single comment's thread
view the rest of the comments

[–] Shadow 2 points 1 week ago (1 children)

I suspect something might be funky with your account, rather than the network / apps. The timeout message is a lie, you're really getting 400 / 499 errors that seem to be related to this lemmy error message:

2025-01-20T17:30:03.366014Z  WARN Error encountered while processing the incoming HTTP request: lemmy_server::root_span_builder: NotAModOrAdmin: NotAModOrAdmin
   0: lemmy_api_common::utils::check_community_mod_of_any_or_admin_action
             at crates/api_common/src/utils.rs:102
   1: lemmy_api::local_user::report_count::report_count

and:

2025-01-20T20:39:43.202677Z  WARN Error encountered while processing the incoming HTTP request: lemmy_server::root_span_builder: CouldntFindPerson: Record not found
   0: lemmy_apub::fetcher::resolve_actor_identifier
             at crates/apub/src/fetcher/mod.rs:22
   1: lemmy_apub::api::read_person::read_person

I wonder if it could be a bug related to the unicode name you've got going on. Did you set that recently, or has it been like that since day 1?

I just restarted all of our docker containers, see if that helps? If not, try setting a normal name and confirm if that changes things?

[–] GlassHalfHopeful 1 points 6 days ago* (last edited 6 days ago)

Well, I've checked out the source. (Rust is very foreign to me. Haha.) However, I can see the offending code now. I don't really have the means to dig further, but I did learn the following:

RE: First error

the error comes from a method performing the following: "Check that a person is either a mod of any community, or an admin."
the code block where NotAModOrAdmin error is returned as had the error check was refactored and moved. but... it looks like it will still act the same in later versions of the BE.
what i cannot say is WHY this being checked. i am neither, so it is_mod_of_any_or_admin == false. but... so what? i neither know why the check is occurring nor why it matters.
the stack trace shows preceding calling method which is report_count(), but no idea what happens before that or why... so unfortunately i didn't learn too much about this "error." i wonder if it would happen still if I was the mod of any given community. it should pass, but again... what would that matter and why? i am literally only trying to load a list of posts from the front page. (seems to happen more often when looking at "All" posts)

Re: Second Error

resolve_actor_identifier make two attempts to get the actor (my user account me thinks). the call to DbActor::read_from_name_and_domain() seems to fail and so webfinger_resolve_actor() is called which also does not come back OK.
it's possible my user isn't being found due to network latency, issues with server response time, or who knows what else.

So the cause? Who knows. Ugh.

Even though this started for me after the defective power supply was replaced... if that's ALL they changed (including not adjusting any server settings at all)... then we shouldn't see this at all. I wonder still if something happened while writing to the DB and the power cut. perhaps something related to my account is unhappy in the DB. Who knows.

You all will be changing hardware providers in the near future. The next version of the BE, which you will eventually update, also adjusts the affected code a bit. And so... maybe it will resolve itself?

One can hope.