Log file is filling up on Windows

Support
1

Recently I had 2 systems that have been syncing for 11 months have their log files fill up.

The log file grew to over 100GB in one day, deleting the file and recreating it fills it up again.

The log files fill up with the following content:

[7BHVH] 07:53:47 INFO: quic://0.0.0.0:22000 resolved external address quic://72.29.247.114:54294 (via stun.syncthing.net:3478)
[7BHVH] 07:58:57 INFO: quic://0.0.0.0:22000 detected NAT type: Symmetric NAT
[7BHVH] 07:58:57 INFO: quic://0.0.0.0:22000 resolved external address quic://72.29.247.114:62100 (via stun.syncthing.net:3478)
[7BHVH] 08:04:07 INFO: quic://0.0.0.0:22000 detected NAT type: Symmetric NAT
[7BHVH] 08:04:07 INFO: quic://0.0.0.0:22000 resolved external address quic://72.29.247.114:41556 (via stun.syncthing.net:3478)
[7BHVH] 08:09:17 INFO: quic://0.0.0.0:22000 detected NAT type: Symmetric NAT
[7BHVH] 08:09:17 INFO: quic://0.0.0.0:22000 resolved external address quic://72.29.247.114:45147 (via stun.syncthing.net:3478)
[7BHVH] 08:14:27 INFO: quic://0.0.0.0:22000 detected NAT type: Symmetric NAT
[7BHVH] 08:14:27 INFO: quic://0.0.0.0:22000 resolved external address quic://72.29.247.114:5484 (via stun.syncthing.net:3478)
[7BHVH] 08:19:37 INFO: quic://0.0.0.0:22000 detected NAT type: Symmetric NAT
[7BHVH] 08:19:37 INFO: quic://0.0.0.0:22000 resolved external address quic://72.29.247.114:30958 (via stun.syncthing.net:3478)
[7BHVH] 08:24:47 INFO: quic://0.0.0.0:22000 detected NAT type: Symmetric NAT
[7BHVH] 08:24:47 INFO: quic://0.0.0.0:22000 resolved external address quic://72.29.247.114:4908 (via stun.syncthing.net:3478)
[7BHVH] 08:29:57 INFO: quic://0.0.0.0:22000 detected NAT type: Symmetric NAT
[7BHVH] 08:29:57 INFO: quic://0.0.0.0:22000 resolved external address quic://72.29.247.114:41937 (via stun.syncthing.net:3478)
[7BHVH] 08:35:08 INFO: quic://0.0.0.0:22000 detected NAT type: Symmetric NAT
[7BHVH] 08:35:08 INFO: quic://0.0.0.0:22000 resolved external address quic://72.29.247.114:7941 (via stun.syncthing.net:3478)
[7BHVH] 08:40:18 INFO: quic://0.0.0.0:22000 detected NAT type: Symmetric NAT
[7BHVH] 08:40:18 INFO: quic://0.0.0.0:22000 resolved external address quic://72.29.247.114:59238 (via stun.syncthing.net:3478)
[7BHVH] 08:45:28 INFO: quic://0.0.0.0:22000 detected NAT type: Symmetric NAT
[7BHVH] 08:45:28 INFO: quic://0.0.0.0:22000 resolved external address quic://72.29.247.114:51018 (via stun.syncthing.net:3478)
[7BHVH] 08:50:38 INFO: quic://0.0.0.0:22000 detected NAT type: Symmetric NAT
[7BHVH] 08:50:38 INFO: quic://0.0.0.0:22000 resolved external address quic://72.29.247.114:47171 (via stun.syncthing.net:3478)
[7BHVH] 08:55:48 INFO: quic://0.0.0.0:22000 detected NAT type: Symmetric NAT
[7BHVH] 08:55:48 INFO: quic://0.0.0.0:22000 resolved external address quic://72.29.247.114:6907 (via stun.syncthing.net:3478)
[7BHVH] 09:00:58 INFO: quic://0.0.0.0:22000 detected NAT type: Symmetric NAT
[7BHVH] 09:00:58 INFO: quic://0.0.0.0:22000 resolved external address quic://72.29.247.114:50195 (via stun.syncthing.net:3478)
[7BHVH] 09:06:07 INFO: quic://0.0.0.0:22000 detected NAT type: Symmetric NAT
[7BHVH] 09:06:07 INFO: quic://0.0.0.0:22000 resolved external address quic://72.29.247.114:55743 (via stun.syncthing.net:3478)
[7BHVH] 09:11:17 INFO: quic://0.0.0.0:22000 detected NAT type: Symmetric NAT
[7BHVH] 09:11:17 INFO: quic://0.0.0.0:22000 resolved external address quic://72.29.247.114:33316 (via stun.syncthing.net:3478)
[7BHVH] 09:16:27 INFO: quic://0.0.0.0:22000 detected NAT type: Symmetric NAT
[7BHVH] 09:16:27 INFO: quic://0.0.0.0:22000 resolved external address quic://72.29.247.114:2035 (via stun.syncthing.net:3478)
[7BHVH] 09:21:37 INFO: quic://0.0.0.0:22000 detected NAT type: Symmetric NAT
[7BHVH] 09:21:37 INFO: quic://0.0.0.0:22000 resolved external address quic://72.29.247.114:12595 (via stun.syncthing.net:3478)

Is there a way to set the log file to append every let’s say 6 hours or so.

2

Can you open an issue on github?

3

Actually, this doesn’t add up. It’s ~206 bytes every 5mins, which is 60kb a day.

Something else is up… Does the logging start happening more often or something?

1 Like
4

I thought I had fixed the issue by updating and rebooting but recently the problem came back. I will open the issue in github.

69 GB file this morning.

5

I’m not sure, if I delete the file it stays normal for a couple days. Then it grows again. I’ve had this happen on two systems now.

6
7

Searching for an equivalent of tail in powershell gave me Get-Content *logfile* -Tail 100. Could you do that on your huge log file to see what there is at the end?

1 Like
8

I’ll try that next time the file fills up.

Thanks.

9

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