New to graylog having difficulty installing mongodb

Hello,
This is for a fresh install of mongodb and I keep getting this error. Please advise on how to fix this issue:

[sudo] password for console:
× mongod.service - MongoDB Database Server
Loaded: loaded (/lib/systemd/system/mongod.service; enabled; vendor preset: enabled)
Active: failed (Result: core-dump) since Fri 2023-02-24 22:54:46 UTC; 2 days ago
Docs: https://docs.mongodb.org/manual
Main PID: 1138 (code=dumped, signal=ILL)
CPU: 64ms

Feb 24 22:54:45 graylog systemd[1]: Started MongoDB Database Server.
Feb 24 22:54:46 graylog systemd[1]: mongod.service: Main process exited, code=dumped, status=4/ILL
Feb 24 22:54:46 graylog systemd[1]: mongod.service: Failed with result ‘core-dump’.

Hello && welcome @mfmaruzzo

Found this here for you.

1 Like

What version of Linux? Does your CPU support AVX?

how do i verify that? we run on vmware environment. Our server’s processor is Intel Xeon CPU E7-4809 v4 @ 2.10GHz. im running the latest ubuntu server 20.04 LTS

which OS are you running?

ubuntu server 20.04 LTS

in the terminal of the ESXi host run:

grep avx /proc/cpuinfo

you should get something like this: "avx"
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 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 smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx lahf_lm epb pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid xsaveopt dtherm ida arat pln pts md_clear flush_l1d
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 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 smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx lahf_lm epb pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid xsaveopt dtherm ida arat pln pts md_clear flush_l1d
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 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 smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx lahf_lm epb pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid xsaveopt dtherm ida arat pln pts md_clear flush_l1d
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 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 smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx lahf_lm epb pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid xsaveopt dtherm ida arat pln pts md_clear flush_l1d

it gives me no result when i typed those commands:

console@graylog:~$
console@graylog:~$ grep avx /proc/cpuinfo
console@graylog:~$
console@graylog:~$ sudo grep avx /proc/cpuinfo
console@graylog:~$

That would could mean you will have issues running MongoDB V5 or V6, it’s a requirement of the processor from these versions upwards.
Below is the link to the Mongo Docs for processor support.

ok, thanks, i guess that ends my journey in trying to install graylog. there’s no alternative in this?

If you are installing single node, and don’t need major ingestion and you just want to trial it, you can install it with docker on another dedicated PC with AVX support or you can install it on Windows for test purposes only. On Windows you can install WSL and in WSL install docker. Then deploy Graylog on Docker. Is that an option for you?

yes, only single node. would there be a problem if i install it inside a windows server 2019 VM?

Same thing would apply on the AVX support if it was still running on a ESXi host.

Also, if using Hyper-V, you will need to disable CPU compatibility in the VM.

This is assuming the CPU in your Windows Server 2019 machine supports AVX.

2 Likes