[SERVER-31711] Unable to connect to Sandbox cluster Created: 25/Oct/17  Updated: 07/Dec/17  Resolved: 10/Nov/17

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

Type: Bug Priority: Major - P3
Reporter: Gururaj Shetty Assignee: Mark Agarunov
Resolution: Incomplete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

Connection failed.

SERVER [cluster0-shard-00-02-iylpg.mongodb.net:27017] (Type: UNKNOWN)

_/ Connection error (MongoSocketReadException): Prematurely reached end of stream

SERVER [cluster0-shard-00-00-iylpg.mongodb.net:27017] (Type: REPLICA_SET_SECONDARY) CONNECTED

SERVER [cluster0-shard-00-01-iylpg.mongodb.net:27017] (Type: REPLICA_SET_SECONDARY) CONNECTED

Details:
Timed out after 30000 ms while waiting for a server that matches ReadPreferenceServerSelector

{readPreference=primary}

. Client view of cluster state is {type=REPLICA_SET, servers=[{address=cluster0-shard-00-02-iylpg.mongodb.net:27017, type=UNKNOWN, state=CONNECTING, exception={com.mongodb.MongoSocketReadException: Prematurely reached end of stream}},

{address=cluster0-shard-00-00-iylpg.mongodb.net:27017, type=REPLICA_SET_SECONDARY, roundTripTime=271.7 ms, state=CONNECTED}

,

{address=cluster0-shard-00-01-iylpg.mongodb.net:27017, type=REPLICA_SET_SECONDARY, roundTripTime=249.6 ms, state=CONNECTED}

]



 Comments   
Comment by Mark Agarunov [ 10/Nov/17 ]

Hello gururaj.shetty@legaldesk.com,

We haven’t heard back from you for some time, so I’m going to mark this ticket as resolved. If this is still an issue for you, please provide additional information and we will reopen the ticket.

Thanks,
Mark

Comment by Mark Agarunov [ 27/Oct/17 ]

Hello gururaj.shetty@legaldesk.com,

Thank you for the report. To get a better idea of what may be causing this behavior, could you please provide the complete log files from all affected/involved mongod nodes? This should give a better insight into the underlying cause.

Thanks,
Mark

Generated at Thu Feb 08 04:27:58 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.