Syncthing unresponsive constantly restarting

I have seen this now several times:

I have one very weak device (Raspi) which has (amongst several smaller ones) one very big folder. (About 665.000 files and 23k dirs.)

When I pause the big folder all is fine. sc starts and scans everything and eventually all is synced.

But when i activate the big folder (which I did reset 2 days ago by changing its id) it takes a while and finally syncthing reaches this state:

syncthing processes are constantly (maybe every second) starting and stopping.

sudo service syncthing@sync stop does not seem to do anything.

dmesg -w -T stopped printing sc logs 2 hours ago …

Last messages:

[Mo Sep 17 21:10:56 2018] systemd[1]: syncthing@backup.service holdoff time over, scheduling restart.
[Mo Sep 17 21:28:53 2018] systemd[1]: syncthing@backup.service holdoff time over, scheduling restart.
[Mo Sep 17 21:34:04 2018] systemd[1]: Unit syncthing@backup.service entered failed state.
[Mo Sep 17 21:34:04 2018] systemd[1]: syncthing@backup.service holdoff time over, scheduling restart.
[Mo Sep 17 21:34:06 2018] systemd[1]: Unit syncthing@backup.service entered failed state.
[Mo Sep 17 21:34:06 2018] systemd[1]: syncthing@backup.service holdoff time over, scheduling restart.

sudo service syncthing@sync status prints this:

● syncthing@sync.service - Syncthing - Open Source Continuous File Synchronization for sync
   Loaded: loaded (/lib/systemd/system/syncthing@.service; enabled)
   Active: inactive (dead) since Mo 2018-09-17 16:17:53 UTC; 5h 21min ago
     Docs: man:syncthing(1)
  Process: 30583 ExecStart=/usr/bin/syncthing -no-browser -no-restart -logflags=0 (code=killed, signal=PIPE)
 Main PID: 30583 (code=killed, signal=PIPE)

Sep 17 16:16:16 device-name syncthing[30583]: [2H2VL] INFO: Puller (folder "MY BIG FOLDER" (folder-id), file "some/dir/in/the/folder...sion of this file
Sep 17 16:16:16 device-name syncthing[30583]: [2H2VL] INFO: Puller (folder "MY BIG FOLDER" (folder-id), file "some/dir/in/the/folder...sion of this file
Sep 17 16:16:16 device-name syncthing[30583]: [2H2VL] INFO: Puller (folder "MY BIG FOLDER" (folder-id), file "some/dir/in/the/folder...sion of this file
Sep 17 16:16:19 device-name syncthing[30583]: [2H2VL] INFO: Puller (folder "MY BIG FOLDER" (folder-id), file "some/dir/in/the/folder...sion of this file
Sep 17 16:16:19 device-name syncthing[30583]: [2H2VL] INFO: Puller (folder "MY BIG FOLDER" (folder-id), file "some/dir/in/the/folder...sion of this file
Sep 17 16:16:19 device-name syncthing[30583]: [2H2VL] INFO: Puller (folder "MY BIG FOLDER" (folder-id), file "some/dir/in/the/folder...sion of this file
Sep 17 16:16:19 device-name syncthing[30583]: [2H2VL] INFO: Puller (folder "MY BIG FOLDER" (folder-id), file "some/dir/in/the/folder...sion of this file
Sep 17 16:16:19 device-name syncthing[30583]: [2H2VL] INFO: Puller (folder "MY BIG FOLDER" (folder-id), file "some/dir/in/the/folder...sion of this file
Sep 17 16:16:19 device-name syncthing[30583]: [2H2VL] INFO: Puller (folder "MY BIG FOLDER" (folder-id), file "some/dir/in/the/folder...sion of this file
Sep 17 21:35:12 device-name systemd[1]: Stopped Syncthing - Open Source Continuous File Synchronization for sync.

I tried to manually kill these sc processes, to no avail.

The only thing that helped solve this situation was rebooting.

EDIT: I just found out i can simply start sc again.

But there is still one sc process being constantly restarted:

top

  PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND
31356 sync      31  11  813260 283688   7880 S 227,8 30,0  12:06.16 syncthing
32594 backup    20   0  808124   8072   6320 R  29,1  0,9   0:00.88 syncthing << this one

It has a different user though … how is this possible at all?

What is happening here? What can i do?

Greetings Fred;

p.s. thinking about this: I believe the crash and the rampant processes are two unrelated phenomena.

Get a full log, as now it’s an small piece that doesn’t explain anything.

How to get it and how to send it without diclosing private information?

You can get it from the systemd logs, google can answer how to get logs from systemd. It’s not anonimised, so the only suggestion I have is to redact it yourself.

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