[SERVER-62939] Starting up ESE with no KMIP server available leaves a backtrace Created: 24/Jan/22  Updated: 29/Oct/23  Resolved: 16/Jun/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.1.0-rc0, 6.0.8

Type: Bug Priority: Major - P3
Reporter: Shreyas Kalyan Assignee: Gabriel Marks
Resolution: Fixed Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Problem/Incident
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v6.0
Sprint: Security 2022-05-30, Security 2022-06-13, Security 2022-06-27
Participants:

 Description   

Starting up a mongod with parameters to speak to a KMIP server causes it to reach out to the server. When there is no available KMIP server, the mongod should fail gracefully. Instead, it leaves a stack trace, which is unclean.



 Comments   
Comment by Githook User [ 16/Jun/22 ]

Author:

{'name': 'Gabriel Marks', 'email': 'gabriel.marks@mongodb.com', 'username': 'marksg07'}

Message: SERVER-62939 Don't crash if KMIP server cannot be reached
Branch: master
https://github.com/10gen/mongo-enterprise-modules/commit/b0a7cbb8136be7c78661c3f6f08528568f3c0430

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