MongoDB从3.4升级到4.4后无法以服务/后台方式启动求助

Hey there, let's tackle this MongoDB upgrade headache step by step. Jumping straight from 3.4 to 4.4 is a big leap, and those major version jumps almost always bring compatibility hiccups—let's unpack your issues one by one.

First, Understand the Exit Codes #

Let's start with what those status codes mean, since they're our biggest clues:

• Exit code 1 (systemd failure): Usually points to a config file error, permission mismatch, or systemd service misconfiguration.
• Exit code 100 (forked startup failure): This is MongoDB's way of saying it hit a critical data compatibility issue or invalid startup parameters.

1. Fix Data Compatibility (Root Cause of Exit Code 100) #

MongoDB doesn't support skipping major versions during upgrades. You have to follow a strict path: 3.4 → 3.6 → 4.0 → 4.2 → 4.4, and after each upgrade, you must set the Feature Compatibility Version (FCV) to match the new version before moving on. Skipping steps leaves your data in a format 4.4 can't read.

Verify the Issue #

Since you can start MongoDB directly with mongod --dbpath /var/lib/mongo, fire up the shell and run this command to check your current FCV:

db.adminCommand({ getParameter: 1, featureCompatibilityVersion: 1 })

If it returns "3.4", that's the problem—4.4 refuses to work with 3.4-era data.

Fix Steps (Backup First!) #

1. Roll back to MongoDB 3.4, start it up, and ensure FCV is set to 3.4:

   db.adminCommand({ setFeatureCompatibilityVersion: "3.4" })
   

2. Upgrade to 3.6, start it, and update FCV to 3.6:

   db.adminCommand({ setFeatureCompatibilityVersion: "3.6" })
   

3. Repeat this process for 4.0 (FCV 4.0) and 4.2 (FCV 4.2), then finally upgrade to 4.4 and set FCV to 4.4.

2. Troubleshoot Config File & Systemd Issues (Exit Code 1) #

Since direct startup works, your data directory is fine—so the problem is in your /etc/mongod.conf or systemd setup.

Check for Obsolete Config Parameters #

4.4 dropped support for some older settings. Common culprits:

• storage.engine: mmapv1: 4.4 no longer supports the MMAPv1 engine. If your config has this, replace it with WiredTiger (the default for newer versions):

  storage:
    engine: wiredTiger
  

• Outdated network settings: 4.0+ defaults to binding only 127.0.0.1. If your old config had vague or deprecated network settings, update it explicitly:

  net:
    bindIp: 127.0.0.1  # Or 0.0.0.0 if you need remote access
  

Check Permissions for Log & Data Directories #

Even if your data dir works, the log directory might have wrong permissions. Run these commands to verify:

# Check data directory permissions
ls -ld /var/lib/mongo
# Check log directory and file permissions
ls -ld /var/log/mongodb/
ls -l /var/log/mongodb/mongod.log

Make sure all these files/dirs are owned by the mongod user and group:

chown mongod:mongod /var/lib/mongo /var/log/mongodb/ -R

Debug Systemd in Detail #

To get the exact error behind the exit code 1, run this command to pull systemd's detailed logs:

journalctl -u mongod.service -xe

This will show you exactly where the startup failed—whether it's a config syntax error, missing binary path, or permission issue.

3. Fix Systemd Auto-Start & Background Run #

Once the compatibility and config issues are fixed, get systemd working properly:

1. Verify the systemd service file points to the correct 4.4 mongod binary:

   which mongod
   

   Ensure the path matches what's in /usr/lib/systemd/system/mongod.service under ExecStart.
2. Reload systemd to pick up any config changes:

   systemctl daemon-reload
   

3. Restart and enable auto-start:

   systemctl restart mongod
   systemctl enable mongod
   

Quick Priority Checklist #

1. Fix the FCV/version upgrade path first (this is the root of the exit code 100 issue).
2. Use systemd logs to pinpoint config or permission issues for exit code 1.
3. Verify all file permissions and service file paths match the 4.4 installation.

内容的提问来源于stack exchange，提问作者Marco Martin