Syncthing on CentOS 7 keeps Failing

Hey I followed the steps for setting up syncthing on CentOS 7 from this website. But when I start the service i get the following message:


Sep 14 10:45:10 localhost systemd: Started Syncthing - Open Source Continuous File Synchronization for rndlnxadm.
Sep 14 10:45:10 localhost syncthing: [start] INFO: syncthing v1.18.2 "Fermium Flea" (go1.17 linux-amd64) teamcity@build.syncthing.net 2021-08-22 18:04:47 UTC
Sep 14 10:45:10 localhost syncthing: [23JDG] INFO: My ID: 23JDGFK-RZSEQB7-FZRUWI6-2MEDIT3-EM2W7L6-XCEUWHJ-R43FUW5-ADOCOAW
Sep 14 10:45:11 localhost syncthing: [23JDG] INFO: Single thread SHA256 performance is 123 MB/s using crypto/sha256 (123 MB/s using minio/sha256-simd).
Sep 14 10:45:11 localhost syncthing: [23JDG] INFO: Hashing performance is 108.62 MB/s
Sep 14 10:45:11 localhost syncthing: [23JDG] INFO: Overall send rate is unlimited, receive rate is unlimited
Sep 14 10:45:11 localhost syncthing: [23JDG] INFO: Ready to synchronize "Default Folder" (default) (sendreceive)
Sep 14 10:45:11 localhost syncthing: 2021/09/14 10:45:11 failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See https://github.com/lucas-clemente/quic-go/wiki/UDP-Receive-Buffer-Size for details.
Sep 14 10:45:11 localhost syncthing: [23JDG] INFO: Using discovery mechanism: global discovery server https://discovery.syncthing.net/v2/?noannounce&id=LYXKCHX-VI3NYZR-ALCJBHF-WMZYSPK-QG6QJA3-MPFYMSO-U56GTUK-NA2MIAW
Sep 14 10:45:11 localhost syncthing: [23JDG] INFO: Using discovery mechanism: global discovery server https://discovery-v4.syncthing.net/v2/?nolookup&id=LYXKCHX-VI3NYZR-ALCJBHF-WMZYSPK-QG6QJA3-MPFYMSO-U56GTUK-NA2MIAW
Sep 14 10:45:11 localhost syncthing: [23JDG] INFO: Using discovery mechanism: global discovery server https://discovery-v6.syncthing.net/v2/?nolookup&id=LYXKCHX-VI3NYZR-ALCJBHF-WMZYSPK-QG6QJA3-MPFYMSO-U56GTUK-NA2MIAW
Sep 14 10:45:11 localhost syncthing: [23JDG] INFO: Using discovery mechanism: IPv4 local broadcast discovery on port 21027
Sep 14 10:45:11 localhost syncthing: [23JDG] INFO: Using discovery mechanism: IPv6 local multicast discovery on address [ff12::8384]:21027
Sep 14 10:45:11 localhost syncthing: [23JDG] INFO: QUIC listener ([::]:22000) starting
Sep 14 10:45:11 localhost syncthing: [23JDG] INFO: TCP listener ([::]:22000) starting
Sep 14 10:45:11 localhost syncthing: [23JDG] INFO: Relay listener (dynamic+https://relays.syncthing.net/endpoint) starting
Sep 14 10:45:11 localhost syncthing: [23JDG] INFO: Completed initial scan of sendreceive folder "Default Folder" (default)
Sep 14 10:45:11 localhost syncthing: [23JDG] WARNING: Failed starting API: listen tcp: address tcp/8384": unknown port
Sep 14 10:45:11 localhost syncthing: [23JDG] INFO: Relay listener (dynamic+https://relays.syncthing.net/endpoint) shutting down
Sep 14 10:45:11 localhost syncthing: [23JDG] INFO: QUIC listener ([::]:22000) shutting down
Sep 14 10:45:11 localhost syncthing: [23JDG] INFO: Detected 0 NAT services
Sep 14 10:45:11 localhost syncthing: [23JDG] WARNING: Starting API/GUI: listen tcp: address tcp/8384": unknown port
cSep 14 10:45:12 localhost syncthing: [23JDG] INFO: TCP listener ([::]:22000) shutting down
Sep 14 10:45:12 localhost syncthing: [23JDG] INFO: Exiting
Sep 14 10:45:12 localhost systemd: syncthing@rndlnxadm.service: main process exited, code=exited, status=1/FAILURE
Sep 14 10:45:12 localhost systemd: Unit syncthing@rndlnxadm.service entered failed state.
Sep 14 10:45:12 localhost systemd: syncthing@rndlnxadm.service failed.
Sep 14 10:45:13 localhost systemd: syncthing@rndlnxadm.service holdoff time over, scheduling restart.
Sep 14 10:45:13 localhost systemd: Stopped Syncthing - Open Source Continuous File Synchronization for rndlnxadm.

And it keeps restarting over and over again. I tried the guide on CentOS 8 but there’s no issue so far. Is there something I should change or reconfigure? Thanks

Got it fixed via the documentation. There was something wrong with the systemd file after all.

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