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

When shell fails to connect due to not having ssl, message is not informative

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Shell, Usability
    • Labels:
      None
    • Operating System:
      ALL

      Description

      Steps to reproduce - message should be informative

      ubuntu@ip-10-36-133-56:~/mongodb-linux-x86_64-subscription-ubuntu1104-2.4.0-rc0$ ./bin/mongod --dbpath ./data/ --sslOnNormalPorts --sslPEMKeyFile=smoke.pem

      ubuntu@ip-10-36-133-56:~/mongodb-linux-x86_64-subscription-ubuntu1104-2.4.0-rc0$ ./bin/mongo
      MongoDB shell version: 2.4.0-rc0
      connecting to: test
      Fri Feb 22 10:49:46.812 Socket recv() errno:104 Connection reset by peer 127.0.0.1:27017
      Fri Feb 22 10:49:46.813 SocketException: remote: 127.0.0.1:27017 error: 9001 socket exception [1] server [127.0.0.1:27017]
      Fri Feb 22 10:49:46.813 DBClientCursor::init call() failed
      Fri Feb 22 10:49:46.814 Error: DBClientBase::findN: transport error: 127.0.0.1:27017 ns: admin.$cmd query:

      { whatsmyuri: 1 }

      src/mongo/shell/mongo.js:112
      exception: connect failed

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              andreas.nilsson Andreas Nilsson
              Reporter:
              gregor Gregor Macadam
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: