[SERVER-8669] When shell fails to connect due to not having ssl, message is not informative Created: 22/Feb/13  Updated: 10/Dec/14  Resolved: 09/Jan/14

Status: Closed
Project: Core Server
Component/s: Shell, Usability
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Gregor Macadam Assignee: Andreas Nilsson
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
duplicates SERVER-11292 Connecting to ssl-encrypted mongod wi... Backlog
Operating System: ALL
Participants:

 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



 Comments   
Comment by Andreas Nilsson [ 09/Jan/14 ]

Closing this one since SERVER-11292 is more updated with the latest behavior.

Generated at Thu Feb 08 03:18:02 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.