config and shard cluster has been launched successfully, and go through the time mongos -f mongos.conf start mongos routing error, in fact, can not be considered an error Well, that has been waiting for
Child Process fork to the About, an until Server IS READY Waiting for Connections.
forked Process: 3713
may encounter this problem for several reasons, for a long time I Baidu is not resolved, it is a good record
after viewing the log and found that there is a line:
2019 -08-25T23: 32: 20.203 + 0800 W NETWORK [mongosMain] no primary detected for set config
probably means, no config cluster PRIMARY replica set, then remembered my config shard clusters and clusters are not initialized, you can start after the adoption of the configuration a.