So I have syncthing running on two separate Ubuntu servers and three Mac workstations all running as system services.
No problems on the workstations and one of the servers. The services seem to remain running without fail.
On one of the servers, however, the service fails daily. I can manually restart it (systemctl restart syncthing@user.service) and it works for a time, but then it fails and I can’t pinpoint when it fails.
Is there a standard routine that I can follow to hunt down the reason for its failure?
Here’s what I get when I run systemctl status (actual user is replaced with )
syncthing@<user>.service - Syncthing - Open Source Continuous File
Synchronization for <user>
Loaded: loaded (/lib/systemd/system/syncthing@.service; enabled; vendor preset: enabled)
Active: failed (Result: start-limit-hit) since Sat 2019-03-30 11:20:31 MST; 7h ago
Docs: man:syncthing(1)
Process: 1980 ExecStart=/usr/bin/syncthing -no-browser -no-restart -logflags=0 (code=exited, status=1/FAILURE)
Main PID: 1980 (code=exited, status=1/FAILURE)
Mar 30 11:20:30 server1 systemd[1]: syncthing@<user>.service: Unit entered failed state.
Mar 30 11:20:30 server1 systemd[1]: syncthing@<user>.service: Failed with result 'exit-code'.
Mar 30 11:20:31 server1 systemd[1]: syncthing@<user>.service: Service hold-off time over, scheduling restart.
Mar 30 11:20:31 server1 systemd[1]: Stopped Syncthing - Open Source Continuous File Synchronization for <user>.
Mar 30 11:20:31 server1 systemd[1]: syncthing@<user>.service: Start request repeated too quickly.
Mar 30 11:20:31 server1 systemd[1]: Failed to start Syncthing - Open Source Continuous File Synchronization for <usr>.
Mar 30 11:20:31 server1 systemd[1]: syncthing@<user>.service: Unit entered failed state.
Mar 30 11:20:31 server1 systemd[1]: syncthing@<user>.service: Failed with result 'start-limit-hit'.