Everything looks correct but no sync?

Support
1

I have two Raspberry Pi 4s running syncthing across the country from each other on reasonable speed connections.

IMG_0766

As you can see from this image one is called SkidsFin and one is called SkidsRoad.

Here is the log from SkidsFin:

2023-07-02 16:49:03 My ID: CZYA4N3-CKJZJ52-ELJWGUC-ENJDRHL-SZ4WHA4-WK2OK5E-CDBORWP-DMNHHQ5 2023-07-02 16:49:04 Single thread SHA256 performance is 44 MB/s using minio/sha256-simd (44 MB/s using crypto/sha256). 2023-07-02 16:49:04 Hashing performance is 40.35 MB/s 2023-07-02 16:49:04 Overall send rate is unlimited, receive rate is unlimited 2023-07-02 16:49:04 Ready to synchronize “Syncthing Data” (default) (sendreceive) 2023-07-02 16:49:04 Using discovery mechanism: global discovery server https://discovery.syncthing.net/v2/?noannounce&id=LYXKCHX-VI3NYZR-ALCJBHF-WMZYSPK-QG6QJA3-MPFYMSO-U56GTUK-NA2MIAW 2023-07-02 16:49:04 Using discovery mechanism: global discovery server https://discovery-v4.syncthing.net/v2/?nolookup&id=LYXKCHX-VI3NYZR-ALCJBHF-WMZYSPK-QG6QJA3-MPFYMSO-U56GTUK-NA2MIAW 2023-07-02 16:49:04 Using discovery mechanism: global discovery server https://discovery-v6.syncthing.net/v2/?nolookup&id=LYXKCHX-VI3NYZR-ALCJBHF-WMZYSPK-QG6QJA3-MPFYMSO-U56GTUK-NA2MIAW 2023-07-02 16:49:04 Relay listener (dynamic+https://relays.syncthing.net/endpoint) starting 2023-07-02 16:49:04 Using discovery mechanism: IPv4 local broadcast discovery on port 21027 2023-07-02 16:49:04 … 2023-07-02 16:49:04 Using discovery mechanism: IPv6 local multicast discovery on address [ff12::8384]:21027 2023-07-02 16:49:04 Ready to synchronize “Media” (zmtud-3swyx) (sendreceive) 2023-07-02 16:49:04 GUI and API listening on 192.168.2.3:8384 2023-07-02 16:49:04 Access the GUI via the following URL: http://192.168.2.3:8384/ 2023-07-02 16:49:04 TCP listener ([::]:22000) starting 2023-07-02 16:49:04 My name is “SkidsFin” 2023-07-02 16:49:04 Device R4SILKF-WUCWODW-JTP5T5K-HVFWMQD-CJW3SZG-VL4DQJY-JVFVJUW-RTH4EAM is “SkidsRoad” at [dynamic] 2023-07-02 16:49:04 Completed initial scan of sendreceive folder “Syncthing Data” (default) 2023-07-02 16:49:04 QUIC listener ([::]:22000) starting 2023-07-02 16:49:07 Completed initial scan of sendreceive folder “Media” (zmtud-3swyx) 2023-07-02 16:49:15 quic://0.0.0.0:22000 detected NAT type: Restricted NAT 2023-07-02 16:49:15 quic://0.0.0.0:22000 resolved external address quic://192.173.169.115:35526 (via stun.syncthing.net:3478) 2023-07-02 16:49:19 New NAT port mapping: external TCP address 192.168.1.3:45686 to local address [::]:22000. 2023-07-02 16:49:19 New NAT port mapping: external TCP address 192.168.1.3:4209 to local address [::]:22000. 2023-07-02 16:49:19 Detected 3 NAT services 2023-07-02 16:49:33 Established secure connection to R4SILKF-WUCWODW-JTP5T5K-HVFWMQD-CJW3SZG-VL4DQJY-JVFVJUW-RTH4EAM at 192.168.2.3:47148-198.98.62.174:22067/relay-client/TLS1.3-TLS_CHACHA20_POLY1305_SHA256/WAN-P50 2023-07-02 16:49:33 Device R4SILKF-WUCWODW-JTP5T5K-HVFWMQD-CJW3SZG-VL4DQJY-JVFVJUW-RTH4EAM client is “syncthing v1.23.5” named “SkidsRoad” at 192.168.2.3:47148-198.98.62.174:22067/relay-client/TLS1.3-TLS_CHACHA20_POLY1305_SHA256/WAN-P50 2023-07-02 16:50:09 Established secure connection to R4SILKF-WUCWODW-JTP5T5K-HVFWMQD-CJW3SZG-VL4DQJY-JVFVJUW-RTH4EAM at 192.168.2.3:22000-98.97.21.95:45087/tcp-server/TLS1.3-TLS_CHACHA20_POLY1305_SHA256/WAN-P30 2023-07-02 16:50:09 Replacing old connection 192.168.2.3:47148-198.98.62.174:22067/relay-client/TLS1.3-TLS_CHACHA20_POLY1305_SHA256/WAN-P50 with 192.168.2.3:22000-98.97.21.95:45087/tcp-server/TLS1.3-TLS_CHACHA20_POLY1305_SHA256/WAN-P30 for R4SILKF-WUCWODW-JTP5T5K-HVFWMQD-CJW3SZG-VL4DQJY-JVFVJUW-RTH4EAM 2023-07-02 16:50:09 Connection to R4SILKF-WUCWODW-JTP5T5K-HVFWMQD-CJW3SZG-VL4DQJY-JVFVJUW-RTH4EAM at 192.168.2.3:47148-198.98.62.174:22067/relay-client/TLS1.3-TLS_CHACHA20_POLY1305_SHA256/WAN-P50 closed: reading length: EOF 2023-07-02 16:50:09 Device R4SILKF-WUCWODW-JTP5T5K-HVFWMQD-CJW3SZG-VL4DQJY-JVFVJUW-RTH4EAM client is “syncthing v1.23.5” named “SkidsRoad” at 192.168.2.3:22000-98.97.21.95:45087/tcp-server/TLS1.3-TLS_CHACHA20_POLY1305_SHA256/WAN-P30 2023-07-02 16:50:16 Joined relay relay://193.160.32.204:22067

I am syncing primarily from SkidsFin to SkidsRoad. It has been stuck @ 95% 53.4 gigs for a week?

(If the log from SkidsFin does not provide solution I can get log I can provide log from SkidsRoad.

I appreciate any assitance.

2

If you could expand the “SkidsRoad” device panel, it would be very helpful since it will display available error(s). Also, if there are any out of sync items, an example of one or more of the items would also be very helpful.

(Tip: When posting logs, it’s best to use the preformatted text option or something else suitable to make it easier to read.)

3

I apologize about the Log Post. I know better. Surprisingly last night it started syncing again. Not sure what changed but I am going to go with it.

Thanks, consider this issue closed.

4

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