This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
When a worker cannot connect to another the log messages are unhelpful #16303
Labels
A-Logging
Synapse's logs (structured or otherwise). Not metrics.
A-Workers
Problems related to running Synapse in Worker Mode (or replication)
T-Enhancement
New features, changes in functionality, improvements in performance, or user-facing enhancements.
Description
Media worker tried to connect a wrong IP for federation sender.
The log contained various crazy stuff:
Even enabled DEBUG didn't reveal anything obvious. Lot of stracing and tcpdumps revealed that media worker wanted to connect a wrong IP, which in turn made me find the only hint the log contained, which is
Fixing the ip resolved the problem, but the log have not helped at all. Neither told the real problem nor was it revealing that it has logged fake errors if they were given from the remote server and not our own worker [replication] connection.
Steps to reproduce
Homeserver
grin.hu
Synapse Version
1.90.0-1
Installation Method
Other (please mention below)
Database
psql
Workers
Multiple workers
Platform
Debian/bookworm. Installed from debian pkg, not that it matters.
Configuration
N/A
Relevant log output
Anything else that would be useful to know?
I don't think so.
The text was updated successfully, but these errors were encountered: