[SERVER-3709] Windows service install does not work with the --service option Created: 29/Aug/11 Updated: 31/Jul/15 Resolved: 11/Aug/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Packaging |
| Affects Version/s: | 2.0.0-rc0, 2.3.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Sridhar Nanjundeswaran | Assignee: | Mark Benvenuto |
| Resolution: | Done | Votes: | 1 |
| Labels: | Windows | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Windows 7 x64 |
||
| Operating System: | ALL |
| Participants: |
| Description |
|
When --service is used in conjunction with --install it does not start the service as specified in the documentation. Additionally once this option is used the service cannot be started from the Services panel. It fails with Error 1053 - service did not respond to the start or control request. |
| Comments |
| Comment by Mark Benvenuto [ 11/Aug/14 ] |
|
With the current version in 2.7.x, during --install, --service is ignored. MongoD simply strips --service out of the command line when it creates the service, and then correctly adds one so the end result is that there is only one --service, and everything works as expected. |
| Comment by Tad Marshall [ 27/Nov/12 ] |
|
The bug here is that we do not detect a particular case of user error, and we allow this error to prevent correct installation. The --service option is used to specify that the program has been started by the Windows Service Control Manager and that startup and shutdown should be coordinated with the SCM. The --install option is used to specify that the program has been started from the command line and that instead of running normally it should install itself to be run later as a Windows service. These incompatible options should not be specified together. We should detect when they are both specified and issue an error message and exit. |