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

Typo in error message

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.1.7
    • Affects Version/s: None
    • Component/s: None
    • Fully Compatible
    • ALL

      When initializing a replicaset through rs.initialize() using X509 certificate that doesn't match the hostname used an error is raised:

      2015-07-31T13:22:30.051-0700 I COMMAND  [conn8] initiate : no configuration specified. Using a default configuration for the set
      2015-07-31T13:22:30.051-0700 I COMMAND  [conn8] created this configuration for initiation : { _id: "RS", version: 1, members: [ { _id: 0, host: "infant:27017" } ] }
      2015-07-31T13:22:30.051-0700 I REPL     [conn8] replSetInitiate admin command received from client
      2015-07-31T13:22:30.052-0700 I NETWORK  [initandlisten] connection accepted from 127.0.0.1:60812 #9 (2 connections now open)
      2015-07-31T13:22:30.068-0700 E NETWORK  [conn8] The server certificate does not match the host name infant
      2015-07-31T13:22:30.068-0700 I NETWORK  [conn9] end connection 127.0.0.1:60812 (1 connection now open)
      2015-07-31T13:22:30.068-0700 W NETWORK  [conn8] could't check isSelf (infant:27017) socket exception [CONNECT_ERROR] for The server certificate does not match the host name infant
      2015-07-31T13:22:30.069-0700 E REPL     [conn8] replSet initiate got NodeNotFound No host described in new configuration 1 for replica set RS maps to this node while validating { _id: "RS", version: 1, members: [ { _id: 0, host: "infant:27017" } ] }
      2015-07-31T13:22:38.258-0700 I NETWORK  [conn8] end connection 127.0.0.1:41447 (0 connections now open)
      

      "could't check isSelf" should say "couldn't"

            Assignee:
            mark.benvenuto@mongodb.com Mark Benvenuto
            Reporter:
            bjori Hannes Magnusson
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: