[SERVER-38269] Failed to upgrade to MongoDB 4.0.4 on Windows Created: 27/Nov/18 Updated: 03/Dec/18 Resolved: 29/Nov/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Upgrade/Downgrade |
| Affects Version/s: | 4.0.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Itzhak Kagan | Assignee: | Danny Hatcher (Inactive) |
| Resolution: | Done | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | ALL |
| Participants: |
| Description |
|
Base line: There are two servers (ServerOne, ServerTwo) with the following configuration: Each server has a replica set that comprise two data members + arbiter (Rep1 for ServerOne and Rep2 for ServerTwo) Schema: ServerOne win services: ServerTwo win services: Goal: Steps: Step one: We upgraded all replica sets to version 3.6.8 and set the FCV to 3.6 rs-status-result.txt Attached files: Rep2 on ServerTwo: Rep3 on ServerOne + ServerTwo: Result of rs.status() on replica set three:
Thanks, Itzik |
| Comments |
| Comment by Danny Hatcher (Inactive) [ 03/Dec/18 ] | |
|
Hello Itzik, I'm glad to hear that you were able to resolve your issue. Please note that per our documentation, if your clusterFile is identical to your PEMKeyFile you can omit the clusterFile setting as x509 will default to using the PEMKeyFile. Thank you, Danny | |
| Comment by Itzhak Kagan [ 03/Dec/18 ] | |
|
OK, I understood my mistake. I thought that the "clusterFile" on all config files should be the same, and it happen not to be so! When I change the name of the "clusterFile" to be the same as the name of the "PEMKeyFile" it start working.
Thanks, Itzik | |
| Comment by Itzhak Kagan [ 30/Nov/18 ] | |
|
security:
The configuration of ServerTwo also uses a PEMKeyFile and a clusterFile respectively. That is why on a replica set that comprises tow computers I have different .pem files. Only when the replica set spans over two or more computers we have encountered that error. I will appreciate if you can test the case where the replica set comprises of at least two computers. Thanks, Itzik | |
| Comment by Danny Hatcher (Inactive) [ 30/Nov/18 ] | |
|
Hello Itzhak, I have not been able to reproduce your issue locally and there are no known bugs in regards to x509 support on 4.0. I do notice that you have two different PEM keyfiles listed in the Rep3Server2 config file while all the other servers have only one keyfile listed. Perhaps that is your issue? | |
| Comment by Itzhak Kagan [ 30/Nov/18 ] | |
|
Hi Daniel This Windows error does not occur when MongoDB 3.4.6 and 3.6.8 versions are running. I'm not saying that this is a MongoDB error, but maybe some change in the 4.0.x version is dealing with some X509 issue that the earlier versions did not. Maybe you can give me a hint of that? Thanks, Itzik | |
| Comment by Danny Hatcher (Inactive) [ 29/Nov/18 ] | |
|
Hello Itzhak,
This error message is triggered by Windows and not MongoDB. Unfortunately, I am not sure what is causing it. Please follow up with your Windows admins as they would be the best people to troubleshoot this Windows issue. Thank you, Danny |