-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
doesn't seem to work #4
Comments
Possible answer here? |
oh, I see the problem - it's simply hard coded to a specific version that no longer works. 😅 https://github.com/unjs/mongoz/blob/cd762a7746c29de43516efb2e6f8d416a70bfbcb/src/formula.ts#L1-L21 here's a package that can look up the current URLs for downloads on different platforms: https://www.npmjs.com/package/mongodb-download-url what do you think? |
looks like that would work :-)
|
yep, looks like that fixed it - could you take a look at this PR please? 🙂 |
on ubuntu 22.04 libcrypto.so.1.1: the real cause of the problem is that ubuntu 22 no longer supports this version of the library, but the mongo client is compiled specifically for this version of the library. mongo-org thinks you will switch to another utility mongosh |
@blzzua I don't think this package is being maintained - but "the real cause of the problem" is this package installs the wrong binary. It only has a few hard coded binaries to choose from - I already submitted a PR to fix this, but it needs a merge and publish from the author. |
Environment
Reproduction
Describe the bug
npx mongoz
appears to always exit immediately with exit code 0.it will print
Starting mongo at port 27017
but then just exits.Additional context
Logs
$ cat /tmp/mongo/logs/default/mongo/logs.txt /tmp/mongo/source/mongo/4.4.2/linux/unpacked/bin/mongod: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No such file or directory
looks like a missing dependency?
similar issue here:
journeyapps/node-sqlcipher#101
I'm guessing mongo itself is actually exiting with an error status? But somehow the error message/status isn't making it to the console - this seems to happen also with just
npx mongoz
, so probably not related toconcurrently
.I don't know most of the packages you use, so I can't really be of more help here, sorry.
The text was updated successfully, but these errors were encountered: