[SERVER-25280] mongos can not startup Created: 26/Jul/16  Updated: 26/Jul/16  Resolved: 26/Jul/16

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

Type: Question Priority: Major - P3
Reporter: yinruilin Assignee: Kelsey Schubert
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

CentOS-6.4


Participants:

 Description   

2016-07-26T17:34:09.176+0800 I CONTROL  [main] ***** SERVER RESTARTED *****
2016-07-26T17:34:09.181+0800 I CONTROL  [main] 
2016-07-26T17:34:09.181+0800 I CONTROL  [main] ** WARNING: Insecure configuration, access control is not enabled and no --bind_ip has been specified.
2016-07-26T17:34:09.181+0800 I CONTROL  [main] **          Read and write access to data and configuration is unrestricted, 
2016-07-26T17:34:09.181+0800 I CONTROL  [main] **          and the server listens on all available network interfaces.
2016-07-26T17:34:09.181+0800 I CONTROL  [main] ** WARNING: You are running this process as the root user, which is not recommended.
2016-07-26T17:34:09.181+0800 I CONTROL  [main] 
2016-07-26T17:34:09.181+0800 I SHARDING [mongosMain] MongoS version 3.2.5 starting: pid=12944 port=6080 64-bit host=node14 (--help for usage)
2016-07-26T17:34:09.181+0800 I CONTROL  [mongosMain] db version v3.2.5
2016-07-26T17:34:09.181+0800 I CONTROL  [mongosMain] git version: 34e65e5383f7ea1726332cb175b73077ec4a1b02
2016-07-26T17:34:09.181+0800 I CONTROL  [mongosMain] allocator: tcmalloc
2016-07-26T17:34:09.181+0800 I CONTROL  [mongosMain] modules: none
2016-07-26T17:34:09.181+0800 I CONTROL  [mongosMain] build environment:
2016-07-26T17:34:09.181+0800 I CONTROL  [mongosMain]     distarch: x86_64
2016-07-26T17:34:09.181+0800 I CONTROL  [mongosMain]     target_arch: x86_64
2016-07-26T17:34:09.181+0800 I CONTROL  [mongosMain] options: { net: { port: 6080 }, processManagement: { fork: true }, sharding: { configDB: "192.168.2.10:6072,192.168.2.11:6072,192.168.2.13:6072" }, systemLog: { destination: "file", logAppend: true, path: "/home/mongo/MongoLog/mongos3.log" } }
2016-07-26T17:34:09.181+0800 I SHARDING [mongosMain] Updating config server connection string to: 192.168.2.10:6072,192.168.2.11:6072,192.168.2.13:6072
2016-07-26T17:34:09.189+0800 W SHARDING [mongosMain] config servers 192.168.2.10:6072 and 192.168.2.11:6072 differ
2016-07-26T17:34:09.190+0800 W SHARDING [mongosMain] config servers 192.168.2.10:6072 and 192.168.2.11:6072 differ
2016-07-26T17:34:09.191+0800 W SHARDING [mongosMain] config servers 192.168.2.10:6072 and 192.168.2.11:6072 differ
2016-07-26T17:34:09.192+0800 W SHARDING [mongosMain] config servers 192.168.2.10:6072 and 192.168.2.11:6072 differ
2016-07-26T17:34:09.192+0800 E SHARDING [mongosMain] Error initializing sharding system: ConfigServersInconsistent: hash from 192.168.2.10:6072: { chunks: "d41d8cd98f00b204e9800998ecf8427e", shards: "d41d8cd98f00b204e9800998ecf8427e", version: "969ca8b71951e255a1915cf60f39de4b" } vs hash from 192.168.2.11:6072: { chunks: "d41d8cd98f00b204e9800998ecf8427e", shards: "f5b82160853acd8fb64e6b48c6880558", version: "04bc33949bc93519301706e4006a6488" }
2016-07-26T17:34:09.193+0800 I SHARDING [mongosMain] dbexit:  rc:5

How can I solve the problem



 Comments   
Comment by Kelsey Schubert [ 26/Jul/16 ]

Hi yinrui54,

This error message indicates that your config servers are not in sync. This issue requires manual intervention to resolve.

MongoDB 3.2 introduces Config Servers as Replica Sets, which prevents this scenario. You can upgrade with downtime via this procedure. For the upgrade process to work you must get your config servers in sync first though.

Please note that the SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag, where your question will reach a larger audience. See also our Technical Support page for additional support resources.

Kind regards,
Thomas

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