Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-54752

Version 4.4.4 fails to validate existing certificateKeyFile, refuses to start

    • Type: Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 4.4.4
    • Component/s: None
    • Labels:
      None
    • ALL
    • Security 2021-03-22, Security 2021-04-05, Security 2021-04-19, Security 2021-05-03, Security 2021-05-17, Security 2021-05-31, Security 2021-06-14, Security 2021-06-28, Security 2021-07-12

      Hello, I am running MongoDB under CentOS 7, installed from the official mongodb-org-4.4 yum repo.

      I ran yum today and it updated mongodb-org.x86_64 0:4.4.3-1.el7 to mongodb-org.x86_64 0:4.4.4-1.el7.

      Mongod then failed to restart. It gave me the following startup error, indicating a problem with the existing certificateKeyFile that I know for certain is valid.

      Downgrading MongoDB back to mongodb-org.x86_64 0:4.4.3-1.el7 got things working again.

      Here are the error messages from the log:

      {"t":\{"$date":"2021-02-24T22:03:15.822+11:00"}

      ,"s":"I", "c":"CONTROL", "id":20698, "ctx":"main","msg":"***** SERVER RESTARTED *****"}

      {"t":\{"$date":"2021-02-24T22:03:15.825+11:00"}

      ,"s":"E", "c":"NETWORK", "id":23252, "ctx":"main","msg":"Cannot use PEM key file","attr":{"keyFile":"/etc/mongod.pem","error":"error:0B080074:x509 certificate routines:X509_check_private_key:key values mismatch"}}

      {"t":\{"$date":"2021-02-24T22:03:15.826+11:00"}

      ,"s":"F", "c":"CONTROL", "id":20574, "ctx":"main","msg":"Error during global initialization","attr":{"error":

      {"code":140,"codeName":"InvalidSSLConfiguration","errmsg":"Can not set up PEM key file."}

      }}

            Assignee:
            varun.ravichandran@mongodb.com Varun Ravichandran
            Reporter:
            vlasky@remotelaboratory.com Vlad Lasky
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: