Growing Logs are back...

Support
1

Anyone else seeing this in their logs again? Doing a search there was an issue that was fixed back at the end of 2019…

The “Connection has been broken” entry appears continuously. Occasionally the QUIC listener shuts down and restarts and the messages continue. I don’t know enough about UDP or QUIC to have any idea what’s happening here.

Anyone?

2023-07-25 11:52:56 Listen (BEP/quic): Accepting connection: read udp [::]:22000: wsarecvmsg: The connection has been broken due to keep-alive activity detecting a failure while the operation was in progress.
2023-07-25 11:53:06 Listen (BEP/quic): Accepting connection: read udp [::]:22000: wsarecvmsg: The connection has been broken due to keep-alive activity detecting a failure while the operation was in progress.
2023-07-25 11:53:06 QUIC listener ([::]:22000) shutting down
2023-07-25 11:53:06 Listen address quic://0.0.0.0:22000 resolution has changed: lan addresses: [] wan addresses: []
2023-07-25 11:53:06 listenerSupervisor@quic://0.0.0.0:22000: service quic://0.0.0.0:22000 failed: read udp [::]:22000: wsarecvmsg: The connection has been broken due to keep-alive activity detecting a failure while the operation was in progress.
2023-07-25 11:53:06 QUIC listener ([::]:22000) starting
2023-07-25 11:53:06 Listen address quic://0.0.0.0:22000 resolution has changed: lan addresses: [quic://0.0.0.0:22000 quic://10.52.245.160:22000 quic://192.168.153.130:22000] wan addresses: [quic://0.0.0.0:22000]
2023-07-25 11:53:11 Listen (BEP/quic): Accepting connection: read udp [::]:22000: wsarecvmsg: The connection has been broken due to keep-alive activity detecting a failure while the operation was in progress.
2023-07-25 11:53:12 Listen (BEP/quic): Accepting connection: read udp [::]:22000: wsarecvmsg: The connection has been broken due to keep-alive activity detecting a failure while the operation was in progress.
2023-07-25 11:53:14 Listen (BEP/quic): Accepting connection: read udp [::]:22000: wsarecvmsg: The connection has been broken due to keep-alive activity detecting a failure while the operation was in progress.
2023-07-25 11:53:17 Listen (BEP/quic): Accepting connection: read udp [::]:22000: wsarecvmsg: The connection has been broken due to keep-alive activity detecting a failure while the operation was in progress.
2

What syncthing version(s) are involved on the devices?

3

All are running 1.23.6 stable release.

4

I just checked the logs again and the messages stopped about one hour later. No explanation. No apparent changes in the network. No idea why it stopped… Perhaps this was a fluke? I’m not sure what to make of it…

I definitely don’t understand what the message means.

2023-07-25 12:39:43 Listen (BEP/quic): Accepting connection: read udp [::]:22000: wsarecvmsg: The connection has been broken due to keep-alive activity detecting a failure while the operation was in progress.
2023-07-25 12:39:51 Listen (BEP/quic): Accepting connection: read udp [::]:22000: wsarecvmsg: The connection has been broken due to keep-alive activity detecting a failure while the operation was in progress.
2023-07-25 12:40:00 Listen (BEP/quic): Accepting connection: read udp [::]:22000: wsarecvmsg: The connection has been broken due to keep-alive activity detecting a failure while the operation was in progress.
2023-07-25 12:40:10 Listen (BEP/quic): Accepting connection: read udp [::]:22000: wsarecvmsg: The connection has been broken due to keep-alive activity detecting a failure while the operation was in progress.
2023-07-25 12:40:10 QUIC listener ([::]:22000) shutting down
2023-07-25 12:40:10 listenerSupervisor@quic://0.0.0.0:22000: service quic://0.0.0.0:22000 failed: read udp [::]:22000: wsarecvmsg: The connection has been broken due to keep-alive activity detecting a failure while the operation was in progress.
2023-07-25 12:40:10 Listen address quic://0.0.0.0:22000 resolution has changed: lan addresses: [] wan addresses: []
2023-07-25 12:40:10 QUIC listener ([::]:22000) starting
2023-07-25 12:40:10 Listen address quic://0.0.0.0:22000 resolution has changed: lan addresses: [quic://0.0.0.0:22000 quic://10.52.245.160:22000 quic://192.168.153.130:22000] wan addresses: [quic://0.0.0.0:22000]
2023-07-25 12:40:20 quic://0.0.0.0:22000 detected NAT type: Symmetric NAT
5

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.