[SERVER-1877] Using single hyphen for install parameter will install un-startable Windows service Created: 30/Sep/10 Updated: 12/Jul/16 Resolved: 06/May/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin |
| Affects Version/s: | 1.6.1, 1.6.3 |
| Fix Version/s: | 2.1.2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Matt Smith | Assignee: | Tad Marshall |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Windows 2008 Server R2 |
||
| Operating System: | Windows |
| Participants: |
| Description |
|
When installing MongoDB as a Windows service with a single hyphen before the "install" parameter, the Windows service will be created. However, when attempting to start the service, the service will fail to start. Alternatively, if you install using two hyphens before the "install" parameter, the service will start just fine. For example, this will create a Windows service that cannot be started: This will create a Windows service that CAN be started (notice the two hyphens before "install"): |
| Comments |
| Comment by auto [ 06/May/12 ] |
|
Author: {u'login': u'tadmarshall', u'name': u'Tad Marshall', u'email': u'tad@10gen.com'}Message: Because we use allow_long_disguise in our style for |
| Comment by Tad Marshall [ 31/Jan/12 ] |
|
It's true. Apparently, the -install switch is "recognized" as the --install switch when checking to see if we should install the service, but is "not recognized" by the code that would change it to --service. So, we set up the service's command line including the bogus -install switch and not including the --service switch that would make it work correctly. |