When deploying a MongoDB cluster, rs.initiate (config) initializes the configuration times wrong

Problem: MongoDB configures the replica set file to initialize the times wrong:

"OK": 0, "errmsg": "Replsetinitiate quorum check failed because not all proposed set members responded affirmatively:17 2.24.240.103:28001 failed with no route to host, 172.24.240.104:28001 failed with no route to host, 172.24.240.105:28001 F Ailed with No route to host ",
"Code": 74,

"codename": "Nodenotfound"

Solution:

Since the MongoDB distributed replica set is initialized with calls between the individual nodes, the firewall on each node needs to be shut down.

Method One: The command is: # service iptables Stop (immediate effect, temporarily shut down the firewall, the firewall will automatically open after the system)

Method Two: # Chkconfig iptables off (takes effect after reboot, permanently shuts down the firewall)