-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
RoomInitialSyncRestServlet internal server error with "AssertionError synapse.util.linked_list in move_after" #11436
Comments
Seems to come from synapse/synapse/util/linked_list.py Lines 92 to 98 in 524b8ea
|
Are we able to get a stack trace? |
We have now, it's happening again, for the same customer, for the same kind of initial synchrotron EMS worker setup. Please ping if customer or other details needed, restarting the worker now.
|
We see these assertions fail in Sentry, but all the examples there are in the server-server API. Curiously this seems to only occur on federation_reader-4. Probably a distinct issue? https://sentry.matrix.org/sentry/synapse-matrixorg/?query=is%3Aunresolved+linked_list |
Seen in 1.38.1 too. |
The error points to an For context, this code seems to have been introduced by #10205 (1.38.0). |
@jaywink Has the |
Yes we enabled it for all hosts. I'll disable it for this customer as a quick patch, thanks! |
There's a bug in synapse/synapse/util/caches/lrucache.py Lines 273 to 276 in a4521ce
The cache in question is a state group cache: synapse/synapse/storage/databases/state/store.py Lines 97 to 101 in a4521ce
and it has a synapse/synapse/util/caches/dictionary_cache.py Lines 69 to 71 in a4521ce
All the errors in sentry are for the |
Description
A host started throwing
AssertionError synapse.util.linked_list in move_after
inGET' uri='/_matrix/client/r0/rooms/!abcdefgh%3Adomain.tld/initialSync?limit=20&access_token=<redacted>
.The particular client calling that URL had been fine for a long time. It seems the error started happening at or some time after a restart of Synapse and the two workers (synchrotron + initial synchrotron).
After restarting everything again, the error disappeared.
Version information
The text was updated successfully, but these errors were encountered: