-
-
Notifications
You must be signed in to change notification settings - Fork 160
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
Update to 4.12.3 (and 4.12.6) fails with Could not start process: error while loading shared libraries
#515
Comments
@froth ..hmm. the system is detected as debian12 ({operatingSystem=Linux, architecture=X86_64, distribution=Debian, version=DEBIAN_12}) .. i guess that the version for debian11 will not run on debian12 .. can you use a newer mongodb version? Is it a debian12 dist or is it something else (Ubuntu 22.04.4 LTS?) ? |
It is Ubuntu 22.04.4 LTS (Jammy Jellyfish). Updating to Mongo 7.0 works fine. However 6.0 worked until flapdoodle 4.12.2. and downloaded https://fastdl.mongodb.org/linux/mongodb-linux-x86_64-ubuntu2204-6.0.12.tgz So I think something changed in the OS resolution? |
@froth .. hmm.. i must check.. can you give me your /etc/os-release file? I am very surprised that os detection fails this way.. (if this is the bug and not something else) |
I am sorry is was confused yesterday and gave you incorrect information :( . The "this CI-runner Docker image has multiple base images"-maze messed with my brain. The OS actually is I am not sure if that is something that can be configured in this granularity in flapdoodle or if this would even be a good idea. I could live with upgrading to Mongo 7. Sorry again for the wrong OS Info. |
@froth .. i think i could map older versions to ubuntu instead of debian.. |
@froth .. i think i add an option 'strict' or a warning if there is no match desired mongodb version and platform.. so 6.0.x on debian12 would fail.. using the ubuntu version on mongodb could be achieved by overriding the platform detection ... Or i introduce some kind of blacklisting .. It should be maintainable .. somehow:) |
@michaelmosmann that sounds reasonable, thanks for looking into it. It is impressive that it works so nicely across operation systems and mongodb versions :) You can close this issue if you want, I can live with upgrading and/or overriding. |
@froth .. thanks:) i close this if i have a good answer for that question:) until that i leave this open as an reminder .. |
Hello, I had the same problem after upgrading java from 19 to 21 env : Packages:
i tryied changing de.flapdoodle.embed.mongo.version to 4.13.0 i also tryed but everytime i had the same problem. The problem was fixed when i changed the mongodb version from 6.0.2 to 7.0.12
|
@influence160 AFAIK does ubuntu 22.x does not provides libssl1.x anymore and newer mongodb version are using libssl3.x .. so yes. You must use a newer version of mongodb on a newer version of ubuntu. |
Update to 4.12.3 (and following) suddenly failed with
Caused by: java.lang.RuntimeException: Could not start process: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No such file or directory
.Has anything changed in this release that could have caused this?
It uses https://fastdl.mongodb.org/linux/mongodb-linux-x86_64-debian11-6.0.14.tgz on
[Ubuntu 22.04.4 LTS (Jammy Jellyfish)](https://releases.ubuntu.com/jammy)
Full stacktrace:
The text was updated successfully, but these errors were encountered: