Debugging and Troubleshooting MongoDB on CentOS, AlmaLinux, and RockyLinux

When MongoDB won't start on a RHEL-family server, the cause is usually one of a handful of things: a CPU that lacks the instructions MongoDB needs, wrong file ownership, SELinux, a port already in use, or a bad line in the config file. This guide shows how to find which one it is and fix it on AlmaLinux and Rocky Linux. It applies to your own VPS or server; MongoDB can't be installed on shared hosting.

1. First look: status, journal and log

Run these three commands and read the output before you change anything:

sudo systemctl status mongod
sudo journalctl -u mongod -n 50 --no-pager
sudo tail -n 50 /var/log/mongodb/mongod.log

The journal shows how the process died. The MongoDB log, which is written as one JSON document per line, usually says why. To make it easier to read, filter for errors:

sudo grep -E '"s":"(E|F)"' /var/log/mongodb/mongod.log | tail -n 20

"s":"F" lines are fatal errors and "s":"E" lines are errors. The msg and attr fields describe the problem.

2. "Illegal instruction": check the CPU

On x86_64, MongoDB 5.0 and every later release are built for CPUs with AVX instructions. If the CPU, or the virtual CPU your VPS presents, doesn't expose AVX, mongod crashes the moment it starts. You'll see status=4/ILL in systemctl status, and the kernel log shows a trap:

sudo dmesg | grep -i -E 'mongod|trap'

Check which instruction sets the CPU exposes:

grep -o -w -E 'avx|avx2|sse4_2' /proc/cpuinfo | sort -u
lscpu | grep -i -E 'model name|flags' | head -n 2

If avx is missing from the output, current MongoDB releases cannot run on this machine as it is configured. On a virtual server this usually means the hypervisor presents a generic CPU model to the guest instead of the host's real CPU. You can't fix that from inside the VPS.

On ARM (aarch64) servers, MongoDB 5.0 and later need ARMv8.2-A or newer. Older ARM boards hit the same crash.

3. Fixing a missing-AVX problem

On a Domain India VPS, run the grep command above. If avx is missing, open a support ticket with the output and your VPS details, and support will tell you what can be done.

4. Permissions and SELinux

MongoDB runs as the mongod user, which must own its data and log directories. After a restore, a manual copy or running mongod once as root, these often end up owned by root:

ls -ld /var/lib/mongo /var/lib/mongodb /var/log/mongodb 2>/dev/null
sudo chown -R mongod:mongod /var/lib/mongo /var/log/mongodb
sudo systemctl restart mongod

The default data path in the official RHEL packages is /var/lib/mongo; check storage.dbPath in /etc/mongod.conf if you changed it.

On AlmaLinux and Rocky Linux, SELinux is enforcing by default. If ownership is right but you still see "Permission denied", look for SELinux denials:

getenforce
sudo ausearch -m avc -ts recent | grep mongod

Don't switch SELinux off to make the error go away. MongoDB's installation guide for Red Hat Enterprise Linux describes its SELinux policy and the semanage fcontext commands needed when the data or log directory is in a non-default path.

5. Port, config file, disk and lock file

Port already in use. Another mongod, or a container, may already hold port 27017:

sudo ss -ltnp | grep 27017

Config file errors. /etc/mongod.conf is YAML: indentation must use spaces, not tabs, and keys are case-sensitive. A single wrong indent stops the service. After editing, restart and read the log, which names the line it could not parse.

Disk full. df -h /var/lib/mongo shows free space. MongoDB stops writing when the disk fills, and the journal needs room to start.

After a crash. If the server lost power, MongoDB normally recovers from its journal on the next start. Don't delete files in the data directory to "clear a lock"; if it won't start after a crash, restore from a backup or follow MongoDB's repair guidance for your version.

6. Check the service and shell

The mongo shell used in older guides was removed in MongoDB 6.0. Use mongosh:

mongosh --eval 'db.runCommand({ ping: 1 })'

A reply of { ok: 1 } means the server is running and accepting connections. For production, keep net.bindIp at 127.0.0.1 unless another server must connect, turn on authentication, and never open port 27017 to the whole internet. Allow it in the firewall only from the specific servers that need it.

7. Package and repository problems

On AlmaLinux and Rocky Linux, use dnf and the official MongoDB repository for your major version and OS release. If you have an old or wrong repository file, remove it and clean the cache before installing again:

sudo rm /etc/yum.repos.d/mongodb-org*.repo
sudo dnf clean all

Then add the repository file for a currently supported MongoDB release, as shown in MongoDB's installation guide for Red Hat Enterprise Linux. CentOS Linux 7 and 8 are end of life, so new servers should use AlmaLinux or Rocky Linux instead.

8. MongoDB on Domain India

A Domain India VPS is self-managed with full root access and KVM virtualization, so you install and run MongoDB yourself; the live VPS page lists MongoDB among the databases you can run. Check for AVX first with the command in section 2. For setup steps see installing MongoDB on a Domain India VPS, and if you're still choosing a database, read choosing between PostgreSQL, MySQL, SQLite and MongoDB.

Prices on the cards are live and exclude 18% GST. Domain India VPS plans are self-managed, so MongoDB installation, updates and backups are your responsibility.

Ready to run MongoDB on your own server? Compare the VPS plans, check AVX with the command above, and open a support ticket if the CPU check fails on a Domain India VPS.