Mongodb-memory-server: throw custom error on "lib*" missing

Created on 15 Oct 2020  路  8Comments  路  Source: nodkz/mongodb-memory-server

Versions

  • NodeJS: v12.18.3
  • mongodb-memory-server-*: 6.9.2
  • mongodb: 3.2.7
  • system: Fedora 32 Linux 5.8.13-200.fc32.x86_64

package: mongo-memory-server

What is the Problem?

Running jest failed throwing:

mongod instance closed with code 127

Do you know why it happenes?

Enabling debugging revealed:

libcrypto.so.10: cannot open shared object

Then installing compat-openssl fixed the issue

feature released released on @beta

Most helpful comment

Thanks for the answers! Going to close the issue since there's nothing to be done from what I can tell.

as i said before, i converted this issue to an feature request to "throw an custom error if an lib is missing", which is not implemented yet

All 8 comments

this is not really an bug of this package, i will change this to an "feature request" (as in throwing an custom error on lib* missing)

One Fedora 33 the package is called compat-openssl10.

Thanks for the answers! Going to close the issue since there's nothing to be done from what I can tell.

Thanks for the answers! Going to close the issue since there's nothing to be done from what I can tell.

as i said before, i converted this issue to an feature request to "throw an custom error if an lib is missing", which is not implemented yet

Thanks for the answers! Going to close the issue since there's nothing to be done from what I can tell.

as i said before, i converted this issue to an feature request to "throw an custom error if an lib is missing", which is not implemented yet

Oh sorry I misunderstood

:tada: This issue has been resolved in version 7.0.0-beta.21 :tada:

The release is available on:

Your semantic-release bot :package::rocket:

closing because extra logging got added in 7.0.0-beta.21

Was this page helpful?
0 / 5 - 0 ratings