Instance failed to start because a library is missing or cannot be opened: "libcrypto.so.1.1"

[Sangyog10]

Versions

• NodeJS: 20.12.2
• mongodb-memory-server:9.2.0
• mongodb: 7.0.9
• mongoose: 8.3.3
• system: fedora 40

What is your question?

I am running the test in Fedora 40 and got this error. I do have "libcrypto.so.1.1" installed

Starting the MongoMemoryServer Instance failed, enable debug log for more information. Error:
StdoutInstanceError: Instance failed to start because a library is missing or cannot be opened: "libcrypto.so.1.1"
at MongoInstance.checkErrorInLine (/home/sangyog/Projects/MIcroservices/Ticket app/tickets/node_modules/mongodb-memory-server-core/src/util/MongoInstance.ts:708:11)
at MongoInstance.stderrHandler (/home/sangyog/Projects/MIcroservices/Ticket app/tickets/node_modules/mongodb-memory-server-core/src/util/MongoInstance.ts:595:10)
at Socket.emit (node:events:518:28)
at addChunk (node:internal/streams/readable:559:12)
at readableAddChunkPushByteMode (node:internal/streams/readable:510:3)
at Socket.Readable.push (node:internal/streams/readable:390:5)
at Pipe.onStreamRead (node:internal/stream_base_commons:190:23)

[hasezoey]

I do have "libcrypto.so.1.1" installed

if that error is present, then you either dont have it installed, or it is not available to be found. you can check with ldconfig -p | grep libcrypto.

[Sangyog10]

I get the following result by running the given command: $ldconfig -p | grep libcrypto
libcrypto.so.3 (libc6,x86-64) => /lib64/libcrypto.so.3
libcrypto.so.1.1 (libc6) => /lib/libcrypto.so.1.1
libcrypto.so (libc6,x86-64) => /lib64/libcrypto.so

[hasezoey]

if that is your output and you are not running mongodb-memory-server / the resulting started binary in a separate environment, i dont know what could be wrong with linking, maybe it would help to have the full debug log?

[Yarkhan]

Having this issue as well on a docker container. Using the image node:20-buster solved the issue for me.

[mpsebastianvidiv]

Same on Node 20.14.0

[steven-supersolid]

There is a similar issue on Debian 11 Bullseye nodejs/docker-node#1916 (fixed by using an image that uses Buster as mentioned above)
But not sure how that relates to Fedora 40
Did you try running the following, although the ldconfig may cover it?

whereis libcrypto.so.1.1