Mongodb (Result= Signal, Code = Killed, Signal = Ill

Mongod does not start (mongod.service: Failed with result 'signal')

Signal "ILL" is illegal instruction.

MongoDB 5.0 requires Advanced Vector Extensions, Xeon E5540 does not have them.

For a list of processors that support AVX, see https://en.wikipedia.org/wiki/Advanced_Vector_Extensions#CPUs_with_AVX

Mongod does not start: mongod.service: Failed with result 'signal'

While this doesn't completely solve the issue, I'm fine with this resolution:
For whatever reason, 4.2 works fine, but 4.4 doesn't, even though I was completely fine running 4.4 on Arch.

Why mongod.service is killed by my system?

I figured out that my Linux ulimits were not set to the recommended values of mongod instance.
One of the limits ( locked-in-memory ) was 65536 and in /lib/systemd/system/mongod.service LimitMEMLOCK was infinity.
So I've changed that to 65536, restarted the service and it was working again.

This worked for me!

mongodb.service dies after running some hours in Ubuntu

using dmesg -T show the reason why system kill mongodb(updated in question section), it's because "ot ouf memory".
Mongodb consumes 2486640kB while my server is 16 GB, so mongodb does not consume too high memory.

The failure is because other programs take too much memory, it's not mongodb problem

---

Related Topics