Bug 45959 - mongo5.0: Не запускаются mongod.service и mongos.service
Summary: mongo5.0: Не запускаются mongod.service и mongos.service
Status: CLOSED NOTABUG
Alias: None
Product: Sisyphus
Classification: Development
Component: mongo5.0 (show other bugs)
Version: unstable
Hardware: x86_64 Linux
: P5 normal
Assignee: Alexei Takaseev
QA Contact: qa-sisyphus
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-04-26 10:38 MSK by Alexander Makeenkov
Modified: 2023-04-27 09:33 MSK (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Makeenkov 2023-04-26 10:38:15 MSK 
Версии пакетов:
mongo5.0-server-mongos-5.0.17-alt1                                                                                                                               
mongo5.0-server-mongod-5.0.17-alt1

Шаги воспроизведения:
# systemctl start mongod.service
# systemctl start mongos.service

Получаемый результат:
Job for mongod.service failed because a fatal signal was delivered to the control process.
See "systemctl status mongod.service" and "journalctl -xeu mongod.service" for details.

Job for mongos.service failed because a fatal signal was delivered to the control process.
See "systemctl status mongos.service" and "journalctl -xeu mongos.service" for details.

Ошибки в логах:
kernel: traps: mongod[3322] trap invalid opcode ip:562f781d24dc sp:7ffda00ccf00 error:0 in mongod[562f74763000+4dbf000]

kernel: traps: mongos[3480] trap invalid opcode ip:55db19a4b3ec sp:7ffc94ad3e30 error:0 in mongos[55db16fd9000+39eb000]
Comment 1 Alexei Takaseev 2023-04-27 09:33:50 MSK 
Начиная с версии 5.0 для работы ПО требуется процессор с поддержкой AVX, на процессорах старее Sandy Bridge не запустится по определению.