Syncthing fails to start using systemd, OK 'by hand'

Support
1

I am running syncthing on a number of Linux systems, running xubuntu 19.10, xubuntu 18.04, Raspbian, Debian (on an armhf) and Ubuntu 16.04 on a virtual machine.

I have moved all of the above from running syncthing ‘manually’ via /etc/rc.local to using systemd services. They all work OK except the Ubuntu 16.04 virtual machine where syncthing fails to start as a systemd service even though it worked fine when run from /etc/rc.local.

In syslog I see the following syncthing related messages:-

Jan 21 17:35:12 isbdGandi systemd[927]: syncthing@chris.service: Failed at step SECCOMP spawning /usr/bin/syncthing: Invalid argument
Jan 21 17:35:12 isbdGandi systemd[1]: syncthing@chris.service: Main process exited, code=exited, status=228/SECCOMP
Jan 21 17:35:12 isbdGandi systemd[1]: syncthing@chris.service: Unit entered failed state.
Jan 21 17:35:12 isbdGandi systemd[1]: syncthing@chris.service: Failed with result 'exit-code'.
Jan 21 17:35:12 isbdGandi systemd[1]: syncthing@chris.service: Service hold-off time over, scheduling restart.
Jan 21 17:35:12 isbdGandi systemd[1037]: syncthing@chris.service: Failed at step SECCOMP spawning /usr/bin/syncthing: Invalid argument
Jan 21 17:35:12 isbdGandi systemd[1]: syncthing@chris.service: Main process exited, code=exited, status=228/SECCOMP
Jan 21 17:35:12 isbdGandi systemd[1]: syncthing@chris.service: Unit entered failed state.
Jan 21 17:35:12 isbdGandi systemd[1]: syncthing@chris.service: Failed with result 'exit-code'.
Jan 21 17:35:12 isbdGandi systemd[1]: syncthing@chris.service: Service hold-off time over, scheduling restart.
Jan 21 17:35:12 isbdGandi systemd[1100]: syncthing@chris.service: Failed at step SECCOMP spawning /usr/bin/syncthing: Invalid argument
Jan 21 17:35:12 isbdGandi systemd[1]: syncthing@chris.service: Main process exited, code=exited, status=228/SECCOMP
Jan 21 17:35:12 isbdGandi systemd[1]: syncthing@chris.service: Unit entered failed state.
Jan 21 17:35:12 isbdGandi systemd[1]: syncthing@chris.service: Failed with result 'exit-code'.
Jan 21 17:35:13 isbdGandi systemd[1]: syncthing@chris.service: Service hold-off time over, scheduling restart.
Jan 21 17:35:13 isbdGandi systemd[1133]: syncthing@chris.service: Failed at step SECCOMP spawning /usr/bin/syncthing: Invalid argument
Jan 21 17:35:13 isbdGandi systemd[1]: syncthing@chris.service: Main process exited, code=exited, status=228/SECCOMP
Jan 21 17:35:13 isbdGandi systemd[1]: syncthing@chris.service: Unit entered failed state.
Jan 21 17:35:13 isbdGandi systemd[1]: syncthing@chris.service: Failed with result 'exit-code'.
Jan 21 17:35:13 isbdGandi systemd[1]: syncthing@chris.service: Service hold-off time over, scheduling restart.
Jan 21 17:35:13 isbdGandi systemd[1214]: syncthing@chris.service: Failed at step SECCOMP spawning /usr/bin/syncthing: Invalid argument
Jan 21 17:35:13 isbdGandi systemd[1]: syncthing@chris.service: Main process exited, code=exited, status=228/SECCOMP
Jan 21 17:35:13 isbdGandi systemd[1]: syncthing@chris.service: Unit entered failed state.
Jan 21 17:35:13 isbdGandi systemd[1]: syncthing@chris.service: Failed with result 'exit-code'.
Jan 21 17:35:13 isbdGandi systemd[1]: syncthing@chris.service: Service hold-off time over, scheduling restart.
Jan 21 17:35:13 isbdGandi systemd[1]: syncthing@chris.service: Start request repeated too quickly.
Jan 21 17:35:13 isbdGandi systemd[1]: syncthing@chris.service: Unit entered failed state.
Jan 21 17:35:13 isbdGandi systemd[1]: syncthing@chris.service: Failed with result 'start-limit-hit'.

Is this probably because Ubuntu 16.04 is so old (I’m limited by the what’s available on the virtual machine) or is something else wrong that I can fix?

2

Sorry, but this is really a systemd question and not a syncthing question.

3

This might be that the old systemd version in Ubuntu 16.04 doesn’t know the hardening options in the unit file.

1 Like
4

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