Windows – stopping a service created via NSSM does not work
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- documentation, operating-systems
Research direction
Start with the Windows service setup and final settings described in the documentation, using the reported NSSM procedure. Reproduce the failed stop on Windows, then compare it with the browser restart workaround. Done means the service-stop behavior is explained or corrected in the documentation, with the workaround and expected result verified.
Written by the indexing model from the issue text.
Description
If Syncthing is installed on Windows as a service using NSSM, exactly as described in the documentation (--no-restart --no-browser --home=""), including the subsequent “final settings” (step 12), then after the initial service start (sc start "service name") it cannot be stopped by any means. The stopping process eventually times out, but the service never terminates. It cannot be stopped from the command line via SC or NSSM, nor from the GUI / MMC. To stop the service, it is necessary to kill the NSSM process.
This behavior was reproduced on two different Windows installations (Windows 10 LTSC and Windows Server 2019), with identical installation procedures, exactly according to the guide. The NSSM version was the latest available. The behavior was identical.
Workaround: After starting the service, stop Syncthing at least once from the browser/web interface running at ip:8384 (Actions / Restart). After doing this, the service can be stopped and started normally via MMC or from the command line (SC / NSSM). Until this is done, the service cannot be stopped.
- Dominant language
- Python
- Stars
- 327
- Forks
- 653
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from syncthing/docs
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Dark theme Open
Difficulty 5/5 Over a week Newbie friendliness 30/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
use-agent-os/agent-os#3314 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
BasedHardware/omi#15662 · 1 comment ·
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
AiursoftWeb/AnduinOS-2#19 ·