Cosmetic problem? - "pull: connection closed"

Hi,

I’m currently experiencing a cosmetic issue on v1.1.1 windows amd64 Syncthing. Here are pictures and logs:

2019-04-17 12:17:22 syncthing v1.1.1 "Erbium Earthworm" (go1.12.1 windows-amd64) teamcity@build.syncthing.net 2019-03-25 11:43:21 UTC
2019-04-17 12:17:22 My ID: LRORKSI-2CWSI6G-PA74TDZ-XXX-M5DHCD4-5OUYHIE-SLSVV2R-QF56CQN
2019-04-17 12:17:23 Single thread SHA256 performance is 314 MB/s using minio/sha256-simd (273 MB/s using crypto/sha256).
2019-04-17 12:17:23 Hashing performance is 260.74 MB/s
2019-04-17 12:17:23 Ready to synchronize "Dokumentation" (cdaf2-v5ayb) (receiveonly)
2019-04-17 12:17:23 Ready to synchronize "Installationsquellen" (n4q4z-ohpfz) (receiveonly)
2019-04-17 12:17:23 Ready to synchronize "Persoenlich" (xnxjv-w6vvp) (receiveonly)
2019-04-17 12:17:23 Overall send rate is unlimited, receive rate is unlimited
2019-04-17 12:17:23 TCP listener (0.0.0.0:20081) starting
2019-04-17 12:17:23 GUI and API listening on [::]:20080
2019-04-17 12:17:23 ...
2019-04-17 12:17:23 Access the GUI via the following URL: http://127.0.0.1:20080/
2019-04-17 12:17:23 My name is "THRE-NB"
2019-04-17 12:17:23 Device VBHJ3YR-WXRWUR4-GVZBFIL-4I2GE5T-TYHNPZY-NY3PKDS-XXXXX-MZNP4AD is "THRE" at [tcp4://thre-w10.polygon.local:20081]
2019-04-17 12:17:23 Syncthing should not run as a privileged or system user. Please consider using a normal user account.
2019-04-17 12:17:23 Completed initial scan of receiveonly folder "Persoenlich" (xnxjv-w6vvp)
2019-04-17 12:17:23 Puller (folder "Persoenlich" (xnxjv-w6vvp), file "Dokumentation\\2019-02-13_Dokumentation.rar"): no connected device has the required version of this file
2019-04-17 12:17:23 Established secure connection to VBHJ3YR-XXXX-GVZBFIL-4I2GE5T-TYHNPZY-NY3PKDS-Y2AFDBO-MZNP4AD at 10.20.20.90:56039-10.20.30.95:20081/tcp-client/TLS1.2-TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
2019-04-17 12:17:23 Device VBHJ3YR-WXRWUR4-GVZBFIL-4I2GE5T-XXXXX-NY3PKDS-Y2AFDBO-MZNP4AD client is "syncthing v1.1.1" named "THRE" at 10.20.20.90:56039-10.20.30.95:20081/tcp-client/TLS1.2-TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
2019-04-17 12:17:24 Completed initial scan of receiveonly folder "Dokumentation" (cdaf2-v5ayb)
2019-04-17 12:17:25 Completed initial scan of receiveonly folder "Installationsquellen" (n4q4z-ohpfz)
2019-04-17 12:17:46 Connection to VBHJ3YR-WXRWUR4-GVZBFIL-4I2GE5T-TYHNPZY-NY3PKDS-Y2AFDBO-MZNP4AD at 10.20.20.90:56039-10.20.30.95:20081/tcp-client/TLS1.2-TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 closed: reading message: local error: tls: bad record MAC
2019-04-17 12:17:48 Established secure connection to VBHJ3YR-WXRWUR4-GVZBFIL-4I2GE5T-TYHNPZY-NY3PKDS-Y2AFDBO-MZNP4AD at 10.20.50.90:20081-10.20.30.95:54923/tcp-server/TLS1.2-TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
2019-04-17 12:17:48 Device VBHJ3YR-WXRWUR4-GVZBFIL-4I2GE5T-XXXXX-NY3PKDS-Y2AFDBO-MZNP4AD client is "syncthing v1.1.1" named "THRE" at 10.20.50.90:20081-10.20.30.95:54923/tcp-server/TLS1.2-TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
2019-04-17 12:17:57 Puller (folder "Persoenlich" (xnxjv-w6vvp), file "Dokumentation\\2019-02-13_Dokumentation.rar"): pull: connection closed

The connection was closed because THRE-NB sporadically disconnected and reconnect WiFi.

The problem is that the file is syncing but is still listed as a failed object from a previous run, right?

That’s probably because we retry pulling up to three times and only reset all errors at the end. The correct thing would be to reset individual errors whenever we start actually processing the item.

Yes, your description fits perfectly what I’ve experienced. The file synced okay after waiting some minutes since the reconnect.

That should be pretty simple to fix, I’ll probably get around to doing that sometime soon - an enhancement issue on github would help me remember :wink:

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