-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Synapse becomes unresponsive spamming "exceptions.ValueError: list.remove(x): x not in list" errors #3981
Comments
@Ralith: sorry, I'm not able to reproduce this, or figure out why it might be happening. Are there any ERRORs or CRITICALs in the log before this? |
We run into the same issue:
This is occuring a lot:
Version information
|
ok, please can you send me more detailed logs. |
I tried to get all the individual CRITICALs and ERRORs leading towards the |
@gusttt : hrm, a bunch of things there, some of which are known, and some of which I have opened issues for:
However, I think the above are all relatively harmless, and do not appear to be directly related to this bug. So far I have established that this exception is caused if a cooperative task (a) stops itself and (b) raises an exception during its first iteration. I think this might happen if an outbound federation connection drops before we have written the body of a request (so might be somewhat related to #4003) - I need to investigate more. However, that wouldn't really explain why there are thousands of this error. I think what might help would be complete logs. You can reach me at |
Thank you for the feedback. I provided the log file in private. |
We don't have the
Perhaps it is the combination of #1760 and something else that leads to this error and unresponsiveness. |
After staring at this for really far too long, I have finally managed to reproduce this, and my conclusions are that the exception being logged is a relatively harmless side-effect of synapse being overloaded and getting behind. I've raised https://twistedmatrix.com/trac/ticket/9547 to track the noisy exceptions from the twisted side. Anyway, this really amounts to "Synapse becomes unresponsive", which in all honesty could be due to any number of reasons. I don't think having a single bug to track every reason Synapse could get overloaded is useful, so I'm going to close this. For anyone finding this issue, and @Ralith, please:
|
Description
0.33.5 becomes unresponsive after a few minutes, utterly flooding the logs with this error:
0.33.3.1 seems to work fine.
Version information
The text was updated successfully, but these errors were encountered: