nsqio/nsq

nsqd: issues running as a NSSM service or scheduled task on windows

Open

#817 opened on Nov 28, 2016

View on GitHub
 (12 comments) (0 reactions) (0 assignees)Go (25,788 stars) (2,898 forks)batch import
bughelp wanted

Description

Running NSQd 0.3.8 in a user session on Windows works perfectly but running it any other way does not work.

Tested for Schedule Tasks

  • Pointing directly to nsqd.exe
  • Pointing directly to a bat file that starts nsqd.exe
  • Made my own golang program that does os.exec start on nsqd.exe
  • Made my own golang program that starts a bat file that starts nsqd.exe
  • Made a powershell script that uses start-process for nsqd.exe, and to the bad file
  • Have a C# program start nsqd.exe

I can see in the task manager that the process starts for a second and then goes away. In the results in the eventlog for the task is always that it starts "with return code 2147942401.". Google says this could be a permission problem but it does not seem to be the case. Tried running it as SYSTEM, NETWORK SERVICE, LOCAL SERVICE and a specific user. All this works if the scheduled task is set to Run only when user is logged on, then a console window pops up with the stdout information. Nothing works when its set to Run weather user is logged on or not. In my golang app, bat file and powershell script I tested I tried to capture the stdout from NSQd but nothing was ever captured.

Tested for Service

  • Have NSSM configured to point to nsqd.exe
  • Have NSSM configured to point to my golang program
  • Have NSSM configured to point to a bat file

In the NSSM log file it logs: "2016/11/28 11:10:30 The service process could not connect to the service controller."

Contributor guide

Tech stack
go
Domain
backend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
Windows service managementGo basicsNSSM usage
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Investigate why nsqd exits immediately when run as a Windows service or scheduled task. The error code 2147942401 (0x8007010B) commonly occurs when a console application fails to interact with the service controller. Examine nsqd's main function (likely in nsqd/main.go) to determine if it handles the SERVICE CONTROL environment or uses the Windows service API. Also check if the issue relates to console handle inheritance. Look for any existing PRs or comments that suggest a patch. Consider adding support for Windows service control via golang.org/x/sys/windows/svc.