MongoDB社区版3.6频繁崩溃求助：Win10本地启动数分钟即停止

Hey Sean, sorry to hear you're stuck with this frustrating MongoDB crash issue on your local Windows 10 setup—especially since your AWS Ubuntu production instance is running smoothly. Let's walk through targeted troubleshooting steps tailored to your scenario:

First, pull up MongoDB's log file—it’ll tell you exactly why the process is dying. By default, it’s located at C:\Program Files\MongoDB\Server\3.6\log\mongod.log (unless you changed the path in your config).

• Scan for ERROR or FATAL entries right around the timestamp when the service stops. Common culprits here include:
  • Low disk space on the drive hosting your MongoDB data/logs
  • Permission issues preventing the service from writing to data or log directories
  • Unexpected termination triggers (like Windows killing the process to free up resources)

Open Task Manager (Ctrl+Shift+Esc) and keep an eye on mongod.exe before it crashes:

• Memory: MongoDB 3.6 is memory-intensive. If your Windows machine is short on RAM, the OS might terminate the process automatically. Try closing other heavy apps, or adjust the wiredTigerCacheSizeGB setting in mongod.cfg to cap memory usage (set it to roughly half your available RAM for starters).
• CPU: Spiking CPU could mean a background process is conflicting with MongoDB, or a corrupted collection is causing an infinite loop.

• Service Permissions: Open services.msc, find the MongoDB service, and check its properties. Ensure it’s running under an account with write access to the data and log directories (avoid Local System if possible—use a local admin or the account you installed MongoDB with).
• Config File Checks: Open mongod.cfg (usually in C:\Program Files\MongoDB\Server\3.6\bin) and double-check:
  • dbPath points to a valid, writable directory
  • logPath is correctly set and the directory exists
  • No experimental features or custom plugins are enabled (these can cause instability on older MongoDB versions)

• Antivirus/Firewall: Some antivirus tools flag mongod.exe as suspicious and terminate it. Add exceptions for MongoDB’s bin, data, and log directories in your antivirus software.
• Windows Updates: Recent Windows 10 patches might break compatibility with older MongoDB versions (3.6 is from 2018, after all). Try rolling back any recent updates if you can, or consider upgrading to a newer supported version (if your workflow allows it).
• Port Conflicts: Run netstat -ano | findstr :27017 in Command Prompt to check if another process is using MongoDB’s default port. If so, either kill the conflicting process or change MongoDB’s port in mongod.cfg.

Corrupted collections or indexes often cause crashes. Test with a fresh setup:

1. Stop the MongoDB service
2. Rename your existing dbPath directory (e.g., data → data_old)
3. Create a new empty data directory in the same location
4. Start the service. If it stays running, you’ll need to restore from a backup or repair the old database with mongod --repair

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