[SERVER-40918] Shard member sometimes backtraces when starting up a sharded cluster with TLS Created: 30/Apr/19  Updated: 03/Mar/20

Status: Open
Project: Core Server
Component/s: Security
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Timothy Olsen (Inactive) Assignee: Timothy Olsen (Inactive)
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File config1.log     Text File config2.log     Text File config3.log     Text File mongos1.log     Text File mongos2.log     Text File rs1_1.log     Text File rs1_2.log     Text File rs1_3.log    
Operating System: ALL
Steps To Reproduce:

1. Start up a sharded cluster with 3 config servers, 2 mongoses, and 1 shard with 3 members on OS X
2. One of the shard members might backtrace. Doesn't happen everytime

Sprint: Security 2019-05-20, Security 2019-06-03, Security 2019-07-01, Security 2019-07-15, Security 2019-07-29, Security 2019-08-12, Security 2019-08-26, Security 2019-09-09
Participants:

 Description   

A shard member sometimes backtraces when starting up a sharded cluster with TLS. See attached log files. The backtace is in rs1_2.log. This is with MongoDB 4.1.10 on OS X



 Comments   
Comment by Timothy Olsen (Inactive) [ 04/Feb/20 ]

sure thing

Comment by Timothy Olsen (Inactive) [ 19/Nov/19 ]

Hi kelly.lewis .  I don't think I'll be able to look at this for a while.  

Comment by Mark Benvenuto [ 24/Jul/19 ]

Please attach a core dump so that we may continue our investigation. We have not seen this issue in our local testing.

Also, what version of macOS are you running on?

Comment by Timothy Olsen (Inactive) [ 16/May/19 ]

I do not necessarily believe that this problem does not occur with older style arguments. I think that's a misunderstanding.

The automation agent will first attempt an SSL connection if it has been given a CA file. If that fails, it will try to connect without SSL. That said, there could be an old Go driver client hanging around that first connected without SSL before SSL was enabled on the mongod. In that case, that client will continue to try to connect without SSL.

Generated at Thu Feb 08 04:56:19 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.