[SERVER-15475] Feedback on MongoDB 2.6 Windows zip - two issues Created: 01/Oct/14 Updated: 03/Dec/14 Resolved: 03/Dec/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Packaging |
| Affects Version/s: | 2.6.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Asko Kauppi | Assignee: | Ramon Fernandez Marina |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
Two things we have noticed, installing mongodb-win32-x86_64-2008plus-2.6.4.zip to Windows 8.1 Professional.
I would like you to document this, and if possible, make sure services would not even attempt to start, or they would give appropriate error messages. It may be a Windows issue, though, outside of your reach.
I know that it works for pretty much anything. Then why the name? You could simply call these "win64-2.6.4", couldn't you? Our customers need to install MongoDB by themselves, so it's not just me, it's what we place to instructions for them. My apologies for pushing two into one (bad bug management habits, I know). Just wanted you to be aware of these. |
| Comments |
| Comment by Asko Kauppi [ 13/Nov/14 ] | |||||||||||||||||
|
We're revising the said installation instructions within Nov/Dec. It's not a major issue from our side - using configuration files the problem does not occur so we'll simply go such way. The naming reasoning makes sense from a technical point of view, but if you look at it from a "which is the right package for my ... [Windows 8.1 Pro|...]" I think the benefits of current naming scheme are less obvious. Sorry but I think I won't be able to fill more data on the reported issues. Busy... | |||||||||||||||||
| Comment by Ramon Fernandez Marina [ 12/Nov/14 ] | |||||||||||||||||
|
akauppi, here's an explanation of the package naming:
As for the issue with long paths, are you still investigating it? Have you been able to try using a config file to see if the issue still reproduces? | |||||||||||||||||
| Comment by Asko Kauppi [ 01/Oct/14 ] | |||||||||||||||||
|
Hi, Ramon I'll need to look into this a bit more in our end. Maybe I find a reason that wasn't MongoDB after all. Here are the commands. I'm not using a config file but command line parameters, which probably makes the long path names issue worse by multiplying the paths. We probably must change our user instructions to use a config file and all will be great. Anyways, in case you wish to see if you can reproduce it. `mongodb-helper.cmd` is a small batch we did, irrelevant since the actual Windows service commands are visible here. A project name has been fuzzified, since it's not public, yet.
More help is available by typing NET HELPMSG 2186.
The log:
But the error happened with the `net start MongoDB`, not the installation (which presumably I had just run multiple times). I'll try to come back to this within a week. | |||||||||||||||||
| Comment by Ramon Fernandez Marina [ 01/Oct/14 ] | |||||||||||||||||
|
Thanks for your report akauppi. Can you please send us the windows path you used, the MongoDB logs when the service startup failure happen, and any OS logs you may have? Thanks, |