MongoDb 5 Docker failed to start after Upgrade about graylog-docker

[bernd]

@HungryHowies The MongoDB message indicates that your CPU doesn't support the AVX instructions.

You can check your hypervisor settings if it's possible to enable these instructions for the virtual machine.

WARNING: MongoDB 5.0+ requires a CPU with AVX support, and your current system does not appear to have that!

[HungryHowies]

@bernd
Hey,
Thank you for the reply, much appreciated.
Yeah I did some digging. Thankfully this is only my lab Hyper-v servers. Glad I found this issue before we upgrade.

[HungryHowies]

@bernd
My fix was... Unchecking the tic box

But new errors occurred.

Dec  8 17:26:43 ansible dockerd[1254]: time="2022-12-08T17:26:43.701125233-06:00" level=warning msg="Health check for container 41c441ca3b149707002c2d3b5805af3c77c86c48ca43c2584ea1d607019f1c95 error: Cannot link to a non running container: /a90dc5802cd9_bin_mongodb_1 AS /bin_graylog_1/bin_mongodb_1"
Dec  8 17:26:53 ansible dockerd[1254]: time="2022-12-08T17:26:53.821076778-06:00" level=warning msg="Health check for container 41c441ca3b149707002c2d3b5805af3c77c86c48ca43c2584ea1d607019f1c95 error: Cannot link to a non running container: /a90dc5802cd9_bin_mongodb_1 AS /bin_graylog_1/mongodb_1"
Dec  8 17:27:04 ansible dockerd[1254]: time="2022-12-08T17:27:04.004540983-06:00" level=warning msg="Health check for container 41c441ca3b149707002c2d3b5805af3c77c86c48ca43c2584ea1d607019f1c95 error: Cannot link to a non running container: /a90dc5802cd9_bin_mongodb_1 AS /bin_graylog_1/bin_mongodb_1"
Dec  8 17:27:14 ansible dockerd[1254]: time="2022-12-08T17:27:14.026510867-06:00" level=warning msg="Health check for container 41c441ca3b149707002c2d3b5805af3c77c86c48ca43c2584ea1d607019f1c95 error: Cannot link to a non running container: /a90dc5802cd9_bin_mongodb_1 AS /bin_graylog_1/bin_mongodb_1"
Dec  8 17:27:24 ansible dockerd[1254]: time="2022-12-08T17:27:24.092746682-06:00" level=warning msg="Health check for container 41c441ca3b149707002c2d3b5805af3c77c86c48ca43c2584ea1d607019f1c95 error: Cannot link to a non running container: /a90dc5802cd9_bin_mongodb_1 AS /bin_graylog_1/bin_mongodb_1"
Dec  8 17:27:34 ansible dockerd[1254]: time="2022-12-08T17:27:34.109101675-06:00" level=warning msg="Health check for container 41c441ca3b149707002c2d3b5805af3c77c86c48ca43c2584ea1d607019f1c95 error: Cannot link to a non running container: /a90dc5802cd9_bin_mongodb_1 AS /bin_graylog_1/bin_mongodb_1"
Dec  8 17:27:44 ansible dockerd[1254]: time="2022-12-08T17:27:44.126879809-06:00" level=warning msg="Health check for container 41c441ca3b149707002c2d3b5805af3c77c86c48ca43c2584ea1d607019f1c95 error: Cannot link to a non running container: /a90dc5802cd9_bin_mongodb_1 AS /bin_graylog_1/mongo"
Dec  8 17:27:53 ansible kernel: [ 2473.152844] traps: mongod[18239] trap invalid opcode ip:56311d63fa7a sp:7ffc21b4de10 error:0 in mongod[5631195ba000+51eb000]
Dec  8 17:27:54 ansible dockerd[1254]: time="2022-12-08T17:27:54.182350966-06:00" level=warning msg="Health check for container 41c441ca3b149707002c2d3b5805af3c77c86c48ca43c2584ea1d607019f1c95 error: Cannot link to a non running container: /a90dc5802cd9_bin_mongodb_1 AS /bin_graylog_1/bin_mongodb_1"
Dec  8 17:28:04 ansible dockerd[1254]: time="2022-12-08T17:28:04.426020497-06:00" level=warning msg="Health check for container 41c441ca3b149707002c2d3b5805af3c77c86c48ca43c2584ea1d607019f1c95 error: Cannot link to a non running container: /a90dc5802cd9_bin_mongodb_1 AS /bin_graylog_1/bin_mongodb_1"
root@ansible:/usr/local/bin#

Working on the resolve, but I'm starting to think that an upgrade might not be my solution, perhaps a fresh install.

[HungryHowies]

@bernd

I thought I resolved it, but its a "No Go". I aware of the correct cpu architecture type is needed. TBH this is the first time I upgraded software and the service would not start unless I have to correct CPU. Were still looking into. BTW I tried CentOS 7, Ubuntu 18,20,22. and the latest Docker/Docker-compose. Same out come.

https://en.wikipedia.org/wiki/Advanced_Vector_Extensions#CPUs_with_AVX

[bernd]

@HungryHowies Does the CPU on your hypervisor support the AVX instructions?

The screenshot doesn't show the exact CPU model.

[HungryHowies]

@bernd

Sort answerer no it doesn't.
This is unfortunate that the CPU's on our blade servers is prevent us to upgrade or use the newer software. True they may be a little old, also true Advanced Vector Extensions (AVX) are additions to the x86 instruction set architecture. Put simply, the additional instruction set allow compatible processors to perform more demanding functions when used with compatible software. So I am aware but for now our option at this point is compile Mongo OR replace all the CPU that is incompatible (i.e., this would be very expensive and time consuming) OR stay with old version OR move on.

• https://github.com/mongodb/mongo/blob/master/docs/building.md
• mongodb/docs@7f1143f

@bernd Here is my Test GL Server specs. Notice we do have "sse " but not AVX.

[root@graylog graylog]# cat /proc/cpuinfo
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 44
model name      : Intel(R) Xeon(R) CPU           E5620  @ 2.40GHz
stepping        : 2
microcode       : 0xffffffff
cpu MHz         : 2400.083
cache size      : 12288 KB
physical id     : 0
siblings        : 6
core id         : 0
cpu cores       : 6
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 mmx fxsr sse sse2 ss ht syscall nx lm constant_tsc rep_good nopl xtopology eagerfpu pni cx16 hypervisor lahf_lm ibrs ibpb spec_ctrl arch_capabilities
bogomips        : 4800.16
clflush size    : 64
cache_alignment : 64
address sizes   : 40 bits physical, 48 bits virtual

I appreciate your replay, and thank you.