MongoDB副本集与反向代理配置问题及副本集环境变量咨询

Let's break down each of your issues and walk through solutions step by step—these are all common hurdles, so we'll get your project running smoothly in no time:

1. Fixing the "Port 3000 Already in Use" Error #

This almost always stems from a leftover Node.js process that didn't shut down properly. Here's how to resolve it:

• Locate the process hogging port 3000: Run one of these commands to get the process ID (PID):

  lsof -i :3000
  # If lsof isn't installed, use this instead:
  netstat -tulpn | grep 3000
  

• Kill the stuck process: Replace <PID> with the number you retrieved from the command above:

  kill -9 <PID>
  

• Prevent future occurrences: Add a cleanup script to your package.json to auto-kill old processes before starting the app:

  "scripts": {
    "start": "pkill -f 'node your-app-entry.js' || true && node your-app-entry.js"
  }
  

  Alternatively, you can change your Node app's listening port (e.g., to 3001) and update your Nginx proxy config to point to the new port.

2. Access /posts Without Typing It in the URL #

You can handle this with a simple Nginx configuration tweak. Choose one of these options based on your needs:

Option 1: Redirect root URL to /posts (URL will update to /posts) #

This sends users to the /posts path when they visit your root domain:

server {
    listen 80;
    server_name your-domain.com; # Replace with your server IP/domain

    location / {
        rewrite ^/$ /posts permanent; # 301 permanent redirect
    }

    location /posts {
        proxy_pass http://localhost:3000;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
    }
}

Option 2: Serve /posts content at the root (URL stays at /) #

If you want the root path to display /posts content without changing the URL, use this:

server {
    listen 80;
    server_name your-domain.com;

    location / {
        proxy_pass http://localhost:3000/posts;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
    }

    # Keep this block if you still want direct access to /posts
    location /posts {
        proxy_pass http://localhost:3000;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
    }
}

After editing, reload Nginx to apply changes: sudo systemctl reload nginx

3. Configuring MongoDB Replica Set in an Environment Variable #

The key here is using the correct replica set connection string format, which includes all nodes and a mandatory replicaSet parameter. Here's how to set it up:

• Set the environment variable: Replace rs0 with your replica set name, and add your other node IPs:

  export MONGODB_URI="mongodb://10.0.1.100:27017,10.0.1.101:27017,10.0.1.102:27017/posts?replicaSet=rs0"
  

• Critical pre-requisites:
  1. Enable replication on every mongod instance in your set. Update each mongod.conf to include:

     replication:
       replSetName: "rs0" # Must match the name in your connection string
     

  2. Restart each mongod instance: sudo systemctl restart mongod
  3. Initialize the replica set (run this once on your primary node via the mongo shell):

     rs.initiate()
     // Add the other nodes one by one:
     rs.add("10.0.1.101:27017")
     rs.add("10.0.1.102:27017")
     

• Verify: Your Node app should now connect to the replica set using the environment variable. If you hit errors, double-check that all nodes are reachable from your app server and the replica set name matches exactly.

Quick mongod.conf Sanity Check #

Ensure your template variables rendered correctly. The final net section in /etc/mongod.conf should look like this:

net:
  port: 27017
  bindIp: 0.0.0.0

内容的提问来源于stack exchange，提问作者Nayden Van