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 }] }
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.