配置replSet后MongoDB执行rs.initiate()报错，Rocket.chat安装受阻求助

Hey there, let's troubleshoot why your MongoDB replica set setup isn't working as expected. Here are the key steps to resolve the error you're seeing when running rs.initiate():

1. Double-Check Your mongod.conf Configuration #

First, confirm the replSet setting is correctly placed in your config file. For MongoDB 2.4.10, the ini-style config should have the line directly at the top level (not nested under any section):

replSet=001-rs

Make sure there are no typos (like misspelling replSet as replSetName—that's for newer MongoDB versions) and no extra quotes around the replica set name.

2. Verify MongoDB is Loading the Correct Config File #

Sometimes systemd services use a different config path than you expect. To check if your mongod.conf is being used:

• Run this command to see MongoDB's startup parameters:

  ps aux | grep mongod
  

• Look for a --config flag pointing to /etc/mongod.conf. If you don't see it, or if it points to another file (like /etc/mongodb.conf—note the missing 'd'), your changes aren't being applied.

3. Force the Replica Set Flag via Systemd Service #

If the config file isn't being picked up, modify the systemd service to explicitly pass the --replSet flag:

1. Open the service file in a text editor:

   sudo nano /lib/systemd/system/mongodb.service
   

2. Find the ExecStart line and append --replSet 001-rs to the end. It should look something like:

   ExecStart=/usr/bin/mongod --config /etc/mongod.conf --replSet 001-rs
   

3. Reload systemd to apply the changes:

   sudo systemctl daemon-reload
   

4. Restart MongoDB again:

   sudo systemctl restart mongodb
   

4. Confirm the Replica Set Config is Active #

Once MongoDB is restarted, open the mongo shell and run this command to verify the replSet flag is enabled:

db.adminCommand({getCmdLineOpts: 1})

Look for replSet: "001-rs" under the parsed section. If it's there, go ahead and run rs.initiate()—it should return a result with "ok": 1 now.

A quick side note: MongoDB 2.4 is quite outdated, and newer versions of Rocket.Chat might have better compatibility with more recent MongoDB releases (like 4.4+). If you run into further issues down the line, consider upgrading MongoDB if your environment allows it.

内容的提问来源于stack exchange，提问作者Hung Tran