Syncthing thinks another copy is running

[mikh3x4]

Sometimes (recently it became more often) synching just stops working. Files aren’t synced and the GUI is inaccessible, but the process continues running. When this happens my logs quickly fill up with the following message:

[TGJ64] 02:50:53 INFO: syncthing v0.14.19 “Dysprosium Dragonfly” (go1.7.4 darwin-amd64) brew@elcapitanvm.local 2017-01-10 07:50:11 UTC [TGJ64] 02:50:53 INFO: My ID: XXXXXXX-XXXXXXX-XXXXXXX-XXXXXXX-XXXXXXX-XXXXXXX-XXXXXXX-XXXXXXX [TGJ64] 02:50:54 INFO: Single thread hash performance is 167 MB/s using crypto/sha256 (159 MB/s using minio/sha256-simd). [TGJ64] 02:50:54 FATAL: Cannot open database: resource temporarily unavailable - Is another copy of Syncthing already running?

But another copy of syncthing isn’t running! Output from ps aux | grep syncthing:

mik              2486   0.0  0.0 556692216     88   ??  S     4:32pm   0:00.00 /usr/local/opt/syncthing/bin/syncthing -no-browser -no-restart
mik               608   0.0  0.0 573436356   4076   ??  S    Wed01pm   0:06.18 /usr/local/opt/syncthing-inotify/bin/syncthing-inotify
mik             10204   0.0  0.0  2444056    804 s000  S+    3:03am   0:00.01 grep syncthing

However running brew services stop syncthing doesn’t stop syncthing from running, I need to kill -9 it and then restart to force the problem to temporarily disappear

I’m running a brewed syncthing 14.19 on El Capitan. I manage the synchting LaunchAgents using brew services. Interestingly I have two machines with almost identical setups but this only happens on one of them

I’d appreciate any help with this issue

[calmh (Jakob Borg)]

ps shows a syncthing process, so it is running. The log output you see is from another syncthing that launchd (presumably) is trying to start.

As for the root cause, hard to say. I haven’t heard about this issue before and I’m not sure what the brew build and package process does really.