installing Syncthing on Netgear ReadyNAS 104

Chris.Karst · April 27, 2021, 2:47am

Trying to instal on ReadyNAS 104 as advised: (sorry about the quote from other thread)

BananasInPyjamas

In short follow the instructions on the link @Nummer378 posted (https://apt.syncthing.net/ ) and then this to get it up and running automatically https://docs.syncthing.net/users/autostart.html#using-systemd . If you encounter problems, both describe the steps you have taken and what happened (and how that’s different from what you want to achieve if not obvious (if in doubt assume everything is not obvious)).

App does not show as installed, and checking status of service gives errors:

login as: root root@192.168.1.30’s password:

Welcome to ReadyNASOS 6.10.4

root@Netgear-NAS:~# sudo curl -s -o /usr/share/keyrings/syncthing-archive-keyring.gpg https://syncthing.net/release-key.gpg -bash: sudo: command not found root@Netgear-NAS:~# curl -s -o /usr/share/keyrings/syncthing-archive-keyring.gpg https://syncthing.net/release-key.gpg root@Netgear-NAS:~# echo “deb [signed-by=/usr/share/keyrings/syncthing-archive-keyring.gpg] https://apt.syncthing.net/ syncthing stable” | sudo tee /etc/apt/sources.list.d/syncthing.list -bash: sudo: command not found root@Netgear-NAS:~# echo “deb [signed-by=/usr/share/keyrings/syncthing-archive-keyring.gpg] https://apt.syncthing.net/ syncthing stable” | tee /etc/apt/sources.list.d/syncthing.list deb [signed-by=/usr/share/keyrings/syncthing-archive-keyring.gpg] https://apt.syncthing.net/ syncthing stable root@Netgear-NAS:~# printf “Package: *\nPin: origin apt.syncthing.net\nPin-Priority: 990\n” | tee /etc/apt/preferences.d/syncthing Package: * Pin: origin apt.syncthing.net Pin-Priority: 990 root@Netgear-NAS:~# apt-get update Hit:1 http://security.debian.org jessie/updates InRelease Ign:2 http://mirrors.edge.kernel.org/debian jessie InRelease Hit:3 http://mirrors.edge.kernel.org/debian jessie Release Get:4 https://apt.syncthing.net syncthing InRelease [15.1 kB] Get:6 https://apt.syncthing.net syncthing/stable armel Packages [2,229 B] Get:7 https://apt.syncthing.net syncthing/stable armhf Packages [2,217 B] Ign:8 https://apt.readynas.com/packages/readynasos 6.10.4 InRelease Get:9 https://apt.readynas.com/packages/readynasos 6.10.4 Release [22.2 kB] Get:10 https://apt.readynas.com/packages/readynasos 6.10.4 Release.gpg [488 B] Fetched 42.2 kB in 29s (1,413 B/s) Reading package lists… Done root@Netgear-NAS:~# apt-get install syncthing Reading package lists… Done Building dependency tree Reading state information… Done The following NEW packages will be installed: syncthing 0 upgraded, 1 newly installed, 0 to remove and 34 not upgraded. Need to get 9,068 kB of archives. After this operation, 20.7 MB of additional disk space will be used. Get:1 https://apt.syncthing.net syncthing/stable armel syncthing armel 1.15.1 [9,068 kB] Fetched 9,068 kB in 3s (2,451 kB/s) debconf: delaying package configuration, since apt-utils is not installed Selecting previously unselected package syncthing. (Reading database … 19051 files and directories currently installed.) Preparing to unpack …/syncthing_1.15.1_armel.deb … Unpacking syncthing (1.15.1) … Processing triggers for mime-support (3.58) … Setting up syncthing (1.15.1) … root@Netgear-NAS:~# systemctl enable syncthing@karst.service Created symlink /etc/systemd/system/multi-user.target.wants/syncthing@karst.service → /lib/systemd/system/syncthing@.service. root@Netgear-NAS:~# systemctl start syncthing@karst.service root@Netgear-NAS:~# systemctl status syncthing@karst.service ● syncthing@karst.service - Syncthing - Open Source Continuous File S ynchronization for karst Loaded: loaded (/lib/systemd/system/syncthing@.service; enabled; vendor prese t: enabled) Active: failed (Result: start-limit-hit) since Mon 2021-04-26 22:1 6:17 EDT; 55s ago Docs: man:syncthing(1) Process: 28060 ExecStart=/usr/bin/syncthing serve --no-browser --no-restart – logflags=0 (code=exited, status=217/USER) Main PID: 28060 (code=exited, status=217/USER)

Apr 26 22:16:16 Netgear-NAS systemd[1]: syncthing@karst.service: Failed with result ‘exit-code’. Apr 26 22:16:17 Netgear-NAS systemd[1]: syncthing@karst.service: Service hold-of f time over, scheduling restart. Apr 26 22:16:17 Netgear-NAS systemd[1]: Stopped Syncthing - Open Source Continuo us File Synchronization for karst. Apr 26 22:16:17 Netgear-NAS systemd[1]: syncthing@karst.service: Start r equest repeated too quickly. Apr 26 22:16:17 Netgear-NAS systemd[1]: Failed to start Syncthing - Open Source Continuous File Synchronization for karst. Apr 26 22:16:17 Netgear-NAS systemd[1]: syncthing@karst.service: Unit en tered failed state. Apr 26 22:16:17 Netgear-NAS systemd[1]: syncthing@karst.service: Failed with result ‘start-limit-hit’. root@Netgear-NAS:~#

bt90 · April 27, 2021, 5:12am

journalctl -u syncthing@karst.service

Chris.Karst · April 27, 2021, 12:20pm

random command with no context?

how about this one?: Delete all

Diagnose service startup?

Is this what you want to see?

root@Netgear-NAS:~# journalctl -u syncthing@karst.service
-- Logs begin at Tue 2021-03-16 22:11:22 EDT, end at Tue 2021-04-27 08:37:17 EDT
. --
Apr 26 22:15:39 Netgear-NAS systemd[1]: [/lib/systemd/system/syncthing@.
service:11] Unknown lvalue 'StartLimitIntervalSec' in section 'Service'
Apr 26 22:15:39 Netgear-NAS systemd[1]: [/lib/systemd/system/syncthing@.
service:20] Unknown lvalue 'MemoryDenyWriteExecute' in section 'Service'
Apr 26 22:16:12 Netgear-NAS systemd[1]: Started Syncthing - Open Source Continuo
us File Synchronization for karst.
Apr 26 22:16:12 Netgear-NAS systemd[28032]: syncthing@karst.service: Fai
led at step USER spawning /usr/bin/syncthing: No such process
Apr 26 22:16:12 Netgear-NAS systemd[1]: syncthing@karst.service: Main pr
ocess exited, code=exited, status=217/USER
Apr 26 22:16:12 Netgear-NAS systemd[1]: syncthing@karst.service: Unit en
tered failed state.
Apr 26 22:16:12 Netgear-NAS systemd[1]: syncthing@karst.service: Failed
with result 'exit-code'.
Apr 26 22:16:13 Netgear-NAS systemd[1]: syncthing@karst.service: Service hold-of
f time over, scheduling restart.
Apr 26 22:16:13 Netgear-NAS systemd[1]: Stopped Syncthing - Open Source Continuo
us File Synchronization for karst.
Apr 26 22:16:13 Netgear-NAS systemd[1]: Started Syncthing - Open Source Continuo
us File Synchronization for karst.
Apr 26 22:16:13 Netgear-NAS systemd[28043]: syncthing@karst.service: Fai
led at step USER spawning /usr/bin/syncthing: No such process
Apr 26 22:16:13 Netgear-NAS systemd[1]: syncthing@karst.service: Main pr
ocess exited, code=exited, status=217/USER
Apr 26 22:16:13 Netgear-NAS systemd[1]: syncthing@karst.service: Unit en
tered failed state.
Apr 26 22:16:13 Netgear-NAS systemd[1]: syncthing@karst.service: Failed
with result 'exit-code'.
Apr 26 22:16:14 Netgear-NAS systemd[1]: syncthing@karst.service: Service hold-of
f time over, scheduling restart.
Apr 26 22:16:14 Netgear-NAS systemd[1]: Stopped Syncthing - Open Source Continuo
us File Synchronization for karst.
Apr 26 22:16:14 Netgear-NAS systemd[1]: Started Syncthing - Open Source Continuo
us File Synchronization for karst.
Apr 26 22:16:15 Netgear-NAS systemd[28052]: syncthing@karst.service: Fai
led at step USER spawning /usr/bin/syncthing: No such process
Apr 26 22:16:15 Netgear-NAS systemd[1]: syncthing@karst.service: Main pr
ocess exited, code=exited, status=217/USER
Apr 26 22:16:15 Netgear-NAS systemd[1]: syncthing@karst.service: Unit en
tered failed state.
Apr 26 22:16:15 Netgear-NAS systemd[1]: syncthing@karst.service: Failed
with result 'exit-code'.
Apr 26 22:16:16 Netgear-NAS systemd[1]: syncthing@karst.service: Service hold-of
f time over, scheduling restart.
Apr 26 22:16:16 Netgear-NAS systemd[1]: Stopped Syncthing - Open Source Continuo
us File Synchronization for karst.
Apr 26 22:16:16 Netgear-NAS systemd[1]: Started Syncthing - Open Source Continuo
us File Synchronization for karst.
Apr 26 22:16:16 Netgear-NAS systemd[28060]: syncthing@karst.service: Fai
led at step USER spawning /usr/bin/syncthing: No such process
Apr 26 22:16:16 Netgear-NAS systemd[1]: syncthing@karst.service: Main pr
ocess exited, code=exited, status=217/USER
Apr 26 22:16:16 Netgear-NAS systemd[1]: syncthing@karst.service: Unit en
tered failed state.
Apr 26 22:16:16 Netgear-NAS systemd[1]: syncthing@karst.service: Failed
with result 'exit-code'.
Apr 26 22:16:17 Netgear-NAS systemd[1]: syncthing@karst.service: Service hold-of
f time over, scheduling restart.
Apr 26 22:16:17 Netgear-NAS systemd[1]: Stopped Syncthing - Open Source Continuo
us File Synchronization for karst.
Apr 26 22:16:17 Netgear-NAS systemd[1]: syncthing@karst.service: Start r
equest repeated too quickly.
Apr 26 22:16:17 Netgear-NAS systemd[1]: Failed to start Syncthing - Open
 Source Continuous File Synchronization for karst.
Apr 26 22:16:17 Netgear-NAS systemd[1]: syncthing@karst.service: Unit en
tered failed state.
Apr 26 22:16:17 Netgear-NAS systemd[1]: syncthing@karst.service: Failed
with result 'start-limit-hit'.
Apr 26 22:32:31 Netgear-NAS systemd[1]: [/lib/systemd/system/syncthing@.
service:11] Unknown lvalue 'StartLimitIntervalSec' in section 'Service'
Apr 26 22:32:31 Netgear-NAS systemd[1]: [/lib/systemd/system/syncthing@.
service:20] Unknown lvalue 'MemoryDenyWriteExecute' in section 'Service'
-- Reboot --
Apr 26 22:33:32 Netgear-NAS systemd[1]: Started Syncthing - Open Source Continuo
us File Synchronization for karst.
Apr 26 22:33:32 Netgear-NAS systemd[1]: syncthing@karst.service: Main pr
ocess exited, code=exited, status=217/USER
Apr 26 22:33:32 Netgear-NAS systemd[1]: syncthing@karst.service: Unit en
tered failed state.
Apr 26 22:33:32 Netgear-NAS systemd[1]: syncthing@karst.service: Failed
with result 'exit-code'.
Apr 26 22:33:35 Netgear-NAS systemd[1]: syncthing@karst.service: Service hold-of
f time over, scheduling restart.
Apr 26 22:33:35 Netgear-NAS systemd[1]: Stopped Syncthing - Open Source Continuo
us File Synchronization for karst.
Apr 26 22:33:35 Netgear-NAS systemd[1]: Started Syncthing - Open Source Continuo
us File Synchronization for karst.
Apr 26 22:33:35 Netgear-NAS systemd[2198]: syncthing@karst.service: Fail
ed at step USER spawning /usr/bin/syncthing: No such process
Apr 26 22:33:35 Netgear-NAS systemd[1]: syncthing@karst.service: Main pr
ocess exited, code=exited, status=217/USER
Apr 26 22:33:35 Netgear-NAS systemd[1]: syncthing@karst.service: Unit en
tered failed state.
Apr 26 22:33:35 Netgear-NAS systemd[1]: syncthing@karst.service: Failed
with result 'exit-code'.
Apr 26 22:33:37 Netgear-NAS systemd[1]: syncthing@karst.service: Service hold-of
f time over, scheduling restart.
Apr 26 22:33:37 Netgear-NAS systemd[1]: Stopped Syncthing - Open Source Continuo
us File Synchronization for karst.
Apr 26 22:33:37 Netgear-NAS systemd[1]: Started Syncthing - Open Source Continuo
us File Synchronization for karst.
Apr 26 22:33:37 Netgear-NAS systemd[1]: syncthing@karst.service: Main pr
ocess exited, code=exited, status=217/USER
Apr 26 22:33:37 Netgear-NAS systemd[1]: syncthing@karst.service: Unit en
tered failed state.
Apr 26 22:33:37 Netgear-NAS systemd[1]: syncthing@karst.service: Failed
with result 'exit-code'.
Apr 26 22:33:38 Netgear-NAS systemd[1]: syncthing@karst.service: Service hold-of
f time over, scheduling restart.
Apr 26 22:33:38 Netgear-NAS systemd[1]: Stopped Syncthing - Open Source Continuo
us File Synchronization for karst.
Apr 26 22:33:38 Netgear-NAS systemd[1]: Started Syncthing - Open Source Continuo
us File Synchronization for karst.
Apr 26 22:33:38 Netgear-NAS systemd[2210]: syncthing@karst.service: Fail
ed at step USER spawning /usr/bin/syncthing: No such process
Apr 26 22:33:38 Netgear-NAS systemd[1]: syncthing@karst.service: Main pr
ocess exited, code=exited, status=217/USER
Apr 26 22:33:38 Netgear-NAS systemd[1]: syncthing@karst.service: Unit en
tered failed state.
Apr 26 22:33:38 Netgear-NAS systemd[1]: syncthing@karst.service: Failed
with result 'exit-code'.
Apr 26 22:33:39 Netgear-NAS systemd[1]: syncthing@karst.service: Service hold-of
f time over, scheduling restart.
Apr 26 22:33:39 Netgear-NAS systemd[1]: Stopped Syncthing - Open Source Continuo
us File Synchronization for karst.
Apr 26 22:33:39 Netgear-NAS systemd[1]: syncthing@karst.service: Start r
equest repeated too quickly.
Apr 26 22:33:39 Netgear-NAS systemd[1]: Failed to start Syncthing - Open
 Source Continuous File Synchronization for karst.
Apr 26 22:33:39 Netgear-NAS systemd[1]: syncthing@karst.service: Unit en
tered failed state.
Apr 26 22:33:39 Netgear-NAS systemd[1]: syncthing@karst.service: Failed
with result 'start-limit-hit'.
Apr 26 22:33:45 Netgear-NAS systemd[1]: [/lib/systemd/system/syncthing@.
service:11] Unknown lvalue 'StartLimitIntervalSec' in section 'Service'
Apr 26 22:33:45 Netgear-NAS systemd[1]: [/lib/systemd/system/syncthing@.
service:20] Unknown lvalue 'MemoryDenyWriteExecute' in section 'Service'
Apr 26 22:35:17 Netgear-NAS systemd[1]: [/lib/systemd/system/syncthing@.
service:11] Unknown lvalue 'StartLimitIntervalSec' in section 'Service'
Apr 26 22:35:17 Netgear-NAS systemd[1]: [/lib/systemd/system/syncthing@.
service:20] Unknown lvalue 'MemoryDenyWriteExecute' in section 'Service'
Apr 26 22:35:20 Netgear-NAS systemd[1]: [/lib/systemd/system/syncthing@.
service:11] Unknown lvalue 'StartLimitIntervalSec' in section 'Service'
Apr 26 22:35:20 Netgear-NAS systemd[1]: [/lib/systemd/system/syncthing@.
service:20] Unknown lvalue 'MemoryDenyWriteExecute' in section 'Service'

imsodin · April 27, 2021, 1:40pm

Lets stay nice - people are trying to help you. And terse (and actually very to the point and helpful) help is much better than no help.

Yes. It shows that Syncthing isn’t present where it should be /usr/bin/syncthing.
Given you posted in a topic before with an outdated, unnecessarily complicated installation tutorial: Did you follow that? If yes, undo (remove) everything you installed then and re-install as explained on apt.syncthing.net - that should clear out this problem.

Chris.Karst · April 27, 2021, 7:41pm

Didn’t mean to sound rude, just have always taught don’t use a command without knowing what it was. Comment mentioned a command with zero context of what it was or what to do with it.

As to which instructions I used, I used the uses you just mentioned. I had found the other page I commented on first, but had not used them. I also noticed they were quite dated. Was just asking to see if that info was still correct. Obviously is wasn’t due to age.

As to things not in the correct spot: I believe I followed the instructions you pointed to, did I miss something?

bt90 · April 27, 2021, 9:08pm

Does the user exist? Could you check if the binary is where it should be using:

ls -lah /usr/bin/syncthing

Chris.Karst · April 27, 2021, 10:23pm

root@Netgear-NAS:~# ls -lah /usr/bin/syncthing

-rwxr-xr-x 1 root root 20M Apr 6 04:47 /usr/bin/syncthing

Does that show what you need?

bt90 · April 28, 2021, 5:37am

So the binary does in fact exist and has a reasonable size. Very basic test if it’s runnable:

syncthing --version

Are you sure that the user karst exists? To check this:

id -u karst

Chris.Karst · April 28, 2021, 11:14am

root@Netgear-NAS:~# syncthing --version

syncthing v1.15.1 “Fermium Flea” (go1.16.3 linux-arm) deb@build.syncthing.net 2021-04-06 08:42:29 UTC [noupgrade]

root@Netgear-NAS:~# id -u karst

id: ‘karst’: no such user

oops, apparently this NAS only has an admin user, unlike all my other devices.

Which option is best:

just create karst user
do i have to create karst user and repair install?
repair using admin user

bt90 · April 28, 2021, 12:21pm

A dedicated non-root user is always preferable. The service should be startable once you create the user karst

Chris.Karst · April 28, 2021, 12:31pm

created a user karst

Now i got this:

root@Netgear-NAS:~# systemctl enable syncthing@karst.service root@Netgear-NAS:~# systemctl start syncthing@karst.service root@Netgear-NAS:~# systemctl status syncthing@karst.service ● syncthing@karst.service - Syncthing - Open Source Continuous File S ynchronization for karst Loaded: loaded (/lib/systemd/system/syncthing@.service; enabled; vendor prese t: enabled) Active: failed (Result: start-limit-hit) since Wed 2021-04-28 08:2 8:05 EDT; 34s ago Docs: man:syncthing(1) Process: 7247 ExecStart=/usr/bin/syncthing serve --no-browser --no-restart --l ogflags=0 (code=exited, status=1/FAILURE) Main PID: 7247 (code=exited, status=1/FAILURE)

Apr 28 08:28:04 Netgear-NAS systemd[1]: syncthing@karst.service: Failed with result ‘exit-code’. Apr 28 08:28:05 Netgear-NAS systemd[1]: syncthing@karst.service: Service hold-of f time over, scheduling restart. Apr 28 08:28:05 Netgear-NAS systemd[1]: Stopped Syncthing - Open Source Continuo us File Synchronization for karst. Apr 28 08:28:05 Netgear-NAS systemd[1]: syncthing@karst.service: Start r equest repeated too quickly. Apr 28 08:28:05 Netgear-NAS systemd[1]: Failed to start Syncthing - Open Source Continuous File Synchronization for karst. Apr 28 08:28:05 Netgear-NAS systemd[1]: syncthing@karst.service: Unit en tered failed state. Apr 28 08:28:05 Netgear-NAS systemd[1]: syncthing@karst.service: Failed with result ‘start-limit-hit’.

Chris.Karst · April 28, 2021, 12:45pm

Also, Syncthing does not show as an installed App on the ReadyNAS GUI.

Should it?

bt90 · April 28, 2021, 12:57pm

Syncthing does not provide any integration for the NAS GUI. Could you retrieve the logs using the previous journalctl command?

Chris.Karst · April 28, 2021, 11:00pm

(extra question: how can i prevent everything from running together without having to doublespace everything?)

root@Netgear-NAS:~# journalctl -u syncthing@karst.service – Logs begin at Tue 2021-03-16 22:11:22 EDT, end at Wed 2021-04-28 18:58:23 EDT . – Apr 26 22:15:39 Netgear-NAS systemd[1]: [/lib/systemd/system/syncthing@. service:11] Unknown lvalue ‘StartLimitIntervalSec’ in section ‘Service’ Apr 26 22:15:39 Netgear-NAS systemd[1]: [/lib/systemd/system/syncthing@. service:20] Unknown lvalue ‘MemoryDenyWriteExecute’ in section ‘Service’ Apr 26 22:16:12 Netgear-NAS systemd[1]: Started Syncthing - Open Source Continuo us File Synchronization for karst. Apr 26 22:16:12 Netgear-NAS systemd[28032]: syncthing@karst.service: Fai led at step USER spawning /usr/bin/syncthing: No such process Apr 26 22:16:12 Netgear-NAS systemd[1]: syncthing@karst.service: Main pr ocess exited, code=exited, status=217/USER Apr 26 22:16:12 Netgear-NAS systemd[1]: syncthing@karst.service: Unit en tered failed state. Apr 26 22:16:12 Netgear-NAS systemd[1]: syncthing@karst.service: Failed with result ‘exit-code’. Apr 26 22:16:13 Netgear-NAS systemd[1]: syncthing@karst.service: Service hold-of f time over, scheduling restart. Apr 26 22:16:13 Netgear-NAS systemd[1]: Stopped Syncthing - Open Source Continuo us File Synchronization for karst. Apr 26 22:16:13 Netgear-NAS systemd[1]: Started Syncthing - Open Source Continuo us File Synchronization for karst. Apr 26 22:16:13 Netgear-NAS systemd[28043]: syncthing@karst.service: Fai led at step USER spawning /usr/bin/syncthing: No such process Apr 26 22:16:13 Netgear-NAS systemd[1]: syncthing@karst.service: Main pr ocess exited, code=exited, status=217/USER Apr 26 22:16:13 Netgear-NAS systemd[1]: syncthing@karst.service: Unit en tered failed state. Apr 26 22:16:13 Netgear-NAS systemd[1]: syncthing@karst.service: Failed with result ‘exit-code’. Apr 26 22:16:14 Netgear-NAS systemd[1]: syncthing@karst.service: Service hold-of f time over, scheduling restart. Apr 26 22:16:14 Netgear-NAS systemd[1]: Stopped Syncthing - Open Source Continuo us File Synchronization for karst. Apr 26 22:16:14 Netgear-NAS systemd[1]: Started Syncthing - Open Source Continuo us File Synchronization for karst. Apr 26 22:16:15 Netgear-NAS systemd[28052]: syncthing@karst.service: Fai led at step USER spawning /usr/bin/syncthing: No such process Apr 26 22:16:15 Netgear-NAS systemd[1]: syncthing@karst.service: Main pr ocess exited, code=exited, status=217/USER Apr 26 22:16:15 Netgear-NAS systemd[1]: syncthing@karst.service: Unit en tered failed state. Apr 26 22:16:15 Netgear-NAS systemd[1]: syncthing@karst.service: Failed with result ‘exit-code’. Apr 26 22:16:16 Netgear-NAS systemd[1]: syncthing@karst.service: Service hold-of f time over, scheduling restart. Apr 26 22:16:16 Netgear-NAS systemd[1]: Stopped Syncthing - Open Source Continuo us File Synchronization for karst. Apr 26 22:16:16 Netgear-NAS systemd[1]: Started Syncthing - Open Source Continuo us File Synchronization for karst. Apr 26 22:16:16 Netgear-NAS systemd[28060]: syncthing@karst.service: Fai led at step USER spawning /usr/bin/syncthing: No such process Apr 26 22:16:16 Netgear-NAS systemd[1]: syncthing@karst.service: Main pr ocess exited, code=exited, status=217/USER Apr 26 22:16:16 Netgear-NAS systemd[1]: syncthing@karst.service: Unit en tered failed state. Apr 26 22:16:16 Netgear-NAS systemd[1]: syncthing@karst.service: Failed with result ‘exit-code’. Apr 26 22:16:17 Netgear-NAS systemd[1]: syncthing@karst.service: Service hold-of f time over, scheduling restart. Apr 26 22:16:17 Netgear-NAS systemd[1]: Stopped Syncthing - Open Source Continuo us File Synchronization for karst. Apr 26 22:16:17 Netgear-NAS systemd[1]: syncthing@karst.service: Start r equest repeated too quickly. Apr 26 22:16:17 Netgear-NAS systemd[1]: Failed to start Syncthing - Open Source Continuous File Synchronization for karst. Apr 26 22:16:17 Netgear-NAS systemd[1]: syncthing@karst.service: Unit en tered failed state. Apr 26 22:16:17 Netgear-NAS systemd[1]: syncthing@karst.service: Failed with result ‘start-limit-hit’. Apr 26 22:32:31 Netgear-NAS systemd[1]: [/lib/systemd/system/syncthing@. service:11] Unknown lvalue ‘StartLimitIntervalSec’ in section ‘Service’ Apr 26 22:32:31 Netgear-NAS systemd[1]: [/lib/systemd/system/syncthing@. service:20] Unknown lvalue ‘MemoryDenyWriteExecute’ in section ‘Service’ – Reboot – Apr 26 22:33:32 Netgear-NAS systemd[1]: Started Syncthing - Open Source Continuo us File Synchronization for karst. Apr 26 22:33:32 Netgear-NAS systemd[1]: syncthing@karst.service: Main pr ocess exited, code=exited, status=217/USER Apr 26 22:33:32 Netgear-NAS systemd[1]: syncthing@karst.service: Unit en tered failed state. Apr 26 22:33:32 Netgear-NAS systemd[1]: syncthing@karst.service: Failed with result ‘exit-code’. Apr 26 22:33:35 Netgear-NAS systemd[1]: syncthing@karst.service: Service hold-of f time over, scheduling restart. Apr 26 22:33:35 Netgear-NAS systemd[1]: Stopped Syncthing - Open Source Continuo us File Synchronization for karst. Apr 26 22:33:35 Netgear-NAS systemd[1]: Started Syncthing - Open Source Continuo us File Synchronization for karst. Apr 26 22:33:35 Netgear-NAS systemd[2198]: syncthing@karst.service: Fail ed at step USER spawning /usr/bin/syncthing: No such process Apr 26 22:33:35 Netgear-NAS systemd[1]: syncthing@karst.service: Main pr ocess exited, code=exited, status=217/USER Apr 26 22:33:35 Netgear-NAS systemd[1]: syncthing@karst.service: Unit en tered failed state. Apr 26 22:33:35 Netgear-NAS systemd[1]: syncthing@karst.service: Failed with result ‘exit-code’. Apr 26 22:33:37 Netgear-NAS systemd[1]: syncthing@karst.service: Service hold-of f time over, scheduling restart. Apr 26 22:33:37 Netgear-NAS systemd[1]: Stopped Syncthing - Open Source Continuo us File Synchronization for karst. Apr 26 22:33:37 Netgear-NAS systemd[1]: Started Syncthing - Open Source Continuo us File Synchronization for karst. Apr 26 22:33:37 Netgear-NAS systemd[1]: syncthing@karst.service: Main pr ocess exited, code=exited, status=217/USER Apr 26 22:33:37 Netgear-NAS systemd[1]: syncthing@karst.service: Unit en tered failed state. Apr 26 22:33:37 Netgear-NAS systemd[1]: syncthing@karst.service: Failed with result ‘exit-code’. Apr 26 22:33:38 Netgear-NAS systemd[1]: syncthing@karst.service: Service hold-of f time over, scheduling restart. Apr 26 22:33:38 Netgear-NAS systemd[1]: Stopped Syncthing - Open Source Continuo us File Synchronization for karst. Apr 26 22:33:38 Netgear-NAS systemd[1]: Started Syncthing - Open Source Continuo us File Synchronization for karst. Apr 26 22:33:38 Netgear-NAS systemd[2210]: syncthing@karst.service: Fail ed at step USER spawning /usr/bin/syncthing: No such process Apr 26 22:33:38 Netgear-NAS systemd[1]: syncthing@karst.service: Main pr ocess exited, code=exited, status=217/USER Apr 26 22:33:38 Netgear-NAS systemd[1]: syncthing@karst.service: Unit en tered failed state. Apr 26 22:33:38 Netgear-NAS systemd[1]: syncthing@karst.service: Failed with result ‘exit-code’. Apr 26 22:33:39 Netgear-NAS systemd[1]: syncthing@karst.service: Service hold-of f time over, scheduling restart. Apr 26 22:33:39 Netgear-NAS systemd[1]: Stopped Syncthing - Open Source Continuo us File Synchronization for karst. Apr 26 22:33:39 Netgear-NAS systemd[1]: syncthing@karst.service: Start r equest repeated too quickly. Apr 26 22:33:39 Netgear-NAS systemd[1]: Failed to start Syncthing - Open Source Continuous File Synchronization for karst. Apr 26 22:33:39 Netgear-NAS systemd[1]: syncthing@karst.service: Unit en tered failed state. Apr 26 22:33:39 Netgear-NAS systemd[1]: syncthing@karst.service: Failed with result ‘start-limit-hit’. Apr 26 22:33:45 Netgear-NAS systemd[1]: [/lib/systemd/system/syncthing@. service:11] Unknown lvalue ‘StartLimitIntervalSec’ in section ‘Service’ Apr 26 22:33:45 Netgear-NAS systemd[1]: [/lib/systemd/system/syncthing@. service:20] Unknown lvalue ‘MemoryDenyWriteExecute’ in section ‘Service’ Apr 26 22:35:17 Netgear-NAS systemd[1]: [/lib/systemd/system/syncthing@. service:11] Unknown lvalue ‘StartLimitIntervalSec’ in section ‘Service’ Apr 26 22:35:17 Netgear-NAS systemd[1]: [/lib/systemd/system/syncthing@. service:20] Unknown lvalue ‘MemoryDenyWriteExecute’ in section ‘Service’ Apr 26 22:35:20 Netgear-NAS systemd[1]: [/lib/systemd/system/syncthing@. service:11] Unknown lvalue ‘StartLimitIntervalSec’ in section ‘Service’ Apr 26 22:35:20 Netgear-NAS systemd[1]: [/lib/systemd/system/syncthing@. service:20] Unknown lvalue ‘MemoryDenyWriteExecute’ in section ‘Service’ Apr 28 08:27:24 Netgear-NAS systemd[1]: [/lib/systemd/system/syncthing@. service:11] Unknown lvalue ‘StartLimitIntervalSec’ in section ‘Service’ Apr 28 08:27:24 Netgear-NAS systemd[1]: [/lib/systemd/system/syncthing@. service:20] Unknown lvalue ‘MemoryDenyWriteExecute’ in section ‘Service’ Apr 28 08:28:00 Netgear-NAS systemd[1]: Started Syncthing - Open Source Continuo us File Synchronization for karst. Apr 28 08:28:01 Netgear-NAS syncthing[7192]: WARNING: Failure on home directory: mkdir /home/karst: permission denied Apr 28 08:28:01 Netgear-NAS systemd[1]: syncthing@karst.service: Main pr ocess exited, code=exited, status=1/FAILURE Apr 28 08:28:01 Netgear-NAS systemd[1]: syncthing@karst.service: Unit en tered failed state. Apr 28 08:28:01 Netgear-NAS systemd[1]: syncthing@karst.service: Failed with result ‘exit-code’. Apr 28 08:28:02 Netgear-NAS systemd[1]: syncthing@karst.service: Service hold-of f time over, scheduling restart. Apr 28 08:28:02 Netgear-NAS systemd[1]: Stopped Syncthing - Open Source Continuo us File Synchronization for karst. Apr 28 08:28:02 Netgear-NAS systemd[1]: Started Syncthing - Open Source Continuo us File Synchronization for karst. Apr 28 08:28:02 Netgear-NAS syncthing[7204]: WARNING: Failure on home directory: mkdir /home/karst: permission denied Apr 28 08:28:02 Netgear-NAS systemd[1]: syncthing@karst.service: Main pr ocess exited, code=exited, status=1/FAILURE Apr 28 08:28:02 Netgear-NAS systemd[1]: syncthing@karst.service: Unit en tered failed state. Apr 28 08:28:02 Netgear-NAS systemd[1]: syncthing@karst.service: Failed with result ‘exit-code’. Apr 28 08:28:03 Netgear-NAS systemd[1]: syncthing@karst.service: Service hold-of f time over, scheduling restart. Apr 28 08:28:03 Netgear-NAS systemd[1]: Stopped Syncthing - Open Source Continuo us File Synchronization for karst. Apr 28 08:28:03 Netgear-NAS systemd[1]: Started Syncthing - Open Source Continuo us File Synchronization for karst. Apr 28 08:28:03 Netgear-NAS syncthing[7223]: WARNING: Failure on home directory: mkdir /home/karst: permission denied Apr 28 08:28:03 Netgear-NAS systemd[1]: syncthing@karst.service: Main pr ocess exited, code=exited, status=1/FAILURE Apr 28 08:28:03 Netgear-NAS systemd[1]: syncthing@karst.service: Unit en tered failed state. Apr 28 08:28:03 Netgear-NAS systemd[1]: syncthing@karst.service: Failed with result ‘exit-code’. Apr 28 08:28:04 Netgear-NAS systemd[1]: syncthing@karst.service: Service hold-of f time over, scheduling restart. Apr 28 08:28:04 Netgear-NAS systemd[1]: Stopped Syncthing - Open Source Continuo us File Synchronization for karst. Apr 28 08:28:04 Netgear-NAS systemd[1]: Started Syncthing - Open Source Continuo us File Synchronization for karst. Apr 28 08:28:04 Netgear-NAS syncthing[7247]: WARNING: Failure on home directory: mkdir /home/karst: permission denied Apr 28 08:28:04 Netgear-NAS systemd[1]: syncthing@karst.service: Main pr ocess exited, code=exited, status=1/FAILURE Apr 28 08:28:04 Netgear-NAS systemd[1]: syncthing@karst.service: Unit en tered failed state. Apr 28 08:28:04 Netgear-NAS systemd[1]: syncthing@karst.service: Failed with result ‘exit-code’. Apr 28 08:28:05 Netgear-NAS systemd[1]: syncthing@karst.service: Service hold-of f time over, scheduling restart. Apr 28 08:28:05 Netgear-NAS systemd[1]: Stopped Syncthing - Open Source Continuo us File Synchronization for karst. Apr 28 08:28:05 Netgear-NAS systemd[1]: syncthing@karst.service: Start r equest repeated too quickly. Apr 28 08:28:05 Netgear-NAS systemd[1]: Failed to start Syncthing - Open Source Continuous File Synchronization for karst. Apr 28 08:28:05 Netgear-NAS systemd[1]: syncthing@karst.service: Unit en tered failed state. Apr 28 08:28:05 Netgear-NAS systemd[1]: syncthing@karst.service: Failed with result ‘start-limit-hit’.

Chris.Karst · April 28, 2021, 11:11pm

i see a permission denied,

does user karst need to be an admin?

Chris.Karst · April 29, 2021, 3:26am

set user karst as an admin.

setting user karst as an admin did not seem to fixit.

bt90 · April 29, 2021, 5:07am

The home folder of the user doesn’t exist or has the wrong permissions:

Failure on home directory:
mkdir /home/karst: permission denied

That should fix it:

sudo mkdir -p /home/karst
sudo chown -R karst:karst /home/karst

This will create folder if it doesn’t exist yet and changes the ownership of it to the user karst.

imsodin · April 29, 2021, 7:06am

Enclose it with tripple backticks ```, either placing them manually or marking the text and pressing the </> button in the “forum text editor”.

Chris.Karst · April 29, 2021, 11:46am

root@Netgear-NAS:~# sudo mkdir -p /home/karst
-bash: sudo: command not found
root@Netgear-NAS:~# mkdir -p /home/karst
root@Netgear-NAS:~# chown -R karst:karst /home/karst
chown: invalid group: ‘karst:karst’

At this point, i created a Group named karst in the NAS GUI, then tried again.

root@Netgear-NAS:~# chown -R karst:karst /home/karst
root@Netgear-NAS:~# systemctl enable syncthing@karst.service
root@Netgear-NAS:~# systemctl start syncthing@karst.service
root@Netgear-NAS:~# systemctl status syncthing@karst.service
● syncthing@karst.service - Syncthing - Open Source Continuous File S
ynchronization for karst
   Loaded: loaded (/lib/systemd/system/syncthing@.service; enabled; vendor prese
t: enabled)
   Active: active (running) since Thu 2021-04-29 07:41:38 EDT; 12s ag
o
     Docs: man:syncthing(1)
 Main PID: 14046 (syncthing)
   CGroup: /system.slice/system-syncthing.slice/syncthing@karst.service
           ├─14046 /usr/bin/syncthing serve --no-browser --no-restart --logflags
=0
           └─14057 /usr/bin/syncthing serve --no-browser --no-restart --logflags
=0

Apr 29 07:41:42 Netgear-NAS syncthing[14046]: [7JPYA] INFO: QUIC listener ([::]:
22000) starting
Apr 29 07:41:42 Netgear-NAS syncthing[14046]: [7JPYA] INFO: Loading HTTPS certif
icate: open /home/karst/.config/syncthing/https-cert.pem: no such file or direct
ory
Apr 29 07:41:42 Netgear-NAS syncthing[14046]: [7JPYA] INFO: Creating new HTTPS c
ertificate
Apr 29 07:41:42 Netgear-NAS syncthing[14046]: [7JPYA] INFO: TCP listener ([::]:2
2000) starting
Apr 29 07:41:42 Netgear-NAS syncthing[14046]: [7JPYA] INFO: Relay listener (dyna
mic+https://relays.syncthing.net/endpoint) starting
Apr 29 07:41:42 Netgear-NAS syncthing[14046]: [7JPYA] INFO: Ready to synchronize
 "Default Folder" (default) (sendreceive)
Apr 29 07:41:42 Netgear-NAS syncthing[14046]: [7JPYA] INFO: Completed initial sc
an of sendreceive folder "Default Folder" (default)
Apr 29 07:41:43 Netgear-NAS syncthing[14046]: [7JPYA] INFO: GUI and API listenin
g on 127.0.0.1:8384
Apr 29 07:41:43 Netgear-NAS syncthing[14046]: [7JPYA] INFO: Access the GUI via t
he following URL: http://127.0.0.1:8384/
Apr 29 07:41:43 Netgear-NAS syncthing[14046]: [7JPYA] INFO: My name is "Netgear-
NAS"
root@Netgear-NAS:~#

Chris.Karst · April 29, 2021, 11:55am

I obviously cant use http://127.0.0.1:8384/ to access it, because i have to access from a system with a screen.

I tried (actual device IP) 192.168.1.30:8384

“Can’t reach this page.” “refused to connect”

do i need to enable remote access for Syncthing?