MongoDB 8.0 compatibility issue

Mirali_Rafiyev · 2024-10-03T11:44:11.399Z

I installed mongodb 8.0 to ubuntu 22.04 server and got error

× mongod.service - MongoDB Database Server
Loaded: loaded (/lib/systemd/system/mongod.service; enabled; vendor preset: enabled)
Active: failed (Result: core-dump) since Thu 2024-10-03 11:29:38 UTC; 6s ago
Docs: https://docs.mongodb.org/manual
Process: 1431 ExecStart=/usr/bin/mongod --config /etc/mongod.conf (code=dumped, signal=ILL)
Main PID: 1431 (code=dumped, signal=ILL)
CPU: 30ms

Oct 03 11:29:38 playhub systemd[1]: Started MongoDB Database Server.
Oct 03 11:29:38 playhub systemd[1]: mongod.service: Main process exited, code=dumped, status=4/ILL
Oct 03 11:29:38 playhub systemd[1]: mongod.service: Failed with result ‘core-dump’.

i have searched a little bit and found some CPU compatibility issue which is not clear for me so please help to solve this issue if it’s not related to compatibility issue.

here is CPU details

Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Address sizes: 40 bits physical, 48 bits virtual
Byte Order: Little Endian
CPU(s): 4
On-line CPU(s) list: 0-3
Vendor ID: GenuineIntel
Model name: Common KVM processor
CPU family: 15
Model: 6
Thread(s) per core: 1
Core(s) per socket: 2
Socket(s): 2
Stepping: 1
BogoMIPS: 5187.49
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscal
l nx lm constant_tsc nopl xtopology cpuid tsc_known_freq pni cx16 x2apic hypervisor lahf_lm cpuid_fault pti
Virtualization features:
Hypervisor vendor: KVM
Virtualization type: full
Caches (sum of all):
L1d: 128 KiB (4 instances)
L1i: 128 KiB (4 instances)
L2: 16 MiB (4 instances)
L3: 32 MiB (2 instances)
NUMA:
NUMA node(s): 1
NUMA node0 CPU(s): 0-3
Vulnerabilities:
Gather data sampling: Not affected
Itlb multihit: KVM: Mitigation: VMX unsupported
L1tf: Mitigation; PTE Inversion
Mds: Vulnerable: Clear CPU buffers attempted, no microcode; SMT Host state unknown
Meltdown: Mitigation; PTI
Mmio stale data: Unknown: No mitigations
Reg file data sampling: Not affected
Retbleed: Not affected
Spec rstack overflow: Not affected
Spec store bypass: Vulnerable
Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Spectre v2: Mitigation; Retpolines; STIBP disabled; RSB filling; PBRSB-eIBRS Not affected; BHI Retpoline
Srbds: Not affected
Tsx async abort: Not affected

RAM details

top - 11:35:39 up 30 min, 1 user, load average: 0.13, 0.06, 0.07
Tasks: 114 total, 1 running, 113 sleeping, 0 stopped, 0 zombie
%Cpu(s): 0.1 us, 0.0 sy, 0.0 ni, 99.8 id, 0.1 wa, 0.0 hi, 0.0 si, 0.1 st
MiB Mem : 7937.4 total, 7172.5 free, 199.0 used, 565.8 buff/cache
MiB Swap: 0.0 total, 0.0 free, 0.0 used. 7496.2 avail Mem

chris · 2024-10-04T15:15:16.326Z

Hi @Mirali_Rafiyev

Yes, the vCPU is missing required feature set (avx2).

Either the virtual machince host does not support it or the virtual machine guest cpu needs re-configuring.

system · 2024-10-09T15:15:38.087Z

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