Fatal assertion possibly related to openssl

Ops and Admin Containers and Orchestration
1

I have a deployment of mongoDB on a Rancher cluster that is crashing with the following logs:

{"t":{"$date":"2024-11-05T17:46:59.739Z"},"s":"F",  "c":"ASSERT",   "id":23089,   "ctx":"main","msg":"Fatal assertion","attr":{"msgid":40379,"file":"src/mongo/crypto/sha_block_openssl.cpp","line":162}}
{"t":{"$date":"2024-11-05T17:46:59.739Z"},"s":"F",  "c":"ASSERT",   "id":23090,   "ctx":"main","msg":"\n\n***aborting after fassert() failure\n\n"}

There seems to be an issue with src/mongo/crypto/sha_block_openssl.cpp. I haven’t been able to find any information about this issue online. The Rancher cluster is version 2.7.10 and the mongo container is the official Dockerhub image with the latest tag.

2 Likes
2

I am having the exact same error. I am trying to run it using podman on RH8. I wasn’t sure if it was a podman thing or something wrong in the mongodb image. ( i.e. is there something I have to setup or pass to podman when it tries to run the container? Or is there a flaw in the image?)

2 Likes
3

I’m seeing it too, note I’m trying to run the mongodb 8.0.9 docker container. It doesn’t happen with 7.0.21 but I’ve tried other mongo 8 docker containers and can’t get any to stay started. Meanwhile, on another machine, docker starts the mongodb 8.0.9 docker container just fine. These are virtual machines running the same version RHEL operating system.