[SERVER-5064] mongos can't start when one config server is down. only with keyFile options Created: 24/Feb/12  Updated: 11/Jul/16  Resolved: 07/Aug/12

Status: Closed
Project: Core Server
Component/s: Security, Sharding
Affects Version/s: 2.0.2
Fix Version/s: 2.2.0-rc1

Type: Bug Priority: Major - P3
Reporter: peanutgyz Assignee: Mathias Stearn
Resolution: Done Votes: 1
Labels: authentication, configserver, mongos
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

linux mongodb 2.0.2


Issue Links:
Related
related to SERVER-6665 authentication for a replica set requ... Closed
is related to SERVER-6178 Cannot use mongos if subset of config... Closed
is related to SERVER-6667 --traceExceptions command line parameter Closed
Operating System: ALL
Participants:

 Description   

setting up 3 config server, when any of config server is down,
start mongos will get 9001 socket exception [6] server [xxxx:xxxx]

config server, shard server and mongos all start with --keyFile option.

when no keyFile, mongos works well



 Comments   
Comment by auto [ 09/Feb/13 ]

Author:

{u'date': u'2013-02-09T20:37:32Z', u'name': u'Tad Marshall', u'email': u'tad@10gen.com'}

Message: SERVER-5064 Improve error reporting in test

Adjust code to catch exception during query attempt so that assert
runs and prints stack trace, display message on assertion failure.
Branch: master
https://github.com/mongodb/mongo/commit/2e8ea804a7879babfbb542d8dad07005c4f1ff44

Comment by auto [ 07/Aug/12 ]

Author:

{u'date': u'2012-08-07T10:17:12-07:00', u'email': u'mathias@10gen.com', u'name': u'Mathias Stearn'}

Message: SERVER-5064 don't return false in auth unless all config servers are down

written by greg
Branch: master
https://github.com/mongodb/mongo/commit/439d47d34addf072a9d50444c2a4fc92d41badc9

Comment by peanutgyz [ 24/Feb/12 ]


start mongos get socket exception , then quit.

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