-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Background process 'stats.notify_new_event' threw an exception #6405
Comments
I think I found the cause of & fix for this problem.
Not sure if this represents a Synapse bug or is the expected outcome of haphazard tinkering, so I'll leave this issue open for others to judge. |
That probably shouldn't happen. Is there any more to the stack trace? In fact, can you share enough of the log that it shows the request arriving and completing? |
Here are a few:
|
Hi, InfosOS: centos7 I get following error repeating a couple of times per minute:
Haven't found any solution yet. |
Here's the error on python 3.8 with synapse 1.8.0:
|
I'm getting the same Error messages but with the current synapse Version 1.16.1. With 1.15.2 everything is running fine. I'm using our docker-matrix container. :-) If its helpfull, I can send u the error messages. But because if the private MatrixID's I prefer not to publish it here. |
sorry, we seem to have dropped this. However, We've actually just improved the exception reporting here: please could those of you reporting problems please:
@schnuffle please note that we need the original stack trace from homeserver.log; yours appears to have been badly formatted by syslog or similar. I'm going to close this one for now; @mrjohnson22 if you're still seeing the problem please open a new issue with stacktraces from 1.17.0rc1, as above. |
Description
Starting a few hours ago, my HS has repeatedly been throwing exceptions that look like this:
These errors get thrown several times per minute, but the visible operation of the homeserver seems to be fine.
Steps to reproduce
Not sure what the root cause is, but I did restore a
pg_dump
ed synapse database right before this problem started happening. Maybe doing that caused a problem.Version information
The text was updated successfully, but these errors were encountered: