-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Synapse initial sync becomes impossible for clients after possible silent database corruption #12878
Comments
Thanks for digging out the stack trace. As noted by richvdh, it looks like you may have Could you:
|
I'm having an issue with the server stuck on the deletion part currently it's stuck on:
It never seems to complete and just eventually times out |
I wonder if the deletion is stuck for the same reason /sync is stuck. Do you see any |
Yes I am |
I think you need to stop the server, then And, for goodness sake, turn off |
I'm going to close this, as I think the above instructions will fix it, and it's really somewhat self-inflicted |
Description
After upgrading synapse to either 1.57.1 or 1.58.1 (I'm not sure which version caused this) clients can no longer perform an initial sync with the home server. All of these clients have the same issue:
All will not allow users to perform an initial sync with affected home server. The symptom of this is that the homeserver never sends a response to the client causing a timeout with the client causing a retry loop with no errors shown in the client console or in the logs (looks to them as if the server became unresponsive). There are no errors being shown in the logs on the
WARN
log level on theINFO
log level I have found multiple of these events that show up at server startup:Steps to reproduce
Note: I'm unsure what settings or events causes this and as such I'll explain the symptoms of the issue that should be able to be pointed out to users/server admins
/sync
endpoints connection is still trying to be establishedVersion information
Version:
Install method:
Platform:
The text was updated successfully, but these errors were encountered: