[SERVER-18837] Window Service doesnot start Created: 05/Jun/15 Updated: 18/Jun/15 Resolved: 18/Jun/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin |
| Affects Version/s: | 3.0.0, 3.0.1, 3.0.2, 3.0.3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Sharat M R | Assignee: | Mark Benvenuto |
| Resolution: | Done | Votes: | 0 |
| Labels: | server, service, windows | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Window 7 64bit |
||
| Operating System: | Windows |
| Steps To Reproduce: | 1. Install mongod as a service in window with any config. |
| Participants: |
| Description |
|
After install mongod as a service in Window 7 64bit, when trying to start the service it fails to start. This problem starting coming in the 3.x update. Things already done for resolving the issue:-
|
| Comments |
| Comment by Ramon Fernandez Marina [ 18/Jun/15 ] | |||||||||||||||||||||||||||
|
A service run from the CLI will run as the logged in user, whereas when run as a service it will run under the LocalSystem account. While the latter has extensive privileges, if your user has admin access it is possible to configure permissions/ACLs such that the user has all the right permissions but the LocalSystem user doesn't. We have not been able to reproduce this on our end. You can try using different, new directories for dbpath and logpath created from Explorer (as if you're using Cygwin permissions can get messed up), and examining carefully the permissions/ACLs of all the directories involved. Since we're not able to find evidence of a bug in the SERVER I'm closing this ticket, as the SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag, where your question will reach a larger audience. A question like this involving more discussion would be best posted on the mongodb-user group. Regards, | |||||||||||||||||||||||||||
| Comment by Sharat M R [ 05/Jun/15 ] | |||||||||||||||||||||||||||
|
I still don't understand about the permission stuff? The server runs fine when run from the CLI. How does the permission effect the running of mongod Server when run as a service and though CLI? | |||||||||||||||||||||||||||
| Comment by Sharat M R [ 05/Jun/15 ] | |||||||||||||||||||||||||||
|
The output of
is
I did the command you suggested, the result is the same the service does not start here is the output of sc qc after the service installation.
| |||||||||||||||||||||||||||
| Comment by Mark Benvenuto [ 05/Jun/15 ] | |||||||||||||||||||||||||||
|
To help me understand the issue, please run the follow as administrator.
If there are no logs, then MongoDB likely cannot open the log file due to a permission issue. Also, try installing the service as
| |||||||||||||||||||||||||||
| Comment by Sharat M R [ 05/Jun/15 ] | |||||||||||||||||||||||||||
|
It fails on step number 5 net start Mongodb Is there any drastic change from 2.x to 3.x in windows service? What kind of permission would be required for windows service? For Note i am running all operation under a user with admin access | |||||||||||||||||||||||||||
| Comment by Ramon Fernandez Marina [ 05/Jun/15 ] | |||||||||||||||||||||||||||
|
cosmosgenius, can you please check the instructions for installing MongoDB on Windows and pinpoint at which step things fail to work? I'm guessing a permission issue, but it could also be using the wrong syntax; have you tried using "--dbpath ..." as opposed to "--dbpath=..."? That is, replacing the "=" above with " "? |