Log grows until available diskspace is consumed (127GB total in my case)

Once in a while, and only on one server (2012R2) Syncthing loses connection and starts logging continuously until all available diskspace is consumed and Syncthing goes into stopped-mode. The log when it starts is like this: [VISHJ] 18:47:05 INFO: Connection to JDB3PLR-HNWZ7H4-2ZDRVYR-HUKZ32W-LMXMAZG-3BBBOXH-GFIIS5K-DM3XDQL at 192.168.0.55:62260-212.47.253.154:22067/relay-server/TLS1.3-TLS_CHACHA20_POLY1305_SHA256 closed: replacing connection [VISHJ] 18:47:05 INFO: Device JDB3PLR-HNWZ7H4-2ZDRVYR-HUKZ32W-LMXMAZG-3BBBOXH-GFIIS5K-DM3XDQL client is “syncthing v1.3.1” named “Management” at 192.168.0.55:62638-80.56.17.214:22000/tcp-client/TLS1.3-TLS_CHACHA20_POLY1305_SHA256 [VISHJ] 02:39:53 INFO: Connection to JDB3PLR-HNWZ7H4-2ZDRVYR-HUKZ32W-LMXMAZG-3BBBOXH-GFIIS5K-DM3XDQL at 192.168.0.55:62638-80.56.17.214:22000/tcp-client/TLS1.3-TLS_CHACHA20_POLY1305_SHA256 closed: reading length: read tcp 192.168.0.55:62638->80.56.17.214:22000: wsarecv: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. [VISHJ] 04:18:46 WARNING: Listen (BEP/quic): Accepting connection: read udp [::]:22000: wsarecvfrom: The connection has been broken due to keep-alive activity detecting a failure while the operation was in progress. [VISHJ] 04:18:46 WARNING: Listen (BEP/quic): Accepting connection: read udp [::]:22000: wsarecvfrom: The connection has been broken due to keep-alive activity detecting a failure while the operation was in progress. [VISHJ] 04:18:46 WARNING: Listen (BEP/quic): Accepting connection: read udp [::]:22000: wsarecvfrom: The connection has been broken due to keep-alive activity detecting a failure while the operation was in progress. [VISHJ] 04:18:46 WARNING: Listen (BEP/quic): Accepting connection: read udp [::]:22000: wsarecvfrom: The connection has been broken due to keep-alive activity detecting a failure while the operation was in progress. [VISHJ] 04:18:46 WARNING: Listen (BEP/quic): Accepting connection: read udp [::]:22000: wsarecvfrom: The connection has been broken due to keep-alive activity detecting a failure while the operation was in progress.

Then, it keeps repeating the last message over and over fillling up the entire disk. This is Windows 2012R2 Syncthing v1.3.1. I can’t find a setting to at least disable logging. Simply shutting down Syncthing and starting it solves it because it starts a new logfile. Annoying thing is however ofcourse that Syncthing stops without you knowing, so that node is then stopped/offline for as long as the disk holds out…

Again, something that is fixed in the next release.

Is there somewhere where I can check the changelog for the upcoming release, so I can check before posting problems here that will be fixed soon… ? Thanx for the very quick response

Github has the issues and the PRs closing it, and tags for the versions.

@Wizard17 You may want to redact the device IDs from the log you posted.

Leaking the ID does not compromise security in any way, so it’s not really mandatory.