Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Servers, nginx and Docker

mongod dies at start with a core dump because the CPU is too old

Errormongod.service ends with result core-dump a moment after start

Short answer

MongoDB 5.0 and later needs the AVX instruction set on x86_64, and the ARMv8.2-A microarchitecture on arm64. On a CPU below that, mongod crashes at start instead of printing an error. Check the CPU flags, then move to hardware that meets the requirement.

  • Applies to MongoDB 5.0 and later, Ubuntu 24.04
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    Find the CPU architecture. Then check for the avx flag on x86_64.

    uname -m
    grep -o -m1 -w avx /proc/cpuinfo || echo "no avx flag"
  2. 2Match what you see, then jump to its fix

    1. 1uname -m prints x86_64 and the avx check prints 'no avx flag'The x86_64 CPU has no AVXFix
    2. 2uname -m prints aarch64 and mongod crashes at startThe arm64 CPU is older than ARMv8.2-AFix

What does the error look like?

  • mongod.service ends with result core-dump a moment after start
  • mongod crashes at start on a CPU without the avx flag
  • mongod crashes at start on an arm64 board older than ARMv8.2-A

Cause 1 of 2

The x86_64 CPU has no AVX

1Check

The MongoDB production notes state that MongoDB 5.0 and later requires the AVX instruction set, available on select Intel and AMD processors. Some low-end and some virtualised CPUs do not expose it.

lscpu | grep -i "model name"
mongod --version | head -n 1

2Fix

Run MongoDB on a machine whose CPU has AVX. If it is a VM, ask the host provider for a CPU type that exposes AVX. Running a release below 5.0 avoids the rule, but old releases stop getting fixes once they reach end of life.

# after moving to a host that reports avx
sudo systemctl start mongod

3Verify

The service stays active.

systemctl status mongod

Confirmed by mongodb.com

Did this fix it?

Cause 2 of 2

The arm64 CPU is older than ARMv8.2-A

1Check

On arm64 MongoDB needs the ARMv8.2-A or later microarchitecture. Since 5.0, mongod, mongos and the legacy mongo shell no longer support arm64 platforms below it.

uname -m
lscpu | grep -i -E "model name|architecture"

2Fix

Use an arm64 host that meets ARMv8.2-A, or an x86_64 host with AVX. Look up the exact core of your board in the vendor's data sheet.

# no setting fixes this; move to hardware that meets ARMv8.2-A, then:
sudo systemctl start mongod

3Verify

On the new host, start the service and check it.

sudo systemctl start mongod
systemctl status mongod

Confirmed by mongodb.com

Did this fix it?

How do I stop it coming back?

  • Check the CPU against the production notes before picking a server, VM type or board for MongoDB.
  • When you move a VM between hosts, confirm the avx flag is still present.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Which stack is behind this page?

Related fixes

Servers

dnf cannot install MySQL on Amazon Linux 2023

dnf cannot find a mysql-server package on Amazon Linux 2023

Amazon Linux 2023 documents MariaDB, not MySQL, as its database server, with packages named mariadb105 and mariadb105-server.

3 causes, each with a fix

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.