-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Sharding
-
None
-
ALL
When Mongo-Orchestration tries to start a sharded cluster in Evergreen with a recent nightly build, mongos crashes:
2016-03-10T22:04:12.641+0000 I CONTROL [main] ** NOTE: This is a development version (3.3.2-133-g03eb477) of MongoDB. 2016-03-10T22:04:12.641+0000 I CONTROL [main] ** Not recommended for production. 2016-03-10T22:04:12.641+0000 I CONTROL [main] 2016-03-10T22:04:12.642+0000 I SHARDING [mongosMain] MongoS version 3.3.2-133-g03eb477 starting: pid=9134 port=27017 64-bit host=ip-10-230-205-141.ec2.internal (--help for usage) 2016-03-10T22:04:12.642+0000 I CONTROL [mongosMain] db version v3.3.2-133-g03eb477 2016-03-10T22:04:12.642+0000 I CONTROL [mongosMain] git version: 03eb4777de6cc9bade4041190b837b3c31a88e34 2016-03-10T22:04:12.642+0000 I CONTROL [mongosMain] allocator: system 2016-03-10T22:04:12.642+0000 I CONTROL [mongosMain] modules: none 2016-03-10T22:04:12.642+0000 I CONTROL [mongosMain] build environment: 2016-03-10T22:04:12.642+0000 I CONTROL [mongosMain] distarch: x86_64 2016-03-10T22:04:12.642+0000 I CONTROL [mongosMain] target_arch: x86_64 2016-03-10T22:04:12.642+0000 I CONTROL [mongosMain] options: { config: "/data/db/mongo-tbqXFu", net: { port: 27017 }, setParameter: { enableTestCommands: "1" }, sharding: { configDB: "localhost:27117,localhost:27118,localhost:27119" }, systemLog: { destination: "file", path: "/data/db/mongo-PawruQ/mongos.log" } } 2016-03-10T22:04:12.642+0000 E SHARDING [mongosMain] Error initializing sharding system: UnsupportedFormat: SYNC config server connection string is not allowed. 2016-03-10T22:04:12.642+0000 F - [mongosMain] Invalid access at address: 0xc 2016-03-10T22:04:12.643+0000 F - [mongosMain] Got signal: 11 (Segmentation Fault).
- duplicates
-
SERVER-22996 mongos (nightly build) segfault with invalid config option
- Closed