this post was submitted on 05 Aug 2023
10 points (100.0% liked)

Lemmy Support

4651 readers
13 users here now

Support / questions about Lemmy.

Matrix Space: #lemmy-space

founded 5 years ago
MODERATORS
 

Hello !

My instance is up and running (obligatory YaY!) so these errors are not that important, but I'd like to know what they are and if there is something I can do about them.

Thank you all!

.

Is there some way to increase the number of slots, or should this like never happen on a tiny server on a beefy CPU?

lemmy_1     | 2023-08-05T10:28:15.621675Z  WARN lemmy_server::root_span_builder: Timeout occurred while waiting for a slot to become available

.

Some sort of miss-match and voting related?

lemmy_1     | 2023-08-04T18:38:02.484727Z  WARN lemmy_server::root_span_builder: data did not match any variant of untagged enum PageOrNote
lemmy_1     |    0: lemmy_apub::activities::voting::vote::verify
lemmy_1     |              at crates/apub/src/activities/voting/vote.rs:57
lemmy_1     |    1: lemmy_apub::activities::community::announce::receive
lemmy_1     |              at crates/apub/src/activities/community/announce.rs:144
lemmy_1     |    2: lemmy_server::root_span_builder::HTTP request
lemmy_1     |            with http.method=POST http.scheme="http" http.host=lemmy.mindoki.com http.target=/inbox otel.kind="server" request_id=6df4916b-4d99-4f4b-af9f-19f50e893991
lemmy_1     |              at src/root_span_builder.rs:16
lemmy_1     | LemmyError { message: None, inner: data did not match any variant of untagged enum PageOrNote, context: SpanTrace [{ target: "lemmy_apub::activities::voting::vote", name: "verify", file: "crates/apub/src/activities/voting/vote.rs", line: 57 }, { target: "lemmy_apub::activities::community::announce", name: "receive", file: "crates/apub/src/activities/community/announce.rs", line: 144 }, { target: "lemmy_server::root_span_builder", name: "HTTP request", fields: "http.method=POST http.scheme=\"http\" http.host=lemmy.mindoki.com http.target=/inbox otel.kind=\"server\" request_id=6df4916b-4d99-4f4b-af9f-19f50e893991", file: "src/root_span_builder.rs", line: 16 }] }
top 3 comments
sorted by: hot top controversial new old
[–] Loulou@lemmy.mindoki.com 1 points 1 year ago (1 children)

I made some analysis on a 150MB log output (see below, each line is a warning of the type listed)

So some seems (or are at least rare) to be quite harmless, but there's two who concerns me (BTW; they are all brought to attention by this line: WARN lemmy_server::root_span_builder: HereTheErrorMessageBelow) :

  • 32754 times: Timeout occurred while waiting for a slot to become available
  • 16670 times: data did not match any variant of untagged enum PageOrNote

Also maybe this might hint on a software bug:

  • 380 WARN lemmy_server::root_span_builder: expected value at line 1 column 1

Just FYI it's running on a fresh Linux Mint install on a 8-gen hexa core on a 1Gb/s/0.7Gb/s internet line so I do not think I'm limited in any way.

Is there any way of digging up why this is happening? I downloaded the sources but I'm a C/C++ programmer, not a Rust(?) one :-) but who knows if I can get a couple of pointers ...

Cheers

      9 ./out/arenting not implemented
     43 ./out/cant accept local object from remote instance
     17 ./out/couldnt_find_community: Record not found
      2 ./out/couldnt_find_community: Timeout occurred while waiting for a slot to become available
      2 ./out/couldnt_find_object: data did not match any variant of untagged enum SearchableKinds
      5 ./out/couldnt_find_object: invalid query
     31 ./out/couldnt_find_post: Record not found
      1 ./out/couldnt_find_post: Timeout occurred while waiting for a slot to become available
      1 ./out/couldnt_find_that_username_or_email: Record not found
      3 ./out/couldnt_get_comments: Timeout occurred while waiting for a slot to become available
      1 ./out/couldnt_get_posts: Timeout occurred while waiting for a slot to become available
      1 ./out/couldnt_like_comment: Timeout occurred while waiting for a slot to become available
    834 ./out/data did not match any variant of untagged enum AnnouncableActivities
  16670 ./out/data did not match any variant of untagged enum PageOrNote
     24 ./out/data did not match any variant of untagged enum PersonOrGroup
      3 ./out/duplicate key value violates unique constraint "idx_person_lower_actor_id"
    380 ./out/expected value at line 1 column 1
      4 ./out/Http urls are only allowed in debug mode
      1 ./out/incorrect_login: incorrect_login
      1 ./out/insert or update on table "post_like" violates foreign key constraint "post_like_post_id_fkey"
      3 ./out/Invalid community: Invalid community
    318 ./out/Matching variant not found
     16 ./out/No community found in cc: No community found in cc
      4 ./out/Not a mod: Not a mod
      2 ./out/not_an_admin: not_an_admin
     57 ./out/not_found
      1 ./out/out occurred while waiting for a slot to become available
      1 ./out/Person is banned from site: Person is banned from site
      8 ./out/Post is locked: Post is locked
    666 ./out/Record not found
  32754 ./out/Timeout occurred while waiting for a slot to become available
      1 ./out/Webfinger regex failed to match
  51864 total
[–] Loulou@lemmy.mindoki.com 2 points 1 year ago

3 dayis later:

 1357 ./out/data did not match any variant of untagged enum AnnouncableActivities
  772 ./out/expected value at line 1 column 1
 1086 ./out/Record not found
16426 ./out/data did not match any variant of untagged enum PageOrNote
45962 ./out/Timeout occurred while waiting for a slot to become available

I'm a keeping an eye on this.

[–] Sukuoru@lemmy.neeley.cloud 1 points 1 year ago

I have also seen one of these errors since the upgrade to 0.18.4 on my single user instance, and it looks like there is a bug report on Github for:
times: data did not match any variant of untagged enum PageOrNote
Here is a link to the issue.

I can't comment on the other error, however I would love any/all detail on how you got detail on your errors. Awk/sed/count etc escape me, and I found your post while searching for the error I saw. I have a similiar one-liner for finding exim_mainlog ip spam, but I am not sure how to adapt to something so different.

Though, I did deploy using ansible and am looking at the logs using docker, maybe I am using the wrong approach.