Closed rltas closed 10 months ago
I think these are just say the HTTP clients (i.e. the homeservers sending HTTP requests to Sygnal) are idle and have therefore timed out. Don't think its a problem as long as you're seeing traffic successfully go through Sygnal.
I see a lot of these messages in the log and I'm pretty clueless about their meaning:
2023-12-11 11:06:54,322 [1] INFO twisted Timing out client: IPv6Address(type='TCP', host='::ffff:172.29.0.9', port=52914, flowInfo=0, scopeID=0) 2023-12-11 11:06:54,324 [1] INFO twisted Timing out client: IPv6Address(type='TCP', host='::ffff:172.29.0.9', port=52912, flowInfo=0, scopeID=0) 2023-12-11 11:06:54,368 [1] INFO twisted Timing out client: IPv6Address(type='TCP', host='::ffff:172.29.0.9', port=52918, flowInfo=0, scopeID=0)
sygnal v0.12.0 is running in a docker container as part of the Matrix Ansible Playbook behind a Traefik reverse proxy which is that 172.29.0.9 address appearing in an IPv6 notation I didn't know until today. What am I looking at here, who's the client in this context?