Mongo db failed -- Unable to start mongodb

davip · 2021-09-15T04:16:53.370Z

mongod.service - MongoDB Database Server
     Loaded: loaded (/lib/systemd/system/mongod.service; disabled;>
     Active: failed (Result: core-dump) since Wed 2021-09-15 05:15>
       Docs: https://docs.mongodb.org/manual
    Process: 24919 ExecStart=/usr/bin/mongod --config /etc/mongod.>
   Main PID: 24919 (code=dumped, signal=ILL)

Sep 15 05:15:03 kold systemd[1]: Started MongoDB Database Server.
Sep 15 05:15:04 kold systemd[1]: mongod.service: Main process exit>
Sep 15 05:15:04 kold systemd[1]: mongod.service: Failed with resul>
lines 1-10/10 (END)

Stennie_X · 2021-09-15T10:50:08.399Z

Welcome to the MongoDB Community Forums @davip !

To help investigate your issue please:

confirm the version of MongoDB server you installed
provide the output of cat /proc/cpuinfo
confirm if this is running in a virtual machine instance (and if so, what is the host software & version)?

(code=dumped, signal=ILL)

The likely reason for encountering an ILL (illegal instruction) signal is that your CPU does not meet the x86_64 microarchitecture requirements for the version of MongoDB server you are trying to install.

Regards,
Stennie

davip · 2021-09-15T19:01:33.714Z

processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 58
model name	: Intel(R) Pentium(R) CPU G2020T @ 2.50GHz
stepping	: 9
microcode	: 0x21
cpu MHz		: 1765.862
cache size	: 3072 KB
physical id	: 0
siblings	: 2
core id		: 0
cpu cores	: 2
apicid		: 0
initial apicid	: 0
fpu		: yes
fpu_exception	: yes
cpuid level	: 13
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 popcnt tsc_deadline_timer xsave lahf_lm cpuid_fault epb pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm arat pln pts md_clear flush_l1d
vmx flags	: vnmi preemption_timer invvpid ept_x_only flexpriority tsc_offset vtpr mtf vapic ept vpid unrestricted_guest
bugs		: cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit
bogomips	: 4988.50
clflush size	: 64
cache_alignment	: 64
address sizes	: 36 bits physical, 48 bits virtual
power management:

processor	: 1
vendor_id	: GenuineIntel
cpu family	: 6
model		: 58
model name	: Intel(R) Pentium(R) CPU G2020T @ 2.50GHz
stepping	: 9
microcode	: 0x21
cpu MHz		: 1770.456
cache size	: 3072 KB
physical id	: 0
siblings	: 2
core id		: 1
cpu cores	: 2
apicid		: 2
initial apicid	: 2
fpu		: yes
fpu_exception	: yes
cpuid level	: 13
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 popcnt tsc_deadline_timer xsave lahf_lm cpuid_fault epb pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm arat pln pts md_clear flush_l1d
vmx flags	: vnmi preemption_timer invvpid ept_x_only flexpriority tsc_offset vtpr mtf vapic ept vpid unrestricted_guest
bugs		: cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit
bogomips	: 4988.50
clflush size	: 64
cache_alignment	: 64
address sizes	: 36 bits physical, 48 bits virtual
power management:

I’m using the latest version of mongodb, 5.0.2 and i followed the steps on the official installation doc. I’m not using a virtual Machine.

Stennie_X · 2021-09-16T03:11:13.946Z

Hi @davip,

Thank you for providing detailed CPU information. Unfortunately your Pentium G2020T processor does not meet the microarchitecture requirements for MongoDB 5.0 binary packages. In particular it is missing AVX (Advanced Vector Extensions) which typically are not available in Pentium or Celeron CPUs.

Your options to run MongoDB on this hardware are:

Install the MongoDB 4.4 binary packages (which do not use the same compiler optimisations)
Build MongoDB from Source with an older gcc microarchitecture target, eg:

CCFLAGS=-march=nehalem

Regards,
Stennie

Bora_Kayalar · 2021-09-17T11:37:52.690Z

Hi
I try to install mongo-org 5.0.2 cominuty version to my server :
My server conf is :
CPU : Intel(R) Xeon(R) CPU E5-2690 v2 @ 3.00GHz (Ivy Bridge Family)
OS : Centos 8.4 64bit

Actually there is no problem about installation but When I start to mongo service I am getting error at below.

[root@14979-26502 ~]# sudo service mongod start
Redirecting to /bin/systemctl start mongod.service
Job for mongod.service failed because a fatal signal was delivered causing the control process to dump core.
See "systemctl status mongod.service" and "journalctl -xe" for details.
[root@14979-26502 ~]# journalctl -xe
                                                                 #3  0x00005592e58d059d _ZN8tcmalloc11ThreadCache22CreateCacheIfNecessaryEv (mongod)
                                                                 #4  0x00005592e59796f5 _ZN8tcmalloc24allocate_full_malloc_oomEm (mongod)
                                                                 #5  0x00007f2fe1b1800f __fopen_internal (libc.so.6)
                                                                 #6  0x00007f2fdf217dc2 selinuxfs_exists (libselinux.so.1)
                                                                 #7  0x00007f2fdf20fd0c init_lib (libselinux.so.1)
                                                                 #8  0x00007f2fe38878ba call_init.part.0 (ld-linux-x86-64.so.2)
                                                                 #9  0x00007f2fe38879ba _dl_init (ld-linux-x86-64.so.2)
                                                                 #10 0x00007f2fe3878fda _dl_start_user (ld-linux-x86-64.so.2)

SELinux is disabled

Is this about cpu? Meanwhile I could install and run mongo 4.4 but I want to use 5.0.2

Details of cpu info and also my server runs on wmware :

processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 37
model name      : Intel(R) Xeon(R) CPU E5-2690 v2 @ 3.00GHz
stepping        : 1
microcode       : 0x42e
cpu MHz         : 3000.000
cache size      : 25600 KB
physical id     : 0
siblings        : 1
core id         : 0
cpu cores       : 1
apicid          : 0
initial apicid  : 0
fpu             : yes
fpu_exception   : yes
cpuid level     : 11
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov                                                                                                                                                              pat pse36 clflush dts mmx fxsr sse sse2 syscall nx rdtscp lm constant_tsc arch_p                                                                                                                                                             erfmon pebs bts nopl xtopology tsc_reliable nonstop_tsc cpuid pni pclmulqdq ssse                                                                                                                                                             3 cx16 sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes hypervisor lahf_lm pti                                                                                                                                                              ssbd ibrs ibpb stibp tsc_adjust arat flush_l1d arch_capabilities
bugs            : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds                                                                                                                                                              swapgs itlb_multihit
bogomips        : 6000.00
clflush size    : 64
cache_alignment : 64
address sizes   : 43 bits physical, 48 bits virtual
power management:

processor       : 1
vendor_id       : GenuineIntel
cpu family      : 6
model           : 37
model name      : Intel(R) Xeon(R) CPU E5-2690 v2 @ 3.00GHz
stepping        : 1
microcode       : 0x42e
cpu MHz         : 3000.000
cache size      : 25600 KB
physical id     : 2
siblings        : 1
core id         : 0
cpu cores       : 1
apicid          : 2
initial apicid  : 2
fpu             : yes
fpu_exception   : yes
cpuid level     : 11
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov                                                                                                                                                              pat pse36 clflush dts mmx fxsr sse sse2 syscall nx rdtscp lm constant_tsc arch_p                                                                                                                                                             erfmon pebs bts nopl xtopology tsc_reliable nonstop_tsc cpuid pni pclmulqdq ssse                                                                                                                                                             3 cx16 sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes hypervisor lahf_lm pti                                                                                                                                                              ssbd ibrs ibpb stibp tsc_adjust arat flush_l1d arch_capabilities
bugs            : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds                                                                                                                                                              swapgs itlb_multihit
bogomips        : 6000.00
clflush size    : 64
cache_alignment : 64
address sizes   : 43 bits physical, 48 bits virtual
power management:

processor       : 2
vendor_id       : GenuineIntel
cpu family      : 6
model           : 37
model name      : Intel(R) Xeon(R) CPU E5-2690 v2 @ 3.00GHz
stepping        : 1
microcode       : 0x42e
cpu MHz         : 3000.000
cache size      : 25600 KB
physical id     : 4
siblings        : 1
core id         : 0
cpu cores       : 1
apicid          : 4
initial apicid  : 4
fpu             : yes
fpu_exception   : yes
cpuid level     : 11
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov                                                                                                                                                              pat pse36 clflush dts mmx fxsr sse sse2 syscall nx rdtscp lm constant_tsc arch_p                                                                                                                                                             erfmon pebs bts nopl xtopology tsc_reliable nonstop_tsc cpuid pni pclmulqdq ssse                                                                                                                                                             3 cx16 sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes hypervisor lahf_lm pti                                                                                                                                                              ssbd ibrs ibpb stibp tsc_adjust arat flush_l1d arch_capabilities
bugs            : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds                                                                                                                                                              swapgs itlb_multihit
bogomips        : 6000.00
clflush size    : 64
cache_alignment : 64
address sizes   : 43 bits physical, 48 bits virtual
power management:

processor       : 3
vendor_id       : GenuineIntel
cpu family      : 6
model           : 37
model name      : Intel(R) Xeon(R) CPU E5-2690 v2 @ 3.00GHz
stepping        : 1
microcode       : 0x42e
cpu MHz         : 3000.000
cache size      : 25600 KB
physical id     : 6
siblings        : 1
core id         : 0
cpu cores       : 1
apicid          : 6
initial apicid  : 6
fpu             : yes
fpu_exception   : yes
cpuid level     : 11
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov                                                                                                                                                              pat pse36 clflush dts mmx fxsr sse sse2 syscall nx rdtscp lm constant_tsc arch_p                                                                                                                                                             erfmon pebs bts nopl xtopology tsc_reliable nonstop_tsc cpuid pni pclmulqdq ssse                                                                                                                                                             3 cx16 sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes hypervisor lahf_lm pti                                                                                                                                                              ssbd ibrs ibpb stibp tsc_adjust arat flush_l1d arch_capabilities
bugs            : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds                                                                                                                                                              swapgs itlb_multihit
bogomips        : 6000.00
clflush size    : 64
cache_alignment : 64
address sizes   : 43 bits physical, 48 bits virtual
power management:

chris · 2021-09-17T13:18:58.698Z

Bora_Kayalar:

Is this about cpu? Meanwhile I could install and run mongo 4.4 but I want to use 5.0.2

Yes it is. See the last post from @Stennie_X.

It may be that the VMWare host itself does not have the supporting features. And depending on the VMWare product it could be compatibility(EVC modes) .

Bora_Kayalar · 2021-09-17T13:29:42.116Z

Thank you so much for your reply but mongo 4.4 works there is no problem about it,

chris · 2021-09-17T13:31:11.825Z

Read @Stennie_X’s answer, read the links.

Stennie_X · 2021-09-18T06:08:58.911Z

Welcome to the MongoDB Community Forums @Bora_Kayalar !

Bora_Kayalar:

Is this about cpu? Meanwhile I could install and run mongo 4.4 but I want to use 5.0.2

Yes, the issue is about the CPU support that is available within the environment that mongod is running in.

Your Intel(R) Xeon(R) CPU E5-2690 looks like it should have the right feature support, but as @chris mentioned virtualisation layers can affect the CPU features that are exposed.

I do not see the AVX extension which is required for the MongoDB 5.0 server binaries in your CPU info output. MongoDB 4.4 runs without issue because those server binaries are compiled for older microarchitecture targets.

As a quick test to confirm if the MongoDB 5.0 server binaries should run in your hardware environment before investing further time in VMware investigation, I would try running a 5.0 mongod directly in the host environment. You could use tgz/zip downloads instead of the packaged installers to minimise any installation artifacts (i.e. unpack tgz/zip download and run in a test directory, then remove after testing).

What are the versions of O/S and VMware for your host environment?

If you happen to be using a Windows host you may need to disable Hyper-V. There are similar issues with VirtualBox: HMR3Init: Attempting fall back to NEM (Hyper-V is active) - virtualbox.org.

Normally Hyper-V blocks Virtualbox. Hyper-V is a type-1 hypervisor, which accesses the hardware first before any OS runs, and therefore interferes with other programs that need “virtualization technology”, like Virtualbox, which is a type-2 Hypervisor.

Regards,
Stennie

Bora_Kayalar · 2021-09-23T15:29:26.082Z

Thank you so much, I solved it with vmware settings (EVC modes). @chris @Stennie_X

chris · 2021-09-23T15:37:56.769Z

Thanks for your follow up with what fixed it for you. It will likely help someone in the same position at a later date.

Bora_Kayalar · 2021-09-23T15:47:16.728Z

You’re right, actually I explained the problem to my server manager and He fixed vmware setups. So I dont know all details what he did. But it was about virtualization. So if anyone live the same problem he/she has to look at to vmware configurations.

system · 2021-09-28T15:47:26.380Z

This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.