[SERVER-82165] MongoDB checks reported cpu model Created: 13/Oct/23  Updated: 27/Nov/23  Resolved: 27/Nov/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 5.0.21
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Henry Bullwinkel Assignee: Noopur Gupta
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Steps To Reproduce:

Install mongodb on a vm with kvm cpu-model plus added avx flag:

Proxmox example:

cpu-model: extended_kvm64 
   flags +avx
   phys-bits host 
   hidden 0 
   hv-vendor-id proxmox 

Participants:

 Description   

Description

MongoDB checks the reported-model from the CPU and if its not in the required set, mongodb will not start.

log output

/usr/local/bin/docker-entrypoint.sh: line 416:    26 Illegal instruction     "${mongodHackedArgs[@]}" --fork 

 



 Comments   
Comment by Noopur Gupta [ 27/Nov/23 ]

I am closing this ticket since there has been no activity. 

Comment by Noopur Gupta [ 13/Nov/23 ]

Hi Henry

We still need additional information to diagnose the problem. If this is still an issue for you, would you please share the logs requested?

Comment by Noopur Gupta [ 25/Oct/23 ]

It would be really helpful if you can share some logs which states mongodb has failed or mongod did not start. These logs will help us understand why the server could be failing. 

If these logs are not available, I would suspect that there are compatibility issues with the cpu and MongoDB version.

You can also check if you were able to install an older version (v4.4). There were cpu support changes between v4.4 and v5.0+, see Production notes , this could help us clarify if there is a compatibility issue.

Comment by Henry Bullwinkel [ 24/Oct/23 ]

Issue appers with both, running a container or installing MongoDB on the VM.

So it should be the server itself.

 

Comment by Noopur Gupta [ 20/Oct/23 ]

Hi Henry,

Unfortunately the steps of reproduction and information that you provided for this issue, is not sufficient to understand whether this is an issue with the docker images or the server itself. 

For this issue we'd like to encourage you to start by asking our community for help by posting on the MongoDB Developer Community Forums. If the discussion there leads you to suspect a bug in the MongoDB server, then we'd want to investigate it as a possible bug here in the SERVER project.

 

Generated at Thu Feb 08 06:48:26 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.