-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Federation dying with AttributeError: 'dict' object has no attribute 'edu_type'
or ... no attribute 'content'
#11889
Comments
I don't think so: unless you had debug logging configured everywhere? I think the problem is that I copied and pasted logging from the sender side to the receiver side. But the receiver side just has a |
It seems that none of our unit tests in |
Fixes #11889. Homeservers should only be affected if the `synapse.8631_debug` logger was enabled for DEBUG mode. I am not sure if this merits a bugfix release: I think the logging can be disabled in config if anyone is affected? But it is still pretty bad.
Ah right, I had
So that also trickles down to all loggers lower in the hierarchy. All good then. |
* Fix losing incoming EDUs if debug logging enabled Fixes #11889. Homeservers should only be affected if the `synapse.8631_debug` logger was enabled for DEBUG mode. I am not sure if this merits a bugfix release: I think the logging can be disabled in config if anyone is affected? But it is still pretty bad.
Reopening this: Fix was incorrect and the problem still occurs, just with a different error message. |
AttributeError: 'dict' object has no attribute 'edu_type'
AttributeError: 'dict' object has no attribute 'edu_type'
or ... no attribute 'content'
Description
After upgrading my homeserver to 1.51.0 yesterday, I noticed people on other homeservers weren't responding to my messages. On the receiving side some messages were getting through to me, but not all of them.
Digging into the logs, I noticed my Synapse wasn't able to process some transactions, failing with errors like:
The offending line seems to have been introduced in #11760. I'm not sure why that logger was automatically enabled for me (should it have been?), but as a workaround I reduced
DEBUG
toWARN
and things started working again.Version information
The text was updated successfully, but these errors were encountered: