Mongo DB 5.0 not install

[jegan]

Hello...!

New latest MongoDB 5.0 is not installing in my centos 7 and 8,

The error I got :

After installation of Mongo DB 5.0 it was not started and it was showing "Illegal instruction (core dumped)"

Sep 9 09:36:55 vps systemd[1]: Starting MongoDB Database Server...
Sep 9 09:36:55 vps kernel: traps: mongod[1214455] trap invalid opcode ip:56190269809a sp:7ffeb38315e0 error:0 in mongod[5618fe759000+5055000]
Sep 9 09:36:55 vps systemd[1]: Started Process Core Dump (PID 1214456/UID 0).
Sep 9 09:36:55 vps systemd[1]: mongod.service: Control process exited, code=dumped status=4
Sep 9 09:36:55 vps systemd[1]: mongod.service: Failed with result 'core-dump'.
Sep 9 09:36:55 vps systemd[1]: Failed to start MongoDB Database Server.
Sep 9 09:36:55 vps systemd-coredump[1214457]: Process 1214455 (mongod) of user 976 dumped core.#012#012Stack trace of thread 1214455:#012#0 0x000056190269809a _ZN8tcmalloc7SizeMap4InitEv (mongod)#012#1 0x00005619026a09b7 _ZN8tcmalloc6Static14InitStaticVarsEv (mongod)#012#2 0x00005619026a2407 _ZN8tcmalloc11ThreadCache10InitModuleEv (mongod)#012#3 0x00005619026a259d _ZN8tcmalloc11ThreadCache22CreateCacheIfNecessaryEv (mongod)#012#4 0x000056190274b6f5 _ZN8tcmalloc24allocate_full_malloc_oomEm (mongod)#012#5 0x00007fc9ea55000f __fopen_internal (libc.so.6)#012#6 0x00007fc9e7c4fdc2 selinuxfs_exists (libselinux.so.1)#012#7 0x00007fc9e7c47d0c init_lib (libselinux.so.1)#012#8 0x00007fc9ec2bf8ba call_init.part.0 (ld-linux-x86-64.so.2)#012#9 0x00007fc9ec2bf9ba _dl_init (ld-linux-x86-64.so.2)#012#10 0x00007fc9ec2b0fda _dl_start_user (ld-linux-x86-64.so.2)
Sep 9 09:36:55 vps systemd[1]: systemd-coredump@548-1214456-0.service: Succeeded.


But Tried in VMware, it's installing properly. I guess there is a problem with Proxmox hypervisor.

Base Machine Details
------------------------------

we have a Proxmox Virtual Environment 6.3-3

PRETTY_NAME="Debian GNU/Linux 10 (buster)"
NAME="Debian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

processor : 30
vendor_id : GenuineIntel
cpu family : 6
model : 45
model name : Intel(R) Xeon(R) CPU E5-4650 0 @ 2.70GHz
stepping : 7
microcode : 0x710
cpu MHz : 2899.961
cache size : 20480 KB
physical id : 3
siblings : 16
core id : 6
cpu cores : 8
apicid : 108
initial apicid : 108
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 pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx lahf_lm epb pti tpr_shadow vnmi flexpriority ept vpid xsaveopt dtherm ida arat pln pts
bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit
bogomips : 5419.26
clflush size : 64
cache_alignment : 64
address sizes : 46 bits physical, 48 bits virtual
power management:



please help to solve this issue

 

[Stefan_R]

"illegal instruction" is a weird error indeed. Can you post your VM config? (qm config <vmid>) Potentially try using a different CPU model for your VM, even going to 'host' may be interesting (if only for testing).

 

[tmatthaeus]

Dear @jegan did you found any solution in Proxmox for that?
@Stefan_R I have the same problem. Here are my VM config as requested:

qm config 135
agent: 1,fstrim_cloned_disks=1
boot: c
bootdisk: scsi0
cores: 4
ide2: none,media=cdrom
memory: 8192
name: rocketchat
net0: virtio=DA:7C:BB:67:B9:00,bridge=vmbr0,firewall=1,tag=70
numa: 0
onboot: 1
ostype: l26
parent: updates_20211018
protection: 1
scsi0: ceph-vm:base-902-disk-0/vm-135-disk-0,size=64G
scsihw: virtio-scsi-pci
smbios1: uuid=65682778-3492-46a5-a142-59cc0c69c47e
sockets: 1
vmgenid: b74de17d-35bf-4380-8dbf-16740fd6a1ac

 

[jegan]

root@proxmox13:~# qm config 1114
bootdisk: scsi0
cipassword: **********
ciuser: root
cores: 2
hotplug: disk,network,usb
ide0: storage:1114/vm-1114-cloudinit.qcow2,media=cdrom,size=4M
ide2: none,media=cdrom
ipconfig0: ip=**.**.**.01/23,gw=103.159.84.1
memory: 2048
name: mariadb
net0: virtio=D2:**:**:88:44:BF,bridge=vmbr0,firewall=1,rate=10
numa: 1
ostype: l26
scsi0: storage:1114/vm-1114-disk-0.qcow2,size=32G
scsihw: virtio-scsi-pci
smbios1: uuid=7233bb19-7bc8-4ef3-83f6-cc84bfa079a7
sockets: 1
sshkeys:

 

[oguz]

have you tried using host CPU model in your VM like suggested before? does that make a difference?

 

[Dr.Ish]

Hello.
Faced the same problem.
Hosting support, said that it uses xeon e5, it seems to fit the minimum processor requirements
installed the host processor but it didn't work

boot: order=virtio0;ide2;net0
cores: 2
cpu: host
ide2: fast:iso/debian-11.1.0-amd64-netinst.iso,media=cdrom,size=378M
memory: 2048
name: nodejs
net0: virtio=12:5C:22:DF:8F:1E,bridge=vmbr1,firewall=1
numa: 0
ostype: l26
scsihw: virtio-scsi-pci
smbios1: uuid=44f8b51f-cbfb-45d6-9ca7-ababd409d368
sockets: 1
virtio0: fast:104/vm-104-disk-0.qcow2,size=64G
vmgenid: e5c8b7df-4a66-4d8e-90b4-10fef56bfe5d

 

[Dr.Ish]

Hello.
The point is in the instructions for the processor.
In

cat /proc/cpuinfo

should be AVX without it will not work. I took another air force, which has this AVX and it all worked.

 

[jegan]

processor : 24
vendor_id : GenuineIntel
cpu family : 6
model : 79
model name : Intel(R) Xeon(R) CPU E5-2680 v4 @ 2.40GHz
stepping : 1
microcode : 0xb00002a
cpu MHz : 2893.093
cache size : 35840 KB
physical id : 1
siblings : 28
core id : 11
cpu cores : 14
apicid : 54
initial apicid : 54
fpu : yes
fpu_exception : yes
cpuid level : 20
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 pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb cat_l3 cdp_l3 invpcid_single pti intel_ppin ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm cqm rdt_a rdseed adx smap intel_pt xsaveopt cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local dtherm ida arat pln pts
bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs taa itlb_multihit
bogomips : 4794.70
clflush size : 64
cache_alignment : 64
address sizes : 46 bits physical, 48 bits virtual
power management:

 

[MichaelG]

I have had the same issue on my Proxmox the last few days, installing Ubuntu Server 20.04 LTS on both VMware Player on my windows machine, and on my Proxmox server. The exact same commands was written into both servers. Had putty on both of them side by side, same command on both machines at the same time. But it keept failing on Proxmox, looked into this, and turns out, Proxmox guests, uses KVM64 as default CPU, and KVM64 doesnt support AVX, which is needed by MongoDB 5.x

So to fix this issue, change the CPU from KVM64 to Host at your guest image, and mongoDB will work...

 

[jegan]

Thanks and it's working fine

 

[oguz]

Thanks and it's working fine

great, then you can mark the thread as [SOLVED]

 

[tuxis]

This is a workaround, not a solution imho.

You can set type to host. This has a downside though. If you want to do a live migration of VMs between different hosts, your VM might end up on a new system with a different CPU type. If the CPU flags passed to the guest are missing, the qemu process will stop.

Live migration is an important feature of virtualisation so you can do maintenance on hardware without interrupting production.

 

[InQuize]

You can set type to host. This has a downside though.

'x86-64-v3' type has AVX and works for MongoDB