[SERVER-14009] MongoDB running as network service does not respond to net start Created: 20/May/14 Updated: 10/Dec/14 Resolved: 07/Aug/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin |
| Affects Version/s: | 2.6.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kevin Groat | Assignee: | Mark Benvenuto |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Windows 8.1 Pro |
||
| Attachments: |
|
| Operating System: | Windows |
| Steps To Reproduce: | 1) Install MongoDB as a windows service using the following command: 2) Try to start service using the following command: |
| Participants: |
| Description |
|
After installing the MongoDB windows service, I checked the logfile specified in the config file, and it was being logged to correctly, but when I try to start the network service, I get the following error: If it helps, I had a much older version installed (I believe 2.1.x) for a while, and attempted to upgrade to 2.6.0 a few weeks back, but downgraded to 2.4.10 due to issue I attached the config file that I'm attempting to use when the issue arises. |
| Comments |
| Comment by Thomas Rueckstiess [ 07/Aug/14 ] |
|
Hi Kevin, Thanks for letting us know. This looks like it resolved the issue for you. I'm closing this ticket. Regards, |
| Comment by Kevin Groat [ 24/Jul/14 ] |
|
It looks like using absolute paths did the trick, and the service appears to be running as expected. |
| Comment by Ramon Fernandez Marina [ 24/Jul/14 ] |
|
kgroat09, have you tried using absolute paths in the config file? Does the issue reproduce with absolute paths? |