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

--sslPEMKeyFile and other ssl arguments require the full path when using --fork

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Minor - P4
    • Resolution: Fixed
    • 2.4.0-rc0
    • 2.5.3
    • Security
    • None
    • ALL

    Description

      The path to ssl certificates has to be a full path, where as other command line options are relative to where mongod is called from.

      eg my start mongod bash script:

      #!/bin/bash
      ./bin/mongod --dbpath=./data/single --fork --logpath=./logs/single --sslPEMKeyFile=./jstests/libs/server.pem --sslCAFile=./jstests/libs/ca.pem --sslCRLFile=./jstests/libs/crl.pem --sslOnNormalPorts --sslWeakCertificateValidation --smallfiles --noprealloc --nojournal

      Errors with ERROR: cannot read certificate file. When I supply the full path to the certificates it works but this is different to how dbpath and logpath work.

      Attachments

        Issue Links

          Activity

            People

              matt.dannenberg Matt Dannenberg
              ross@mongodb.com Ross Lawley
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: