Closed zephryn closed 3 years ago
update: the server acl errors might not be directly related to the panic, my bad ^^ issue #1844 seems to mention a similar problem in regards to the NID errors.
yet another update: fixed it, at least enough to get back onto my account! had to go into federationsender.db
and remove the last entry in federationsender_joined_hosts
and also removed the event entry from roomserver.db
in roomserver_events
, but i'm not sure if modifying the second db mentioned helped to resolve the issue since it still panicked when not removing the entry from the former.
This was fixed in https://github.com/matrix-org/dendrite/pull/1824 which is on master
but is unreleased yet.
Background information
go version
:go1.16.3 linux/amd64
Description
when (re)starting my dendrite instance, it panics immediately with the following logged from stdout/stderr. i've removed the timestamps + personal information and reformatted one of the single-line logs for brevity and to hopefully make it a bit more readable.
these seem normal, just included for context.
right after, though, it repeats this error for four different rooms:
then, it panics:
before today, things were running just fine aside from noticing that dendrite was using a surprising amount of resources at times; not sure if that has anything to do with whatever caused this problem, though.
upon further research, the panic error seems to be the same as issue #1786. i definitely don't recall my homeserver crashing for the same reason provided there (making a new conversation) but i'll try to provide updates if the situation changes in the future.