Job for mongod.service failed because a fatal signal was delivered to the control process

I installe mongodb following this tutorial https://www.mongodb.com/docs/manual/tutorial/install-mongodb-on-red-hat/. It gives an error when I try to start the service. can you help me ?

[root@ns1 ~]# systemctl start mongod
Job for mongod.service failed because a fatal signal was delivered to the control process. See "systemctl status mongod.service" and "journalctl -xe" for details.
[root@ns1 ~]# systemctl status mongod.service
● mongod.service - MongoDB Database Server
   Loaded: loaded (/usr/lib/systemd/system/mongod.service; enabled; vendor preset: disabled)
   Active: failed (Result: signal) since Wed 2022-07-06 21:11:45 +03; 31s ago
     Docs: https://docs.mongodb.org/manual
  Process: 572214 ExecStart=/usr/bin/mongod $OPTIONS (code=killed, signal=ILL)
  Process: 572210 ExecStartPre=/usr/bin/chmod 0755 /var/run/mongodb (code=exited, status=0/SUCCESS)
  Process: 572207 ExecStartPre=/usr/bin/chown mongod:mongod /var/run/mongodb (code=exited, status=0/SUCCESS)
  Process: 572205 ExecStartPre=/usr/bin/mkdir -p /var/run/mongodb (code=exited, status=0/SUCCESS)

Jul 06 21:11:45 ns1.localhost.com systemd[1]: Starting MongoDB Database Server...
Jul 06 21:11:45 ns1.localhost.com systemd[1]: mongod.service: control process exited, code=killed status=4
Jul 06 21:11:45 ns1.localhost.com systemd[1]: Failed to start MongoDB Database Server.
Jul 06 21:11:45 ns1.localhost.com systemd[1]: Unit mongod.service entered failed state.
Jul 06 21:11:45 ns1.localhost.com systemd[1]: mongod.service failed.

The errors I get when I run journalctl -xe.

-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat
--
-- A new session with the ID c15063 has been created for the user root.
--
-- The leading process of the session is 561230.
Jul 06 00:31:55 ns1.localhost.com sudo[561230]: pam_unix(sudo:session): session opened for user root by root
Jul 06 00:31:55 ns1.localhost.com polkitd[458]: Registered Authentication Agent for unix-process:561232:1926
Jul 06 00:31:55 ns1.localhost.com systemd[1]: Starting MongoDB Database Server...
-- Subject: Unit mongod.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mongod.service has begun starting up.
Jul 06 00:31:55 ns1.localhost.com kernel: traps: mongod[561243] trap invalid opcode ip:55b5947535da sp:7ffd0
Jul 06 00:31:55 ns1.localhost.com systemd[1]: mongod.service: control process exited, code=killed status=4
Jul 06 00:31:55 ns1.localhost.com systemd[1]: Failed to start MongoDB Database Server.
-- Subject: Unit mongod.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mongod.service has failed.
--
-- The result is failed.
Jul 06 00:31:55 ns1.localhost.com systemd[1]: Unit mongod.service entered failed state.
Jul 06 00:31:55 ns1.localhost.com systemd[1]: mongod.service failed.
Jul 06 00:31:55 ns1.localhost.com polkitd[458]: Unregistered Authentication Agent for unix-process:561232:19
Jul 06 00:31:55 ns1.localhost.com sudo[561230]: pam_unix(sudo:session): session closed for user root
Jul 06 00:31:55 ns1.localhost.com systemd-logind[459]: Removed session c15063.
-- Subject: Session c15063 has been terminated
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Jul 06 00:31:55 ns1.localhost.com kernel: traps: mongod[561243] trap invalid opcode ip:55b5947535da sp:7ffd0

Your hardware doesn’t support the version of mongod you are attempting to run.

x86_64

MongoDB requires the following minimum x86_64 microarchitectures: [3]

  • For Intel x86_64 , MongoDB requires one of:
  • a Sandy Bridge or later Core processor, or
  • a Tiger Lake or later Celeron or Pentium processor.
  • For AMD x86_64 , MongoDB requires:
  • a Bulldozer or later processor.

Starting in MongoDB 5.0, mongod , mongos , and the legacy mongo shell no longer support x86_64 platforms which do not meet this minimum microarchitecture requirement.

Hello mister

Had you resolv the problem with mongodb?

Best regards.