[SERVER-27817] mongod does not response after closing and starting windows service versions 3.4.0,3.4.1 Created: 26/Jan/17 Updated: 24/Aug/17 Resolved: 17/Jul/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin |
| Affects Version/s: | 3.4.0, 3.4.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Itzhak Kagan | Assignee: | Mark Benvenuto |
| Resolution: | Cannot Reproduce | Votes: | 2 |
| Labels: | windows | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | ALL |
| Steps To Reproduce: | start a 3.4.1 mongod windows service. In order to successfully connect you will have to stop the service and restart it again |
| Participants: |
| Description |
|
On versions 3.4.0 and 3.4.1 Needless to say that that situation prevents us from deploying our 3.4 solution. |
| Comments |
| Comment by Ramon Fernandez Marina [ 24/Aug/17 ] | |||||||||||||||||||||||||||||
|
Author: {'username': u'hptabster', 'name': u'Jonathan Abrahams', 'email': u'jonathan@mongodb.com'}Message: | |||||||||||||||||||||||||||||
| Comment by Ramon Fernandez Marina [ 17/Jul/17 ] | |||||||||||||||||||||||||||||
|
itzikkg, unfortunately we have not been able to reproduce this issue, so I'm going to close this ticket. I'd recommend upgrading to the latest 3.4 (3.4.6 at the time of this writing) and if you're still experiencing issues open a new ticket. Thanks, | |||||||||||||||||||||||||||||
| Comment by Mark Benvenuto [ 19/Jun/17 ] | |||||||||||||||||||||||||||||
|
I have not been able to repro this. I used 3.4.2 SSL version on Windows 10 (16053.413) and Windows 2012 (6.2 Build 9200). On reboot of the machine, I can connect from a separate machine to mongod on the Windows machine. I setup the firewall to allow connections through to tcp port 27017. | |||||||||||||||||||||||||||||
| Comment by Itzhak Kagan [ 26/Mar/17 ] | |||||||||||||||||||||||||||||
|
I checked the nightly build version v3.4.3-rc2. From My checks the same behavior happens in 3.2.12. Thanks, | |||||||||||||||||||||||||||||
| Comment by Itzhak Kagan [ 14/Mar/17 ] | |||||||||||||||||||||||||||||
|
I took the nightly build version v3.4.3-rc1. | |||||||||||||||||||||||||||||
| Comment by Itzhak Kagan [ 12/Mar/17 ] | |||||||||||||||||||||||||||||
|
I took the nightly build version v3.4.3-rc0-3-g6ce1c2d. I did succeeded to upgrade the databases from 3.2.11 to that version. I stopped the the mongod service and started it couple of times and all was good. Then I did shut down my machine and started it back again. At that point I tried to run mongo.exe and it failed (the process was up). The message is: D:\MongoDb\bin_32to34\mongo.exe --host <machine name> --port 47017 -u <user> -p <password> --a uthenticationDatabase admin I attached three log files for you to see. Thanks, | |||||||||||||||||||||||||||||
| Comment by Kelsey Schubert [ 08/Mar/17 ] | |||||||||||||||||||||||||||||
|
Hi itzikkg,
Thank you, | |||||||||||||||||||||||||||||
| Comment by Itzhak Kagan [ 05/Feb/17 ] | |||||||||||||||||||||||||||||
|
I was too happy with the previous comment. Remember that you should upgrade a 3.2 server to 3.4 server with the command: ) Please check this scenario. Thanks, | |||||||||||||||||||||||||||||
| Comment by Itzhak Kagan [ 05/Feb/17 ] | |||||||||||||||||||||||||||||
|
In version 3.4.2 this is no longer occurs. Thanks, | |||||||||||||||||||||||||||||
| Comment by Itzhak Kagan [ 01/Feb/17 ] | |||||||||||||||||||||||||||||
|
The server was a 3.2 server and was upgraded to 3.4 with the command: db.adminCommand( { setFeatureCompatibilityVersion: "3.4" }) Log of mongod procces is attached | |||||||||||||||||||||||||||||
| Comment by Kelsey Schubert [ 30/Jan/17 ] | |||||||||||||||||||||||||||||
|
Hi itzikkg, I haven't been able to reproduce the the behavior you describe. From the command prompt. I execute the following:
So we can continue to investigate, would you please provide the mongod logs as well as a step by step guide to reproduce this issue? Thank you for your help, | |||||||||||||||||||||||||||||
| Comment by Itzhak Kagan [ 26/Jan/17 ] | |||||||||||||||||||||||||||||
|
The workaround might be temporarily good for development environment. Would you go with that workaround to production? The answer is definitely NO! | |||||||||||||||||||||||||||||
| Comment by Kelsey Schubert [ 26/Jan/17 ] | |||||||||||||||||||||||||||||
|
Hi itzikkg, Thank you for the report – we're investigating. Since you've identified a workaround, I'm lowering the priority of this ticket. Kind regards, |